forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add forcedotcom/sf-skills --skill service-agentforce-channel-configuregit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/forcedotcom/sf-skills/service-agentforce-channel-configure)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/service-agentforce-channel-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-agentforce-channel-configure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/service-agentforce-channel-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-agentforce-channel-configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 179 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 219 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00211 | $0.05003 |
| Opus 5.5 | $0.00084 | $0.02001 |
| Sonnet 5.5 | $0.00042 | $0.01001 |
| Haiku 4.5 | $0.00021 | $0.00500 |
Grade A, and why
service-agentforce-channel-configure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
service-agentforce-channel-configure: Wire an Agentforce agent to a channel
Adds inbound routing between an existing channel and an existing Agentforce agent. The agent receives work items from the channel; a fallback queue handles overflow when the agent is unavailable.
This skill is generic — it works for any Agentforce agent, not just the Help Agent template.
Scope
In scope:
- Resolving or creating a fallback queue with the correct
QueueSobjectSobjectType - Branch A (Enhanced Chat / Enhanced Messaging): deploying
sessionHandlerType=AgentforceServiceAgent+sessionHandlerQueueon an existing MessagingChannel, then bindingSessionHandlerIdvia Data API PATCH - Branch B (Voice): assumes the phone number and
PstnVoiceMessagingChannel already exist (provisioned by the caller, e.g.service-helpagent-coordinate), then creating an inbound RoutingFlow (routingType: Copilot) that routes to the agent with the queue as fallback - Branch C (Email-to-Case): inbound routing via direct case-owner assignment or an Omni-Channel RoutingFlow, plus deploying a
BotEmailDefinition(Email Configuration) that links the agent to Service Email and binding it to the routing address - Optional outbound escalation: delegating the verified agent-to-human handoff contract to
service-agentforce-human-escalation-configure
Out of scope:
- Creating the agent — use
agentforce-generateorservice-helpagent-coordinate - Creating the MessagingChannel — use
service-digital-engagement-channel-configure - Creating the Embedded Service Deployment — use
service-digital-engagement-deployment-configure - Creating the Voice or Email-to-Case channel infrastructure
Required inputs
- Agent
DeveloperNameand agent label (MasterLabel) — must be an existing, active agent - Channel type — one of: Enhanced Chat, Enhanced Messaging (3rd-party), Voice, Email-to-Case
- Channel identifier — MessagingChannel
DeveloperName(Branch A), or the channel name/context (Branches B/C) - Target org alias
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/BotEmailDefinition.botEmailDefinition-meta.xml 2.1 KB
- assets/email/unfiled$public/AgentforceForServiceEmailTemplate.email 780 B
- assets/email/unfiled$public/AgentforceForServiceEmailTemplate.email-meta.xml 1.5 KB
- assets/mdapi-package.xml 1.1 KB
- assets/settings-mdapi-package.xml 1.4 KB
- references/agent-wiring.md 5.7 KB
- references/botemaildefinition.md 8.5 KB
- references/channel-branch-email.md 23 KB
- references/channel-branch-voice.md 3.5 KB
- references/channel-types.md 5.3 KB
- references/live-traffic-gate.md 5.7 KB
- references/queue-resolution.md 6.5 KB
- references/routing-flow.md 17 KB
- scripts/validate-botemaildefinition.py 4.8 KB runs code
- scripts/validate-emailtemplate.py 4.9 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago Changed · -2 lines 57637d507d08
- 1mo ago Changed · +5 lines ff50676c62c4
- 1mo ago First seen · 281 lines · 211 tokens per session scan A c75a466e0f81
service-agentforce-channel-configure is a skill published in the GitHub repository forcedotcom/sf-skills (1,116 stars, last pushed 4d ago), licensed Apache-2.0. It adds 211 tokens to every session and 5,003 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
commerce-app-migrate
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A…
full-stack-orchestration-full-stack-feature
Coordinate database, backend, frontend, testing, and deployment work for a complete feature. Use when implementing changes that span multiple application layers.
multi-platform-apps-multi-platform
Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.
copying-endpoints-across-projects
Copy a PostHog endpoint (a saved HogQL/insight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's…
developing-subscriptions
Guides PostHog engineers through subscription product changes. Use when changing subscription resource types, destinations, schedules, delivery workflows, retry or automatic disable behavior, permissions, limits, AI summaries, AI prompt reports, delivery history, subscription APIs, MCP tools, or subscription…