Agent skill

Sf Integration

Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills.

Install Sf Integration

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-integration .claude/skills/sf-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .claude/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-integration .agents/skills/sf-integration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .agents/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-integration .cursor/skills/sf-integration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .cursor/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-integration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-integration .gemini/skills/sf-integration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .gemini/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-integration .github/skills/sf-integration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .github/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-integration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-integration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-integration .opencode/skills/sf-integration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-integration" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-integration into .opencode/skills/sf-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-integration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sf-integration
GitHub stars: 424
Token cost: ~1.5k tokens
SKILL.md length: 455 words
Files: 52 (incl. scripts, references, assets)
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills.

Works in 5 steps: Choose the integration pattern → Choose the auth model → Generate from the right templates → …
: user sets up Named Credentials
SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Recommended Workflow and High-Signal Rules, plus 4 more sections
External Services

What it does

Sf Integration is an agent skill from Jaganpro/sf-skills. Salesforce integration architecture with 120-point scoring. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use sf-connected-apps), Apex-only logic (use sf-apex), or data import/export (use sf-data).

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 57 other files, including scripts, reference files and assets (for example `CREDITS.md`, `README.md` and `assets/external-services/external-service-operations.md`).

It sits in Backend & APIs, covering CRM management, Third-party API integration and OAuth and OpenID Connect. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

: user sets up Named Credentials
External Services
REST/SOAP callouts
Platform Events

Example prompts

“/sf-integration”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Choose the integration pattern
Choose the auth model
Generate from the right templates
Validate operational safety
Hand off deployment or implementation details

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sf Integration loads about 1.5k tokens when it runs, and up to ~35k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 455 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~92
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~35k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 455 words, ~1,469 tokens.

Download SKILL.mdSave it as .claude/skills/sf-integration/SKILL.md (or your agent's skills folder). This skill also uses 51 other files; get the full folder from GitHub.

name: sf-integration
description: Salesforce integration architecture with 120-point scoring. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use sf-connected-apps), Apex-only logic (use sf-apex), or data import/export (use sf-data).
license: MIT
metadata.version: 1.2.0
metadata.author: Jag Valaiyapathy
metadata.scoring: 120 points across 6 categories

sf-integration: Salesforce Integration Patterns Expert

Use this skill when the user needs integration architecture and runtime plumbing: Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, CDC, and event-driven integration design.

When This Skill Owns the Task

Use sf-integration when the work involves:

.namedCredential-meta.xml or External Credential metadata
outbound REST/SOAP callouts
External Service registration from OpenAPI specs
Platform Events, CDC, and event-driven architecture
choosing sync vs async integration patterns

Delegate elsewhere when the user is:

configuring the OAuth app itself → sf-connected-apps
writing Apex-only business logic → sf-apex
deploying metadata → sf-deploy
importing/exporting data → sf-data

Required Context to Gather First

Ask for or infer:

integration style: outbound callout, inbound event, External Service, CDC, platform event
auth method
sync vs async requirement
system endpoint / spec details
rate limits, retry expectations, and failure tolerance
whether this is net-new design or repair of an existing integration

Recommended Workflow

1. Choose the integration pattern

Need	Default pattern
authenticated outbound API call	Named Credential / External Credential + Apex or Flow
spec-driven API client	External Service
trigger-originated callout	async callout pattern
decoupled event publishing	Platform Events
change-stream consumption	CDC

2. Choose the auth model

Prefer secure runtime-managed auth:

Named Credentials / External Credentials
OAuth or JWT via the right credential model
no hardcoded secrets in code

3. Generate from the right templates

Use the provided assets under:

assets/named-credentials/
assets/external-credentials/
assets/external-services/
assets/callouts/
assets/platform-events/
assets/cdc/
assets/soap/

4. Validate operational safety

Check:

timeout and retry handling
async strategy for trigger-originated work
logging / observability
event retention and subscriber implications

5. Hand off deployment or implementation details

Use:

sf-deploy for deployment
sf-apex for deeper service / retry code
sf-flow for declarative HTTP callout orchestration

Show full SKILL.md (186 more words)Show less

High-Signal Rules

never hardcode credentials
do not do synchronous callouts from triggers
define timeout behavior explicitly
plan retries for transient failures
use middleware / event-driven patterns when outbound volume is high
prefer External Credentials architecture for new development when supported

Common anti-patterns:

sync trigger callouts
no retry or dead-letter strategy
no request/response logging
mixing auth setup responsibilities with runtime integration design

Output Format

When finishing, report in this order:

Integration pattern chosen
Auth model chosen
Files created or updated
Operational safeguards
Deployment / testing next step

Suggested shape:

text

Integration: <summary>
Pattern: <named credential / external service / event / cdc / callout>
Files: <paths>
Safety: <timeouts, retries, async, logging>
Next step: <deploy, register, test, or implement>

Cross-Skill Integration

Need	Delegate to	Reason
OAuth app setup	sf-connected-apps	consumer key / cert / app config
advanced callout service code	sf-apex	Apex implementation
declarative HTTP callout / Flow wrapper	sf-flow	Flow orchestration
deploy integration metadata	sf-deploy	validation and rollout
use integration from Agentforce	sf-ai-agentscript	agent action composition

Reference Map

Start here

Event-driven / platform patterns

CLI / automation / scoring

Score Guide

Score	Meaning
108+	strong production-ready integration design
90–107	good design with some hardening left
72–89	workable but needs architectural review
< 72	unsafe / incomplete for deployment

Files

SKILL.md and 51 other files (scripts, references, assets) in skills/sf-integration of Jaganpro/sf-skills.

SKILL.md
CREDITS.md
README.md
assets/callouts/callout-retry-handler.cls
assets/callouts/http-response-handler.cls
assets/callouts/rest-queueable-callout.cls
assets/callouts/rest-sync-callout.cls
assets/cdc/cdc-handler.cls
assets/cdc/cdc-subscriber-trigger.trigger
assets/endpoint-security/example.cspTrustedSite-meta.xml
assets/endpoint-security/example.remoteSite-meta.xml
assets/external-credentials/jwt-external-credential.externalCredential-meta.xml
assets/external-credentials/oauth-external-credential.externalCredential-meta.xml
assets/external-services/external-service-operations.md
assets/external-services/openapi-registration.externalServiceRegistration-meta.xml
… and 37 more

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sf Integration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Integration this skillJaganpro/sf-skills	424	—	~1.5k	Automated safety check: Pass	MIT	5 mo ago
Integration Connectivity Generateforcedotcom/sf-skills	1.1k	—	~2.2k	Automated safety check: Pass	Apache-2.0	yesterday
Implementing Zero Trust For SaaS Applicationsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Zoho BiginCraftOS-dev/CraftBot	392	1 repos	~4.3k	Automated safety check: Pass	MIT	yesterday
Integration Connectivity Connected App Configureforcedotcom/sf-skills	1.1k	—	~2.7k	Automated safety check: Notes	Apache-2.0	yesterday
Experience Lwc Legacy Migrateforcedotcom/sf-skills	1.1k	—	~2.6k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Integration Connectivity Generate
forcedotcom/sf-skills
Salesforce integration architecture and runtime plumbing with 120-point scoring.
1.1k GitHub stars~2.2k tokensUpdated yesterday
Backend & APIsAuto-check passed
Implementing Zero Trust For SaaS Applications
mukul975/Anthropic-Cybersecurity-Skills
Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…
34k GitHub stars~2.9k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Zoho Bigin
CraftOS-dev/CraftBot
Zoho Bigin API integration with managed OAuth. An agent skill from CraftOS-dev/CraftBot.
392 GitHub starsUsed in 1 repo~4.3k tokens
Backend & APIsAuto-check passed
Integration Connectivity Connected App Configure
forcedotcom/sf-skills
Salesforce Connected Apps and External Client Apps OAuth configuration with 120-point scoring.
1.1k GitHub stars~2.7k tokensUpdated yesterday
Backend & APIsAuto-check: notes
Experience Lwc Legacy Migrate
forcedotcom/sf-skills
Migrate legacy Salesforce UI stacks onto modern LWC — Aura → LWC conversion completeness verification and Lightning Out Beta → Lightning Out 2.0 host-page migration.
1.1k GitHub stars~2.6k tokensUpdated yesterday
Sales & SupportAuto-check passed
Hunt Sqli
elementalsouls/Claude-BugHunter
Hunting skill for sqli vulnerabilities. An agent skill from elementalsouls/Claude-BugHunter.
4.8k GitHub stars~5.5k tokensUpdated yesterday
DatabasesAuto-check passed

Questions about Sf Integration

What does Sf Integration do?

Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills. Sf Integration is an agent skill from Jaganpro/sf-skills. Salesforce integration architecture with 120-point scoring.

When should I use Sf Integration?

Sf Integration fits situations like: : user sets up Named Credentials; external Services; REST/SOAP callouts; platform Events.

How do I install Sf Integration in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-integration -a claude-code`. Or copy the skill folder (skills/sf-integration in Jaganpro/sf-skills) into .claude/skills/sf-integration in your project. Claude Code loads it when a task matches its description.

How do I install Sf Integration in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-integration -a codex`. Or copy the skill folder (skills/sf-integration in Jaganpro/sf-skills) into .agents/skills/sf-integration in your project. Codex loads it when a task matches its description.

Can I use Sf Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-integration, .gemini/skills/sf-integration, .github/skills/sf-integration and .opencode/skills/sf-integration in your project.

What does Sf Integration need to run?

SKILL.md names no scripts, command-line tools or credentials: Sf Integration is instructions for the agent only.

Does Sf Integration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sf Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sf Integration use?

Sf Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Integration use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 34k tokens, read only when the agent opens those files.

What are the alternatives to Sf Integration?

Skills that share tags, products or a category with Sf Integration: Integration Connectivity Generate (forcedotcom/sf-skills, 1.1k stars), Implementing Zero Trust For SaaS Applications (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Zoho Bigin (CraftOS-dev/CraftBot, 392 stars) and Integration Connectivity Connected App Configure (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Integration?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sf Integration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sf-integration: Salesforce Integration Patterns Expert

When This Skill Owns the Task

Required Context to Gather First

Recommended Workflow

1. Choose the integration pattern

2. Choose the auth model

3. Generate from the right templates

4. Validate operational safety

5. Hand off deployment or implementation details

High-Signal Rules

Output Format

Cross-Skill Integration

Reference Map

Start here

Event-driven / platform patterns

CLI / automation / scoring

Score Guide

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Integration