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-digital-engagement-messaging-site-integrategit 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-digital-engagement-messaging-site-integrate)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/service-digital-engagement-messaging-site-integrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-digital-engagement-messaging-site-integrate/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-digital-engagement-messaging-site-integrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-digital-engagement-messaging-site-integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00200 | $0.04111 |
| Opus 5.5 | $0.00080 | $0.01644 |
| Sonnet 5.5 | $0.00040 | $0.00822 |
| Haiku 4.5 | $0.00020 | $0.00411 |
Grade A, and why
service-digital-engagement-messaging-site-integrate scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- tool: ["curl"] How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embed Messaging Widget on an Experience Cloud Site
Wires an existing Embedded Messaging (MIAW) deployment onto an Experience Cloud site by retrieving the site's bundle (LWR DigitalExperienceBundle or Aura ExperienceBundle), patching the home page JSON to place the experience_messaging:embeddedMessaging component, staging the bundle into the local project, deploying it, publishing the site, and verifying guest access.
The operation is idempotent: if the component is already present it is updated in place (its id is preserved), so re-running with different ESD coordinates cleanly updates.
Scope
- In scope: Detecting LWR vs Aura bundle type; scaffolding missing LWR template routes required by the site template (e.g.
too-many-requests); patching allsfdc_cms__themeLayout/*/content.jsonfiles to insert or update the Embedded Messaging component in the footer region (site-wide placement); staging the bundle intoforce-app; async deploy with polling; resolving theNetwork.Nameand publishing the site; guest-URL smoke test; manual Experience Builder fallback with a deep link. - Out of scope: Creating the
EmbeddedServiceConfig(Embedded Service Deployment) itself — useservice-digital-engagement-deployment-configure; creating theMessagingChannel— useservice-digital-engagement-channel-configure; creating the Experience Cloud site itself — useexperience-lwr-site-generate; generating a standalone JS snippet for a non-Experience website.
Clarifying Questions
Before executing, ask the user if not already clear:
- Site name? The
DeveloperNameof the Experience Cloud site (the metadata folder name underdigitalExperiences/site/<siteName>/orexperiences/<siteName>/). - Deployment coordinates? The
deploymentName(Embedded Service DeploymentDeveloperName), thescrtUrl, and thesiteEndpoint(Experience site base URL). All three come from the publishedEmbeddedServiceConfig— obtain fromservice-digital-engagement-deployment-configureoutput if not provided. - Target org alias? For the
sfcommands. - URL path prefix? The site's
UrlPathPrefix(needed to resolveNetwork.Namefor publish and to hit the guest URL for verification).
What ships with it
9 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.
- references/aura_patch.md 2.4 KB
- references/bundle_detection.md 2.5 KB
- references/deploy_and_publish.md 3.6 KB
- references/lwr_patch.md 3.7 KB
- references/lwr_route_scaffolding.md 1.8 KB
- references/manual_fallback.md 3.0 KB
- scripts/detect_bundle_type.sh 1.1 KB runs code
- scripts/patch_aura_bundle.sh 4.1 KB runs code
- scripts/patch_lwr_bundle.sh 7.3 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.
- 1mo ago First seen · 292 lines · 200 tokens per session scan A 9c9f03e3d191
service-digital-engagement-messaging-site-integrate is a skill published in the GitHub repository forcedotcom/sf-skills (1,120 stars, last pushed today), licensed Apache-2.0. It adds 200 tokens to every session and 4,111 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…