Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Integration

  • 35 installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/claude-code-sfskills

This is a copy of sf-integration by jaganpro - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks.

About

sf-integration is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • sf-integration
  • AI & Agent Building
  • AI-coding skill

Sf Integration by the numbers

  • 35 all-time installs (skills.sh)
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jaganpro/claude-code-sfskills --skill sf-integration

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs35
repo stars423
Last updatedApril 27, 2026
Repositoryjaganpro/claude-code-sfskills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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

NeedDefault pattern
authenticated outbound API callNamed Credential / External Credential + Apex or Flow
spec-driven API clientExternal Service
trigger-originated calloutasync callout pattern
decoupled event publishingPlatform Events
change-stream consumptionCDC

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

---

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: 1. Integration pattern chosen 2. Auth model chosen 3. Files created or updated 4. Operational safeguards 5. 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

NeedDelegate toReason
OAuth app setupsf-connected-appsconsumer key / cert / app config
advanced callout service codesf-apexApex implementation
declarative HTTP callout / Flow wrappersf-flowFlow orchestration
deploy integration metadatasf-deployvalidation and rollout
use integration from Agentforcesf-ai-agentscriptagent action composition

---

Reference Map

Start here

  • references/named-credentials-guide.md
  • references/external-services-guide.md
  • references/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
  • assets/

---

Score Guide

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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.