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 consumer-goods-accruals-datakit-deploygit 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/consumer-goods-accruals-datakit-deploy)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/consumer-goods-accruals-datakit-deploy"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/consumer-goods-accruals-datakit-deploy/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/consumer-goods-accruals-datakit-deploy"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/consumer-goods-accruals-datakit-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00197 | $0.04873 |
| Opus 5.5 | $0.00079 | $0.01949 |
| Sonnet 5.5 | $0.00039 | $0.00975 |
| Haiku 4.5 | $0.00020 | $0.00487 |
Grade A, and why
consumer-goods-accruals-datakit-deploy 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 9d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY: Always write the Phase 6 report
After completing all phases — including early stops, blocked phases, or error conditions — you MUST write the Phase 6 report to disk. Failure to write the report is always a test failure, regardless of how well you handled the scenario.
This applies to ALL exit paths without exception:
- Normal completion (all phases ran)
- Phase 1 stop (preflight failed, sales org not found, CGCloudAddons missing, Data Cloud not enabled)
- Phase 3 error (setup script non-zero exit)
- Phase 4 failure detection (DataKitDeploymentLog failures)
- Schedule conflict (Phase 5 guard triggered)
- Any other blocking condition (missing inputs, org unreachable, etc.)
Write the report to ${outputDir}/report.md (the path from the generatedFileLocationDirective in the task). Do not print it as a chat message only — it must exist as a file on disk. If you handled a scenario correctly but never wrote the file, the eval will record no_output and score zero.
Deploy the Accrual Data Kit
Installs the TPM Liability Accruals solution into a Salesforce org end to end.
Runs the full setup toolchain bundled in scripts/: checks the org is ready,
verifies the Data Cloud connection, downloads the CGCloudAddons static resource,
deploys the data kit, confirms the deployment, and schedules the Data Cloud export
and accrual calculation chain.
Designed for headless delivery: point it at an org and it runs the full install.
The namespace differs per build: cgcloud (released), cgcloud_dev (dev/beta), or no
prefix (source-only). The setup script auto-detects the prefix at runtime via the
DataCloudExportScheduler Apex class query. Never hardcode cgcloud. or cgcloud_dev..
Reference: TPM Accrual Engine concept
Run the setup script from the skill root directory:
node scripts/setup.js --org <alias> [options]
Inputs to collect
What ships with it
12 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.
- scripts/setup.js 11 KB runs code
- scripts/steps/00-check-prerequisites.js 1.9 KB runs code
- scripts/steps/01-download-static-resource.js 3.5 KB runs code
- scripts/steps/02-replace-org-id.js 1.6 KB runs code
- scripts/steps/03-deploy-metadata.js 1.1 KB runs code
- scripts/steps/04-deploy-engine.js 6.7 KB runs code
- scripts/steps/05-deploy-tpm-accruals.js 8.9 KB runs code
- scripts/steps/06-create-dataspace.js 2.0 KB runs code
- scripts/steps/07-deploy-accruals-reports.js 8.5 KB runs code
- scripts/steps/08-deploy-ui.js 8.1 KB runs code
- scripts/steps/09-completion.js 2.5 KB runs code
- scripts/steps/utils.js 16 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.
- 9d ago Changed · -10 lines bd7d4def238b
- 28d ago First seen · 384 lines · 197 tokens per session scan A c419a2cf2a09
consumer-goods-accruals-datakit-deploy is a skill published in the GitHub repository forcedotcom/sf-skills (1,097 stars, last pushed today), licensed Apache-2.0. It adds 197 tokens to every session and 4,873 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-19.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…