Skip to content
Back to search

salesforce

MarketplaceWorks with Claude CodeGitHub

Salesforce Headless 360 — Salesforce agent skills marketplace.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/forcedotcom/sf-skills with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/forcedotcom/sf-skills'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/forcedotcom-sf-skills/badge.svg)](/listings/forcedotcom-sf-skills)

HTML

<a href="/listings/forcedotcom-sf-skills"><img src="/api/listings/forcedotcom-sf-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 1,105 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "salesforce",
  3. "version": "1.0.0",
  4. "description": "Salesforce Headless 360 — Salesforce agent skills marketplace.",
  5. "owner": {
  6. "name": "Salesforce"
  7. },
  8. "plugins": [
  9. {
  10. "name": "education-cloud",
  11. "source": "./plugins/builder/education-cloud",
  12. "description": "Configure Salesforce Education Cloud domains; generate academic years, semester terms, sessions and registration windows; migrate courses into LearningCourse records; configure multi-campus institutional hierarchies and BusinessProfile records; set up the packaged StudentRecruitmentAgent for prospective-student admissions FAQs, campus tours and enrollment.",
  13. "keywords": [
  14. "education",
  15. "academic terms",
  16. "semester dates",
  17. "academic sessions",
  18. "registration windows",
  19. "LearningCourse",
  20. "multi campus",
  21. "institutional hierarchy",
  22. "BusinessProfile",
  23. "student enrollment",
  24. "StudentRecruitmentAgent",
  25. "education domains",
  26. "LearningCourse migration",
  27. "academic calendar"
  28. ],
  29. "metadata": {
  30. "match": {
  31. "examplePrompts": [
  32. "Set up education domains for admissions",
  33. "Generate academic years, semester terms and sessions",
  34. "Import university courses into LearningCourse records",
  35. "Configure a multi-campus institutional hierarchy and BusinessProfile records",
  36. "Enable StudentRecruitmentAgent admissions FAQs and campus tours for prospective students",
  37. "Set up student enrollment"
  38. ],
  39. "anchorTerms": [
  40. "education",
  41. "academic",
  42. "semester",
  43. "institutional",
  44. "learningcourse",
  45. "businessprofile",
  46. "studentrecruitmentagent",
  47. "hierarchy",
  48. "student"
  49. ],
  50. "anchorCompanions": {
  51. "education": [
  52. "domain",
  53. "domains",
  54. "student",
  55. "course",
  56. "courses",
  57. "catalog"
  58. ],
  59. "academic": [
  60. "year",
  61. "years",
  62. "terms",
  63. "sessions",
  64. "registration"
  65. ],
  66. "semester": [
  67. "terms",
  68. "dates"
  69. ],
  70. "institutional": [
  71. "education",
  72. "businessprofile",
  73. "learningcourse"
  74. ],
  75. "hierarchy": [
  76. "multi",
  77. "education",
  78. "businessprofile",
  79. "learningcourse"
  80. ],
  81. "student": [
  82. "enrollment"
  83. ]
  84. },
  85. "enforceAnchorsOnAllSurfaces": true
  86. }
  87. }
  88. },
  89. {
  90. "name": "salesforce-development",
  91. "source": "./plugins/builder/salesforce-development",
  92. "description": "Foundation layer for Salesforce platform development — 38 skills for environment validation, project scaffolding, scratch-org lifecycle, declarative metadata, Apex (author, run anonymous, test, debug), flow automation, SOQL, deploy/retrieve, manifest generation, security, reporting, and generated installed-versus-available capability discovery, plus org-context detection, a production deploy-safety gate, and a bundled Apex + SOQL language server (MCP).",
  93. "keywords": [
  94. "salesforce",
  95. "apex",
  96. "flow",
  97. "soql",
  98. "metadata",
  99. "deploy",
  100. "security"
  101. ],
  102. "metadata": {
  103. "match": {
  104. "examplePrompts": [
  105. "build a flow",
  106. "deploy my metadata",
  107. "run apex tests"
  108. ],
  109. "anchorTerms": [
  110. "apex",
  111. "flow",
  112. "metadata",
  113. "deploy"
  114. ]
  115. }
  116. }
  117. },
  118. {
  119. "name": "salesforce-code-quality",
  120. "source": "./plugins/builder/salesforce-code-quality",
  121. "description": "Analyze and govern Salesforce code quality with Salesforce Code Analyzer and the Well-Architected framework: set up and troubleshoot Code Analyzer, run security/performance/best-practice/style scans across engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), author custom Regex/PMD/ESLint rules, and run a multi-pillar Well-Architected architecture review with file:line evidence. Use for static analysis, code scanning, quality gates, custom lint rules, or a holistic architecture/Well-Architected audit — includes a read-only architecture-review agent.",
  122. "keywords": [
  123. "salesforce code analyzer",
  124. "static analysis",
  125. "code scan",
  126. "pmd",
  127. "eslint",
  128. "sfge",
  129. "apexguru",
  130. "retirejs",
  131. "cpd",
  132. "custom rule",
  133. "quality gate",
  134. "well-architected",
  135. "architecture review",
  136. "code quality"
  137. ],
  138. "metadata": {
  139. "match": {
  140. "examplePrompts": [
  141. "set up Salesforce Code Analyzer for my project",
  142. "scan my Apex code for security violations",
  143. "run PMD and ESLint on my code",
  144. "create a custom PMD rule to ban System.debug",
  145. "run a Well-Architected review of my project",
  146. "audit this project's architecture"
  147. ],
  148. "anchorTerms": [
  149. "analyzer",
  150. "pmd",
  151. "sfge",
  152. "apexguru",
  153. "retirejs",
  154. "cpd",
  155. "architecture",
  156. "architected",
  157. "violations"
  158. ]
  159. }
  160. }
  161. },
  162. {
  163. "name": "agentforce-adlc",
  164. "source": "./plugins/builder/agentforce-adlc",
  165. "description": "Author, discover, scaffold, deploy, test, secure, and optimize Agentforce .agent files",
  166. "keywords": [
  167. "agentforce",
  168. "agent",
  169. "adlc",
  170. ".agent",
  171. "voice agent",
  172. "employee agent"
  173. ],
  174. "metadata": {
  175. "match": {
  176. "examplePrompts": [
  177. "build me a service agent",
  178. "create an employee agent",
  179. "author an .agent definition"
  180. ],
  181. "anchorTerms": [
  182. "agentforce",
  183. "agent",
  184. "adlc"
  185. ]
  186. }
  187. }
  188. },
  189. {
  190. "name": "salesforce-test-drive",
  191. "source": "./plugins/builder/salesforce-test-drive",
  192. "description": "Take a Salesforce capability for a test drive — pick a curated end-to-end build from a menu (e.g. a Service help agent delivered as a website chat widget) and watch it run start to finish. A guided, rehearsable walkthrough and learning engine that checks readiness, helps connect or provision an org, then choreographs the salesforce-development skills to build the real thing.",
  193. "keywords": [
  194. "guided walkthrough",
  195. "rehearsable build",
  196. "curated end-to-end build",
  197. "capability learning engine",
  198. "service help agent",
  199. "website chat widget",
  200. "readiness check"
  201. ],
  202. "metadata": {
  203. "match": {
  204. "examplePrompts": [
  205. "give me a guided walkthrough of building a Service help agent",
  206. "walk me through an end-to-end build of a website chat widget",
  207. "show me a rehearsable end-to-end Salesforce build I can follow",
  208. "curated end-to-end build of a Service help agent chat widget"
  209. ],
  210. "anchorTerms": [
  211. "drive",
  212. "walkthrough",
  213. "rehearsable"
  214. ],
  215. "anchorCompanions": {
  216. "drive": [
  217. "test"
  218. ]
  219. },
  220. "entryCommand": "/salesforce-test-drive:start"
  221. }
  222. }
  223. },
  224. {
  225. "name": "experience-lwc",
  226. "source": "./plugins/builder/experience-lwc",
  227. "description": "Build and validate Lightning Web Components (LWC): generate components with the PICKLES methodology and 165-point scoring, scaffold a fresh LWC from a Figma design or a PRD, wire-service and Jest test patterns, SLDS styling, WCAG/ARIA accessibility validation, and RTL/TypeScript migration. Use when creating, editing, or reviewing LWC components — touching lwc/**/*.js, .html, .css, or .js-meta.xml files, or asking about wire service, base components, SLDS, Jest LWC tests, or component accessibility. Also use when migrating legacy Aura components or Lightning Out apps to LWC.",
  228. "keywords": [
  229. "lwc",
  230. "lightning web component",
  231. "aura migration",
  232. "lightning out",
  233. "wire service",
  234. "jest",
  235. "slds",
  236. "wcag",
  237. "aria",
  238. "figma",
  239. "accessibility"
  240. ],
  241. "metadata": {
  242. "match": {
  243. "examplePrompts": [
  244. "build me an LWC datatable",
  245. "create a lightning web component",
  246. "convert this Figma design into an LWC",
  247. "make my component WCAG accessible",
  248. "migrate this Aura component or Lightning Out app to LWC"
  249. ],
  250. "anchorTerms": [
  251. "lwc"
  252. ]
  253. }
  254. }
  255. },
  256. {
  257. "name": "experience-react",
  258. "source": "./plugins/builder/experience-react",
  259. "description": "Build Salesforce React UI Bundle apps: scaffold a new React UI bundle SFDX starter project from a template, generate and edit pages, components, layout, styling, navigation, and branding with shadcn/ui and Tailwind CSS, configure ui-bundle metadata, host the app on a Digital Experience Site, and deploy it to an org. Use when creating or editing a React frontend under uiBundles/*/src for a Salesforce site — appLayout.tsx, routes.tsx, src/pages/, src/components/, or when starting, scaffolding, hosting, or deploying a React UI bundle app. Also scaffold, configure features for, host, and deploy Angular UI Bundle apps.",
  260. "keywords": [
  261. "react",
  262. "angular",
  263. "ui bundle",
  264. "tsx",
  265. "tailwind",
  266. "shadcn",
  267. "digital experience site",
  268. "sfdx starter"
  269. ],
  270. "metadata": {
  271. "match": {
  272. "examplePrompts": [
  273. "scaffold a new React UI bundle app",
  274. "add a shadcn component to my tsx page",
  275. "build a Digital Experience site with React",
  276. "scaffold a Salesforce Angular UI bundle app"
  277. ],
  278. "anchorTerms": [
  279. "react",
  280. "angular",
  281. "shadcn",
  282. "tsx"
  283. ],
  284. "anchorCompanions": {
  285. "angular": [
  286. "ui",
  287. "bundle",
  288. "frontend",
  289. "experience",
  290. "site"
  291. ]
  292. }
  293. }
  294. }
  295. },
  296. {
  297. "name": "experience-cms",
  298. "source": "./plugins/builder/experience-cms",
  299. "description": "Author and source media for Experience Cloud content: apply CMS branding, generate CMS content, search existing Salesforce CMS or Data 360 media, and search and download ethically licensed stock imagery through Salesforce media-management tooling. Use when producing or branding CMS content for a Digital Experience site, locating an existing content asset, or finding a stock image for a page. Also render accessible CMS-managed images, video, audio, and documents in React experiences.",
  300. "keywords": [
  301. "cms",
  302. "experience cloud",
  303. "content",
  304. "branding",
  305. "media search",
  306. "media rendering",
  307. "stock image",
  308. "digital experience"
  309. ],
  310. "metadata": {
  311. "match": {
  312. "examplePrompts": [
  313. "generate CMS content for my site",
  314. "apply my brand to the Experience Cloud site",
  315. "find a stock image for this page",
  316. "search Salesforce CMS for an existing media asset",
  317. "render CMS images and video accessibly in my React site"
  318. ],
  319. "anchorTerms": [
  320. "cms",
  321. "media",
  322. "stock",
  323. "image",
  324. "brand"
  325. ]
  326. }
  327. }
  328. },
  329. {
  330. "name": "dx-org-lifecycle",
  331. "source": "./plugins/builder/dx-org-lifecycle",
  332. "description": "Administer Salesforce environments, Dev Hubs, and sandbox lifecycle: manage or inspect Dev Hub status and scratch allocation, configure and refresh sandboxes, run post-copy automation, provision trials, inspect expiration, assign permission sets, and set the default target. Use for environment setup and maintenance, especially Dev Hub administration, sandbox refresh, post-copy configuration, time-limited provisioning, access assignment, or target selection.",
  333. "keywords": [
  334. "salesforce environment lifecycle",
  335. "dev hub",
  336. "scratch allocation",
  337. "scratch limits",
  338. "salesforce sandbox",
  339. "sandbox refresh",
  340. "sandbox post copy",
  341. "post copy config",
  342. "temporary environment provisioning",
  343. "expiration check",
  344. "permission set assignment",
  345. "default target",
  346. "target selection"
  347. ],
  348. "metadata": {
  349. "match": {
  350. "examplePrompts": [
  351. "inspect Dev Hub status and show my scratch allocation",
  352. "configure post-copy steps for my Salesforce sandbox refresh",
  353. "create a Salesforce trial environment for this demo",
  354. "switch my default Salesforce target",
  355. "assign a Salesforce permission set to a user"
  356. ],
  357. "anchorTerms": [
  358. "sandbox",
  359. "scratch",
  360. "trial",
  361. "environment",
  362. "permission",
  363. "default",
  364. "target"
  365. ]
  366. }
  367. }
  368. },
  369. {
  370. "name": "dx-devops",
  371. "source": "./plugins/builder/dx-devops",
  372. "description": "Operate Salesforce DevOps Center pipelines and work items and configure their automated testing: manage pipeline definitions and work items, configure test pipelines and suite assignments, run stage test suites, and analyze test failures. Use for DevOps Center pipeline administration, work-item tracking, test-stage configuration, suite execution, quality-gate reruns, or pipeline failure analysis.",
  373. "keywords": [
  374. "devops center",
  375. "devops pipeline",
  376. "work item",
  377. "test pipeline",
  378. "test suite",
  379. "suite assignment",
  380. "quality gate",
  381. "pipeline test failure",
  382. "pipeline stage"
  383. ],
  384. "metadata": {
  385. "match": {
  386. "examplePrompts": [
  387. "configure a DevOps Center test pipeline",
  388. "run the test suite for this DevOps Center pipeline stage",
  389. "analyze why my DevOps Center pipeline tests failed",
  390. "manage a DevOps Center work item",
  391. "assign test suites to a DevOps Center stage"
  392. ],
  393. "anchorTerms": [
  394. "devops",
  395. "pipeline"
  396. ]
  397. }
  398. }
  399. },
  400. {
  401. "name": "platform-trust-security",
  402. "source": "./plugins/builder/platform-trust-security",
  403. "description": "Protect and govern Salesforce data with Shield Platform Encryption and Salesforce Archive: configure encrypted fields and key-management options, search or restore archived records, monitor ArchiveActivity jobs, analyze retained storage, and mask or erase archived data. Use for encryption metadata and guidance or trusted-services archival and retention workflows.",
  404. "keywords": [
  405. "shield platform encryption",
  406. "encrypted field",
  407. "encryption key management",
  408. "byok",
  409. "external key management",
  410. "trusted services archival",
  411. "archived records",
  412. "archiveactivity",
  413. "archival retention",
  414. "archived pii"
  415. ],
  416. "metadata": {
  417. "match": {
  418. "examplePrompts": [
  419. "configure deterministic Shield Platform Encryption for a new Salesforce field",
  420. "compare BYOK with external key management for Platform Encryption",
  421. "search archived Salesforce records by retention criteria",
  422. "restore archived records with the data-resilience API",
  423. "monitor ArchiveActivity jobs and download their failure logs"
  424. ],
  425. "anchorTerms": [
  426. "shield",
  427. "encryption",
  428. "encrypted",
  429. "byok",
  430. "archival",
  431. "archived",
  432. "archiveactivity"
  433. ]
  434. }
  435. }
  436. },
  437. {
  438. "name": "commerce-b2b",
  439. "source": "./plugins/builder/commerce-b2b",
  440. "description": "Customize an existing Salesforce B2B Commerce storefront with the Salesforce Open Code storefront library: bring the official open-source library into site metadata, map out-of-the-box commerce definitions to storefront equivalents, and swap selected definitions. Use for B2B Commerce library integration, mapping lookup, or replacement work in storefront site metadata.",
  441. "keywords": [
  442. "salesforce b2b commerce",
  443. "b2b storefront",
  444. "b2b open code",
  445. "b2b open source library",
  446. "commerce definition mapping",
  447. "ootb mapping",
  448. "site definition replacement",
  449. "storefront site metadata"
  450. ],
  451. "metadata": {
  452. "match": {
  453. "examplePrompts": [
  454. "integrate Salesforce Open Code into a new local copy of my B2B Commerce storefront",
  455. "bring the official B2B Commerce open-source library into storefront site metadata",
  456. "replace OOTB B2B Commerce definitions with mapped site equivalents",
  457. "map this commerce storefront definition to its equivalent"
  458. ],
  459. "anchorTerms": [
  460. "b2b",
  461. "commerce",
  462. "storefront"
  463. ]
  464. }
  465. }
  466. },
  467. {
  468. "name": "mobile-development",
  469. "source": "./plugins/builder/mobile-development",
  470. "description": "Build and extend native Salesforce mobile apps on iOS and Android. Bundles skills for scaffolding new Mobile SDK apps, adding Mobile SDK to existing apps, Salesforce authentication, offline storage (SmartStore) and sync (MobileSync), biometric login, native device capabilities, and embedding Agentforce.",
  471. "keywords": [
  472. "salesforce mobile sdk",
  473. "mobile sdk scaffolding",
  474. "salesforce mobile authentication",
  475. "smartstore offline storage",
  476. "mobilesync",
  477. "biometric login",
  478. "native device capability",
  479. "barcode scanner",
  480. "geolocation",
  481. "nfc",
  482. "document scanner",
  483. "mobile offline",
  484. "komaci",
  485. "offline priming",
  486. "komaci graph analyzer",
  487. "mobileappplus",
  488. "fieldservicemobile",
  489. "agentforce mobile sdk",
  490. "embed agentforce mobile"
  491. ],
  492. "metadata": {
  493. "match": {
  494. "examplePrompts": [
  495. "add a new barcode scanning flow with lightning mobile capabilities",
  496. "add biometric authentication to Salesforce mobile",
  497. "review Salesforce mobile offline behavior with Komaci",
  498. "run a Komaci offline priming audit",
  499. "build a Salesforce iOS app with Mobile SDK",
  500. "add Mobile SDK to my existing Android app",
  501. "add MobileSync and SmartStore offline storage to my mobile app",
  502. "embed an Agentforce agent in my iOS mobile app"
  503. ],
  504. "anchorTerms": [
  505. "mobile",
  506. "barcode",
  507. "biometric",
  508. "komaci",
  509. "offline",
  510. "sdk",
  511. "smartstore",
  512. "mobilesync"
  513. ]
  514. }
  515. }
  516. },
  517. {
  518. "name": "platform-observability",
  519. "source": "./plugins/builder/platform-observability",
  520. "description": "Configure Salesforce tracing metadata: generate EventSettings that turn TraceSpanEvent publishing on or off, and generate AgentforcePlatformTracingSettings that forward execution spans into the required Data Cloud ingestion pipeline. Use for API 68 tracing preferences and the two singleton metadata types that control span publication and ingestion.",
  521. "keywords": [
  522. "platformtracing",
  523. "tracespanevent",
  524. "enableplatformtracing",
  525. "event settings tracing",
  526. "agentforceplatformtracingsettings",
  527. "execution spans",
  528. "platform observability",
  529. "span ingestion"
  530. ],
  531. "metadata": {
  532. "match": {
  533. "examplePrompts": [
  534. "turn on TraceSpanEvent publishing with enablePlatformTracing",
  535. "generate new EventSettings metadata for enablePlatformTracing",
  536. "forward execution spans with AgentforcePlatformTracingSettings",
  537. "generate AgentforcePlatformTracingSettings metadata"
  538. ],
  539. "anchorTerms": [
  540. "tracing",
  541. "enableplatformtracing",
  542. "agentforceplatformtracingsettings"
  543. ]
  544. }
  545. }
  546. },
  547. {
  548. "name": "dx-isv-partner",
  549. "source": "./plugins/builder/dx-isv-partner",
  550. "description": "Support focused Salesforce ISV and partner operations: submit AppAnalyticsQueryRequest records for PackageUsageSummary or SubscriberSnapshot data, configure AppAnalyticsSettings, and set TransactableMarketplaceReceivePartnerOffers for partner-offer reception. Use for managed-package telemetry requests or partner-offer preference changes.",
  551. "keywords": [
  552. "salesforce isv",
  553. "appexchange partner",
  554. "appanalyticsqueryrequest",
  555. "packageusagesummary",
  556. "subscriber snapshot",
  557. "managed package telemetry",
  558. "transactable marketplace",
  559. "transactable marketplace receive partner offers",
  560. "partner offer preference"
  561. ],
  562. "metadata": {
  563. "match": {
  564. "examplePrompts": [
  565. "retrieve PackageUsageSummary for my managed package with AppAnalyticsQueryRequest",
  566. "request a SubscriberSnapshot with AppAnalyticsQueryRequest",
  567. "configure AppAnalyticsSettings for managed-package telemetry",
  568. "set TransactableMarketplaceReceivePartnerOffers to true"
  569. ],
  570. "anchorTerms": [
  571. "isv",
  572. "appexchange",
  573. "appanalyticsqueryrequest",
  574. "appanalyticssettings",
  575. "packageusagesummary",
  576. "subscribersnapshot",
  577. "transactablemarketplacereceivepartneroffers"
  578. ]
  579. }
  580. }
  581. },
  582. {
  583. "name": "service-engagement",
  584. "source": "./plugins/builder/service-engagement",
  585. "description": "Configure Service Cloud digital engagement channels: set up messaging and web chat channels, configure channel deployments, and connect an existing Agentforce channel binding. Use when setting up messaging, web chat, digital engagement deployments, or messaging-site integration.",
  586. "keywords": [
  587. "digital engagement",
  588. "messaging channel",
  589. "web chat",
  590. "engagement channel",
  591. "channel deployment",
  592. "MIAW"
  593. ],
  594. "metadata": {
  595. "match": {
  596. "examplePrompts": [
  597. "set up a Salesforce Digital Engagement messaging channel",
  598. "configure a Service Cloud web chat deployment",
  599. "integrate a messaging site with my Salesforce service org"
  600. ],
  601. "anchorTerms": [
  602. "engagement",
  603. "messaging",
  604. "chat",
  605. "channel",
  606. "miaw"
  607. ]
  608. }
  609. }
  610. },
  611. {
  612. "name": "integration",
  613. "source": "./plugins/builder/integration",
  614. "description": "Build Salesforce integrations and event-driven flows: generate connectivity (Named Credentials, External Services, REST/SOAP callouts), configure a Connected App or External Client App for secure OAuth, configure Change Data Capture, and configure event subscriptions. Use when wiring external systems or event-driven architecture — connectivity, connected apps and OAuth, CDC, or event subscription configuration.",
  615. "keywords": [
  616. "integration",
  617. "connectivity",
  618. "connected app",
  619. "oauth",
  620. "external client app",
  621. "change data capture",
  622. "cdc",
  623. "event subscription",
  624. "event driven"
  625. ],
  626. "metadata": {
  627. "match": {
  628. "examplePrompts": [
  629. "configure a Salesforce Connected App for OAuth",
  630. "enable Change Data Capture for Account",
  631. "configure a Salesforce platform event subscription",
  632. "set up connectivity to an external system",
  633. "wire an event-driven Salesforce integration"
  634. ],
  635. "anchorTerms": [
  636. "integration",
  637. "connectivity",
  638. "oauth",
  639. "connected",
  640. "cdc",
  641. "capture",
  642. "subscription",
  643. "event"
  644. ]
  645. }
  646. }
  647. },
  648. {
  649. "name": "platform-lightning-widgets",
  650. "source": "./plugins/builder/platform-lightning-widgets",
  651. "description": "Build Lightning Types and Agentforce action widgets: generate type definitions, coordinate Apex-backed widgets and MCP tool result widgets, and generate rich display widgets for these actions. Use when defining a Lightning Type or coordinating its widget for an Agentforce/MCP action.",
  652. "keywords": [
  653. "lightning type",
  654. "widget",
  655. "mcp tool widget",
  656. "action widget",
  657. "rich display",
  658. "HXL widget"
  659. ],
  660. "metadata": {
  661. "match": {
  662. "examplePrompts": [
  663. "generate a custom Salesforce Lightning Type",
  664. "build an MCP tool widget for this Agentforce action",
  665. "create a rich display widget for a Lightning Type"
  666. ],
  667. "anchorTerms": [
  668. "widget",
  669. "type"
  670. ]
  671. }
  672. }
  673. },
  674. {
  675. "name": "service-omni",
  676. "source": "./plugins/builder/service-omni",
  677. "description": "Configure Salesforce Omni-Channel work routing: queues, presence statuses, agent capacity, Case and VoiceCall routing flows, skills-based and attribute routing, agent work sharing, classic Omni Supervisor surface setup, and read-only Omni Command Center readiness analysis.",
  678. "keywords": [
  679. "omni routing",
  680. "queue routing",
  681. "presence status",
  682. "agent capacity",
  683. "skills-based routing",
  684. "omni supervisor",
  685. "attribute routing",
  686. "agent work sharing",
  687. "route Cases",
  688. "route VoiceCall"
  689. ],
  690. "metadata": {
  691. "match": {
  692. "examplePrompts": [
  693. "Set up Omni queues and presence statuses",
  694. "configure Omni skills-based routing for Cases",
  695. "deploy an Omni routing flow for VoiceCall",
  696. "configure classic Omni Supervisor queues and users",
  697. "analyze Omni Command Center readiness",
  698. "Configure Salesforce voice call routing"
  699. ],
  700. "anchorTerms": [
  701. "omni",
  702. "routing",
  703. "presence",
  704. "supervisor",
  705. "case",
  706. "cases",
  707. "voicecall",
  708. "queue",
  709. "queues",
  710. "capacity",
  711. "sharing"
  712. ],
  713. "anchorCompanions": {
  714. "omni": [
  715. "routing",
  716. "queue",
  717. "queues",
  718. "presence",
  719. "capacity",
  720. "supervisor",
  721. "readiness",
  722. "channel",
  723. "channels",
  724. "work",
  725. "sidebar",
  726. "skills",
  727. "permission",
  728. "permissions",
  729. "users",
  730. "agents",
  731. "center"
  732. ],
  733. "routing": [
  734. "omni",
  735. "case",
  736. "cases",
  737. "voicecall",
  738. "salesforce"
  739. ],
  740. "presence": [
  741. "omni",
  742. "salesforce"
  743. ],
  744. "supervisor": [
  745. "omni",
  746. "salesforce"
  747. ],
  748. "case": [
  749. "routing",
  750. "route"
  751. ],
  752. "cases": [
  753. "routing",
  754. "route"
  755. ],
  756. "voicecall": [
  757. "routing",
  758. "route"
  759. ],
  760. "queue": [
  761. "omni"
  762. ],
  763. "queues": [
  764. "omni"
  765. ],
  766. "capacity": [
  767. "omni",
  768. "agent",
  769. "agents"
  770. ],
  771. "sharing": [
  772. "work"
  773. ]
  774. },
  775. "enforceAnchorsOnAllSurfaces": true
  776. }
  777. }
  778. },
  779. {
  780. "name": "consumer-goods",
  781. "source": "./plugins/builder/consumer-goods",
  782. "description": "Set up Consumer Goods Cloud Trade Promotion Management (TPM) liability accruals and its summary Lightning component, plus Trade Promotion Effectiveness (TPE): deploy accrual and TPE data kits, configure Real Time Reporting (RTR) promotion-measure export to Data Cloud, prepare TPE dashboards and optional custom KPI measures, and manage supported Consumer Goods sync configurations and user assignments.",
  783. "keywords": [
  784. "Consumer Goods Cloud TPM",
  785. "TPM liability accruals",
  786. "TPM accrual data kit",
  787. "TPM accrual Lightning component setup",
  788. "Trade Promotion Effectiveness TPE",
  789. "TPE data kit deployment",
  790. "TPE dashboard setup",
  791. "TPE custom KPI measures",
  792. "RTR promotion measure export",
  793. "TPM Data Cloud export",
  794. "CG Cloud sync management",
  795. "Consumer Goods sync configuration"
  796. ],
  797. "metadata": {
  798. "match": {
  799. "examplePrompts": [
  800. "Deploy the Consumer Goods TPM liability accrual data kit and schedule its accrual chain",
  801. "Set up the TPE data kit and Trade Promotion Effectiveness dashboards",
  802. "Configure custom KPI measures for our TPE dashboards",
  803. "Set up the RTR export of TPM promotion measures to Data Cloud for TPE",
  804. "Configure Consumer Goods sync management and assign users to a sync configuration",
  805. "Set up trade promotion management liability accruals",
  806. "Set up real time reporting export from Consumer Goods Cloud to Data Cloud",
  807. "Create custom KPIs for TPE dashboards",
  808. "Set up TPE",
  809. "Set up CG Cloud"
  810. ],
  811. "anchorTerms": [
  812. "consumer",
  813. "cg",
  814. "tpm",
  815. "tpe",
  816. "rtr",
  817. "cgcloud",
  818. "trade",
  819. "promotion",
  820. "promotions",
  821. "accrual",
  822. "accruals",
  823. "kpis"
  824. ],
  825. "anchorCompanions": {
  826. "consumer": [
  827. "tpe",
  828. "rtr",
  829. "liability",
  830. "accruals",
  831. "sync",
  832. "measure",
  833. "datakit",
  834. "kit",
  835. "kpi",
  836. "component",
  837. "reporting",
  838. "effectiveness",
  839. "kpis"
  840. ],
  841. "cg": [
  842. "sync",
  843. "tpe",
  844. "effectiveness",
  845. "datakit",
  846. "kit",
  847. "kpis",
  848. "cg cloud"
  849. ],
  850. "tpm": [
  851. "accruals",
  852. "liability",
  853. "datakit",
  854. "data",
  855. "kit",
  856. "tpe",
  857. "dashboard",
  858. "sync",
  859. "component",
  860. "export"
  861. ],
  862. "rtr": [
  863. "promotion",
  864. "measure",
  865. "export",
  866. "tpe",
  867. "tpm"
  868. ],
  869. "cgcloud": [
  870. "sync",
  871. "tpe",
  872. "accruals",
  873. "liability",
  874. "datakit",
  875. "export",
  876. "dashboard",
  877. "kpi",
  878. "measure"
  879. ],
  880. "trade": [
  881. "effectiveness",
  882. "management",
  883. "accrual",
  884. "accruals"
  885. ],
  886. "promotion": [
  887. [
  888. "trade",
  889. "effectiveness"
  890. ],
  891. [
  892. "trade",
  893. "management"
  894. ],
  895. [
  896. "trade",
  897. "accrual"
  898. ],
  899. [
  900. "trade",
  901. "accruals"
  902. ]
  903. ],
  904. "promotions": [
  905. [
  906. "trade",
  907. "effectiveness"
  908. ],
  909. [
  910. "trade",
  911. "management"
  912. ],
  913. [
  914. "trade",
  915. "accrual"
  916. ],
  917. [
  918. "trade",
  919. "accruals"
  920. ]
  921. ],
  922. "accrual": [
  923. "trade",
  924. "promotions",
  925. "tpm",
  926. "cgcloud"
  927. ],
  928. "accruals": [
  929. "trade",
  930. "promotions",
  931. "tpm",
  932. "cgcloud"
  933. ],
  934. "kpis": [
  935. "tpe",
  936. "tpm",
  937. "cgcloud"
  938. ]
  939. },
  940. "enforceAnchorsOnAllSurfaces": true
  941. }
  942. }
  943. },
  944. {
  945. "name": "service-itsm",
  946. "source": "./plugins/builder/service-itsm",
  947. "description": "Set up Agentforce for IT Service: enable Studio, configure Employee and Fulfiller agents, assign ITSM permissions, and grant runtime access.",
  948. "keywords": [
  949. "Agentforce for IT Service",
  950. "ITSM Agentforce setup",
  951. "Employee and Fulfiller agents",
  952. "ITSM permissions",
  953. "Agentforce runtime access"
  954. ],
  955. "metadata": {
  956. "match": {
  957. "examplePrompts": [
  958. "Set up Agentforce for IT Service",
  959. "Enable IT Service Agentforce Studio",
  960. "Configure Employee agent for IT Service",
  961. "Configure Fulfiller agent for IT Service",
  962. "Assign ITSM Agentforce permissions",
  963. "Assign IT Service Agentforce runtime access",
  964. "Validate Agentforce Studio prerequisites for IT Service in Lightning Experience"
  965. ],
  966. "anchorTerms": [
  967. "agentforce",
  968. "itsm",
  969. "fulfiller",
  970. "studio",
  971. "employee",
  972. "runtime"
  973. ],
  974. "anchorCompanions": {
  975. "agentforce": [
  976. "itsm",
  977. "it service"
  978. ],
  979. "studio": [
  980. "itsm",
  981. "it service"
  982. ],
  983. "employee": [
  984. [
  985. "itsm",
  986. "agent"
  987. ],
  988. [
  989. "itsm",
  990. "agents"
  991. ],
  992. [
  993. "it service",
  994. "agent"
  995. ],
  996. [
  997. "it service",
  998. "agents"
  999. ]
  1000. ],
  1001. "runtime": [
  1002. [
  1003. "itsm",
  1004. "agent"
  1005. ],
  1006. [
  1007. "itsm",
  1008. "agents"
  1009. ],
  1010. [
  1011. "it service",
  1012. "agent"
  1013. ],
  1014. [
  1015. "it service",
  1016. "agents"
  1017. ]
  1018. ],
  1019. "itsm": [
  1020. "agentforce",
  1021. "studio",
  1022. "fulfiller",
  1023. [
  1024. "employee",
  1025. "agent"
  1026. ],
  1027. [
  1028. "employee",
  1029. "agents"
  1030. ],
  1031. [
  1032. "runtime",
  1033. "agent"
  1034. ],
  1035. [
  1036. "runtime",
  1037. "agents"
  1038. ]
  1039. ]
  1040. },
  1041. "enforceAnchorsOnAllSurfaces": true
  1042. }
  1043. }
  1044. },
  1045. {
  1046. "name": "dx-packaging",
  1047. "source": "./plugins/builder/dx-packaging",
  1048. "description": "Set up managed packages after installation, operate subscriber push upgrades, and finalize the 2GP cutover for converted 1GP managed packages: automate configuration after installation, plan and schedule controlled rollouts, monitor or abort package push jobs across subscriber fleets, and check eligibility and plan the 2GP cutover, which is finalized only after explicit confirmation.",
  1049. "keywords": [
  1050. "salesforce packaging",
  1051. "managed package",
  1052. "package post install",
  1053. "package setup",
  1054. "push upgrade",
  1055. "subscriber org",
  1056. "package rollout",
  1057. "2gp cutover",
  1058. "2gp",
  1059. "unlocked package"
  1060. ],
  1061. "metadata": {
  1062. "match": {
  1063. "examplePrompts": [
  1064. "finish setup for this managed package after installation",
  1065. "set package permissions and layouts after installing LMA",
  1066. "plan a batched push upgrade for my package subscribers",
  1067. "monitor this PackagePushRequest",
  1068. "abort a scheduled package push upgrade",
  1069. "finalize the 2GP cutover for my converted 1GP managed package",
  1070. "check whether my converted 1GP package is eligible for the 2GP cutover",
  1071. "plan the 2GP cutover for my converted managed package"
  1072. ],
  1073. "anchorTerms": [
  1074. "post",
  1075. "push",
  1076. "installing",
  1077. "lma",
  1078. "fma",
  1079. "packagepushrequest",
  1080. "packagesubscriber",
  1081. "2gp"
  1082. ],
  1083. "anchorCompanions": {
  1084. "post": [
  1085. "install"
  1086. ],
  1087. "push": [
  1088. "upgrade"
  1089. ],
  1090. "installing": [
  1091. "package"
  1092. ],
  1093. "2gp": [
  1094. "move",
  1095. "moves",
  1096. "moved",
  1097. "moving",
  1098. "cutover"
  1099. ]
  1100. }
  1101. }
  1102. }
  1103. }
  1104. ]
  1105. }
README.md · README · 123 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Salesforce Skills and Plugins Library
  2. This repository provides Salesforce agent skills, plugins, and sample apps for building applications. It includes skills for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components (LWC), UI bundles, objects and fields, permission sets, and related areas. The [builder plugins](plugins/builder/) package skills with additional capabilities such as agents, hooks, commands, and Model Context Protocol (MCP) servers. Each client loads the components supported by that plugin's manifest.
  3. The skills are contributed by Salesforce and the broader community. The skills library is optimized for Agentforce Vibes and can be used with any AI tool that supports skills. For guided Salesforce development, start with the [Salesforce Development plugin README](plugins/builder/salesforce-development/README.md) and the [Salesforce Development plugin documentation](https://developer.salesforce.com/docs/platform/salesforce-skills-plugins/guide/salesforce-development-overview.html).
  4. ## See the development workflow
  5. Go from a natural-language request to an app deployed in Salesforce. These short demos
  6. were recorded with Salesforce Development 2.5.0 and show a terminal workflow followed by the finished app.
  7. ![Claude Code building and deploying a Salesforce Lightning app](docs/media/development-demos/claude-salesforce-development-2.5.0.gif)
  8. | Demo | Length | Watch or download |
  9. |---|---:|---|
  10. | Claude Code: Lightning app | 35 seconds | [GIF](docs/media/development-demos/claude-salesforce-development-2.5.0.gif) · [MP4](docs/media/development-demos/claude-salesforce-development-2.5.0.mp4) |
  11. | Codex CLI: Lightning app | 30 seconds | [GIF](docs/media/development-demos/codex-salesforce-development-2.5.0.gif) · [MP4](docs/media/development-demos/codex-salesforce-development-2.5.0.mp4) |
  12. | Claude Code: internal React app | 32 seconds | [GIF](docs/media/development-demos/claude-react-salesforce-development-2.5.0.gif) · [MP4](docs/media/development-demos/claude-react-salesforce-development-2.5.0.mp4) |
  13. The Codex Lightning demo also uses Experience LWC 0.3.0; the React demo uses
  14. Experience React 0.2.1. The clips combine real terminal excerpts with captured views
  15. of the deployed apps. Accelerated terminal sections are labeled. All Account data
  16. shown is fictional. See the [recording notes](docs/media/development-demos/README.md).
  17. <details>
  18. <summary>Preview Codex CLI and React</summary>
  19. ### Codex CLI: Lightning app
  20. ![Codex CLI building and deploying a Salesforce Lightning app](docs/media/development-demos/codex-salesforce-development-2.5.0.gif)
  21. ### Claude Code: internal React app
  22. ![Claude Code building and deploying an internal Salesforce React app](docs/media/development-demos/claude-react-salesforce-development-2.5.0.gif)
  23. </details>
  24. > ⚠️ **Expect frequent changes.** The Salesforce skills and plugins library is evolving rapidly as we refine patterns and incorporate feedback. Skills and plugins may be renamed, restructured, or removed between releases — they do not follow the same stability guarantees as GA platform APIs. If you’ve forked or synced the repository, be prepared for upstream changes that may conflict with local modifications. This repository is always the source of truth.
  25. ## 🗂️ Structure
  26. ```
  27. sf-skills/
  28. ├── .claude-plugin/
  29. │ └── marketplace.json # Salesforce plugin marketplace catalog
  30. ├── plugins/
  31. │ └── builder/ # Plugins for Salesforce development
  32. │ ├── salesforce-development/
  33. │ └── ...
  34. ├── skills/ # Directory-based executable workflows
  35. │ ├── platform-apex-generate/
  36. │ ├── platform-custom-object-generate/
  37. │ ├── automation-flow-generate/
  38. │ └── ...
  39. ├── samples/ # Synced sample apps (e.g. from npm)
  40. │ └── ui-bundle-template-app-react-sample-b2e/
  41. │ └── ...
  42. ├── scripts/
  43. │ └── ...
  44. └── README.md
  45. ```
  46. ## 🚀 Usage
  47. | **Tool** | **Usage** |
  48. |----------|-------------|
  49. | **Agentforce Vibes** | Skills are auto-installed and auto-updated |
  50. | **Claude Code — Salesforce Development plugin** | Follow the [Claude Code installation guide](https://developer.salesforce.com/docs/platform/salesforce-skills-plugins/guide/install-salesforce-development.html) for skills, guided workflows, and integrated tools |
  51. | **Codex — Salesforce Development plugin** | Follow [Codex setup and requirements](plugins/builder/salesforce-development/README.md#codex-lifecycle-support); use a release containing the Codex manifests and Codex CLI 0.145.0 or later |
  52. | **OpenCode, Claude Code, Codex, Cursor, [more](https://agentskills.io/) — standalone skills** | `npx skills add forcedotcom/sf-skills` |
  53. ## 🔌 Plugins
  54. Plugins bundle skills with other components that the coding client installs and loads together. The Salesforce Development plugin provides shared workflows for building, testing, and deploying on the Salesforce Platform, with client-specific commands, hooks, and MCP configuration. Claude Code agents and hooks aren't automatically available in other clients. Specialized builder plugins add capabilities for areas such as Agentforce, code quality, LWC, and React development.
  55. - [Salesforce marketplace manifest](.claude-plugin/marketplace.json) — available plugins, descriptions, and source paths
  56. - [Salesforce Development plugin README](plugins/builder/salesforce-development/README.md) — prerequisites, quick start, and component inventory
  57. - [Salesforce Development plugin documentation](https://developer.salesforce.com/docs/platform/salesforce-skills-plugins/guide/salesforce-development-overview.html) — installation, project and org setup, workflows, and troubleshooting; use the plugin README for Codex-specific setup
  58. - [Claude Code plugin documentation](https://code.claude.com/docs/en/plugins) — plugin components and how plugins work
  59. Check the [plugin changelog](plugins/builder/salesforce-development/CHANGELOG.md) and installed version for release availability. Other clients, including Cursor, can use standalone skills where supported; full plugin support depends on the client and plugin manifest.
  60. ## 📦 Samples
  61. The `samples/` folder contains synced sample apps. For example, `samples/ui-bundle-template-app-react-sample-b2e/` tracks the npm package `@salesforce/ui-bundle-template-app-react-sample-b2e` (nightly and on manual trigger via GitHub Actions).
  62. To run the same sync locally from the repository root:
  63. ```bash
  64. npm install
  65. npm run sync-react-b2e-sample
  66. ```
  67. The GitHub Action runs the same commands and opens a pull request when the npm package version changes. For more information, see [samples/README.md](samples/README.md).
  68. ## 🛠️ Agent Skills
  69. Agent Skills package executable workflows, scripts, and reference material into self-contained directories. This repository follows the open [Agent Skills specification](https://agentskills.io/) and can be used with OpenCode, Claude Code, Codex, Cursor, and other tools that support skills.
  70. ### Directory Structure
  71. Each skill is a folder that can include:
  72. - `SKILL.md` (required): Instructions and YAML front matter.
  73. - `scripts/` (optional): Executable scripts (For example, Python, Bash, or JavaScript).
  74. - `references/` (optional): Extra reference documentation.
  75. - `assets/` (optional): Templates, schemas, and lookup data
  76. ## 🤝 Contributing
  77. See [Contributing](./CONTRIBUTING.md).
  78. ## 💬 Feedback
  79. - Open an issue in this repository
  80. - Open a pull request with suggested changes
  81. - Use GitHub Discussions or the pull request thread for broader conversation
  82. ## Project Governance & Support
  83. - [License](./LICENSE.txt)
  84. - [Code of Conduct](./CODE_OF_CONDUCT.md)
  85. - [Contributing](./CONTRIBUTING.md)
  86. - [Security](./SECURITY.md)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.