Sf Integration
Jaganpro/sf-skills
Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills.
Salesforce integration architecture and runtime plumbing with 120-point scoring.
Install Integration Connectivity Generate
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/integration-connectivity-generate .claude/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.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/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .claude/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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 install https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generateType 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.
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/integration-connectivity-generate .agents/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .agents/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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.
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/integration-connectivity-generate .cursor/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .cursor/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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 https://github.com/forcedotcom/sf-skills.git --path skills/integration-connectivity-generate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/integration-connectivity-generate .gemini/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.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/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .gemini/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generateInstalls 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).
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/integration-connectivity-generate .github/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.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/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .github/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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.
$ npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills integration-connectivity-generate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/integration-connectivity-generate .opencode/skills/integration-connectivity-generate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "integration-connectivity-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/integration-connectivity-generate into .opencode/skills/integration-connectivity-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-connectivity-generate", 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
integration-connectivity-generate- GitHub stars
- 1.1k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 684 words
- Files
- 49 (incl. scripts, references, assets)
- Skills in repo
- 251
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Salesforce integration architecture and runtime plumbing with 120-point scoring.
- Works in 5 steps: Choose the integration pattern → Choose the auth model → Generate from the right templates → …
- Set up Named Credentials
- SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Recommended Workflow and High-Signal Rules, plus 6 more sections
- External Credentials
What it does
Integration Connectivity Generate is an agent skill from forcedotcom/sf-skills. Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. 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 integration-connectivity-connected-app-configure), Apex-only logic (use…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 54 other files, including scripts, reference files and assets (for example `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: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.
When your agent uses it
- Set up Named Credentials
- External Credentials
- External Services
- REST/SOAP callout patterns
Example prompts
- “/integration-connectivity-generate”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5164d9. 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
Integration Connectivity Generate loads about 2.2k tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 192 tokens; SKILL.md has 684 words of instructions outside code blocks.
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 forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 684 words, ~2,233 tokens.
Download SKILL.mdSave it as
.claude/skills/integration-connectivity-generate/SKILL.md (or your agent's skills folder). This skill also uses 48 other files; get the full folder from GitHub.- name
- integration-connectivity-generate
- description
- Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. 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 integration-connectivity-connected-app-configure), Apex-only logic (use platform-apex-generate), data import/export (use platform-data-manage), or CDC channel-membership metadata such as PlatformEventChannel, PlatformEventChannelMember, or EnrichedField (use integration-eventing-cdc-configure).
- metadata.version
- 1.1
- metadata.domains
- Integration
- metadata.minApiVersion
- 61.0
- metadata.relatedSkills
- agentforce-generate, automation-flow-generate, integration-connectivity-connected-app-configure, integration-eventing-cdc-configure, platform-apex-generate…
integration-connectivity-generate: 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 integration-connectivity-generate when the work involves:
.namedCredential-meta.xmlor 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 → integration-connectivity-connected-app-configure
- writing Apex-only business logic → the
platform-apex-generateskill - deploying metadata → the
platform-metadata-deployskill - importing/exporting data → the
platform-data-manageskill
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:
- the
platform-metadata-deployskill for deployment - the
platform-apex-generateskill for deeper service / retry code - the
automation-flow-generateskill for declarative HTTP callout orchestration
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:
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 | integration-connectivity-connected-app-configure | consumer key / cert / app config |
| advanced callout service code | platform-apex-generate skill | Apex implementation |
| declarative HTTP callout / Flow wrapper | automation-flow-generate skill | Flow orchestration |
| deploy integration metadata | platform-metadata-deploy skill | validation and rollout |
| use integration from Agentforce | agentforce-generate skill | agent action composition |
Show full SKILL.md (263 more words)Show less
Reference Map
Start here
- references/named-credentials-guide.md
- references/external-services-guide.md
- references/callout-patterns.md
- references/rest-callout-patterns.md
- references/security-best-practices.md
Event-driven / platform patterns
- references/event-patterns.md
- references/platform-events-guide.md
- references/cdc-guide.md
- references/event-driven-architecture-guide.md
- references/messaging-api-v2.md
CLI / automation / scoring
- references/cli-reference.md
- references/named-credentials-automation.md
- references/scoring-rubric.md
- scripts/README.md — automation scripts overview (configure-named-credential.sh, set-api-credential.sh)
Asset templates
assets/named-credentials/— Named Credential XML templates (OAuth, JWT, Certificate, Custom auth)assets/external-credentials/— External Credential XML templates (OAuth, JWT)assets/external-services/— External Service registration template and operations guideassets/callouts/— REST sync, Queueable, retry handler, and HTTP response handler Apex templatesassets/platform-events/— Platform Event definition, publisher, and subscriber templatesassets/cdc/— CDC handler and subscriber trigger templatesassets/soap/— SOAP callout service template and wsdl2apex guideassets/endpoint-security/— Remote Site Setting and CSP Trusted Site XML templates
Automation hooks
scripts/suggest_credential_setup.py— auto-suggests credential configuration steps when integration files are detectedscripts/validate_integration.py— validates integration patterns before agent responses
Output Expectations
When this skill completes an integration task, it produces:
- Credential metadata — one or more files in
assets/named-credentials/orassets/external-credentials/filled with org-specific values - Callout Apex class — a
.clsfile using the Named Credential pattern, with async/sync pattern chosen based on context - Event/CDC artifacts — Platform Event
.object-meta.xml, subscriber trigger, or CDC config (when event-driven pattern is chosen) - Endpoint security metadata — Remote Site Setting and/or CSP Trusted Site XML files
- Scoring report — 120-point score across 6 categories (Security, Error Handling, Bulkification, Architecture, Best Practices, Documentation)
- Next step — a deployment or testing instruction for the generated artifacts
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 |
Pre-Delivery Checklist
- Never hardcode credentials — all secrets stored in Named Credentials or External Credentials
© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 48 other files (scripts, references, assets) in skills/integration-connectivity-generate of forcedotcom/sf-skills.
- SKILL.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
- assets/named-credentials
- … and 34 more
Open the folder on GitHubat commit e5164d9
Compare with similar skills
Integration Connectivity Generate 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Integration Connectivity Generate this skillforcedotcom/sf-skills | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Sf IntegrationJaganpro/sf-skills | 424 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Implementing Zero Trust For SaaS Applicationsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Zoho BiginCraftOS-dev/CraftBot | 392 | 1 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Sf Connected AppsJaganpro/sf-skills | 424 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Hunt Sqlielementalsouls/Claude-BugHunter | 4.8k | — | ~5.5k | Automated safety check: Pass | MIT |
Similar skills
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…
Zoho Bigin
CraftOS-dev/CraftBot
Zoho Bigin API integration with managed OAuth. An agent skill from CraftOS-dev/CraftBot.
Sf Connected Apps
Jaganpro/sf-skills
Salesforce Connected Apps and OAuth configuration with 120-point scoring.
Hunt Sqli
elementalsouls/Claude-BugHunter
Hunting skill for sqli vulnerabilities. An agent skill from elementalsouls/Claude-BugHunter.
Salesforce Webhooks Events
jeremylongshore/tons-of-skills-marketplace
Select and govern Salesforce change delivery across Pub/Sub API, Change Data Capture, Platform Events, event relay, Streaming API, Outbound Messages, or polling.
More from forcedotcom/sf-skills
All 251 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Integration Connectivity Generate
What does Integration Connectivity Generate do?
Salesforce integration architecture and runtime plumbing with 120-point scoring. Integration Connectivity Generate is an agent skill from forcedotcom/sf-skills. Salesforce integration architecture and runtime plumbing with 120-point scoring.
When should I use Integration Connectivity Generate?
Integration Connectivity Generate fits situations like: set up Named Credentials; external Credentials; external Services; REST/SOAP callout patterns.
How do I install Integration Connectivity Generate in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a claude-code`. Or copy the skill folder (skills/integration-connectivity-generate in forcedotcom/sf-skills) into .claude/skills/integration-connectivity-generate in your project. Claude Code loads it when a task matches its description.
How do I install Integration Connectivity Generate in Codex?
Run `npx skills add forcedotcom/sf-skills --skill integration-connectivity-generate -a codex`. Or copy the skill folder (skills/integration-connectivity-generate in forcedotcom/sf-skills) into .agents/skills/integration-connectivity-generate in your project. Codex loads it when a task matches its description.
Can I use Integration Connectivity Generate 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 forcedotcom/sf-skills --skill integration-connectivity-generate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integration-connectivity-generate, .gemini/skills/integration-connectivity-generate, .github/skills/integration-connectivity-generate and .opencode/skills/integration-connectivity-generate in your project.
What does Integration Connectivity Generate need to run?
SKILL.md names no scripts, command-line tools or credentials: Integration Connectivity Generate is instructions for the agent only.
Does Integration Connectivity Generate 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 Integration Connectivity Generate 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 Integration Connectivity Generate use?
Integration Connectivity Generate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Integration Connectivity Generate use?
About 2.2k tokens (SKILL.md is roughly 8.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 Integration Connectivity Generate?
Skills that share tags, products or a category with Integration Connectivity Generate: Sf Integration (Jaganpro/sf-skills, 424 stars), Implementing Zero Trust For SaaS Applications (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Zoho Bigin (CraftOS-dev/CraftBot, 392 stars) and Sf Connected Apps (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Integration Connectivity Generate?
forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.
Source: forcedotcom/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.