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 experience-aura-lwc-migrategit 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/experience-aura-lwc-migrate)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/experience-aura-lwc-migrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/experience-aura-lwc-migrate/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/experience-aura-lwc-migrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/experience-aura-lwc-migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- 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.00243 | $0.03260 |
| Opus 5.5 | $0.00097 | $0.01304 |
| Sonnet 5.5 | $0.00049 | $0.00652 |
| Haiku 4.5 | $0.00024 | $0.00326 |
Grade A, and why
experience-aura-lwc-migrate 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 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.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating Aura to LWC
Migrate an existing Salesforce Aura component bundle to a Lightning Web Component using a PRD-driven workflow. The Aura source is analyzed through eight expert lenses (static references, data, API surface, slots, styling, default values, unknown dependencies, redundant-code cleanup) to produce a framework-agnostic PRD, which is handed to the LWC authoring skills and verified against the Aura→LWC completeness checklist.
When to Use
- Porting an Aura bundle (
.cmp,.controller.js,.helper.js,.renderer.js,.css,.design,.evt,.intf) to LWC. - Producing a framework-agnostic PRD from Aura source so a sibling team can implement the LWC equivalent.
- Auditing an Aura component for patterns that need explicit mapping before LWC conversion (facets,
aura:idDOM access,force:recordData, application events).
Do NOT use this skill for:
- Authoring a brand-new LWC from a Figma or PRD with no Aura source (delegate to
experience-lwc-generate). - Refactoring an existing LWC (delegate to
experience-lwc-generate). - Post-hoc completeness scoring of a conversion that was already done without this skill, or Lightning Out Beta → 2.0 host-page migration — no checked-in skill covers these today.
Prerequisites
- Aura component bundle files (minimum:
.cmp; usually also controller / helper / CSS / events / interfaces). - Target LWC path (module folder) — discover the caller's module tree from
sfdx-project.jsonpackageDirectories(typically anlwc/<name>/subdirectory under one of the listed package paths). - For resolver-assisted dependency lookup (Phase 2, step 7): the
@sfdc-internal/adk-knowledgepackage installed in the caller's workspace. If it is not present, the skill surfaces the missing dependency as an unknown rather than failing. - Awareness of the project's downstream LWC authoring flow — this skill hands off a PRD to that flow but does not invoke it.
Core Principles
Apply the Aura → LWC migration principles before and during each phase: understand before converting, prioritize functionality equivalence over structural equivalence, leverage native web standards, migrate iteratively, and test thoroughly. The architectural deltas (two-way → one-way binding, Aura events → DOM events, aura:id → this.template.querySelector, etc.) are documented in references/aura-migration-guidelines.md.
What ships with it
11 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-api-expert.md 8.4 KB
- references/aura-data-expert.md 13 KB
- references/aura-migration-guidelines.md 8.2 KB
- references/aura-prd-framework.md 3.7 KB
- references/aura-redundant-code-expert.md 1.5 KB
- references/aura-reference-expert.md 9.3 KB
- references/aura-resolver-expert.md 5.8 KB
- references/aura-slots-expert.md 3.1 KB
- references/aura-style-expert.md 2.4 KB
- references/aura-to-lwc-completeness-checklist.md 7.9 KB
- references/aura-values-expert.md 2.5 KB
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 · 122 lines · 243 tokens per session scan A c0a8275edc97
experience-aura-lwc-migrate is a skill published in the GitHub repository forcedotcom/sf-skills (1,128 stars, last pushed yesterday), licensed Apache-2.0. It adds 243 tokens to every session and 3,260 once invoked, about $0.0010 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-08-30.
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…