Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized capabilities for developers to track and advance work items through the DevOps pipeline. It streamlines the process of updating item metadata, committing code changes to dedicated branches, and initiating pull requests via the DevOps Center API.
By consolidating review operations and status transitions, it helps teams maintain a structured flow from initial creation to final code review without manual overhead.
WHO IT'S FOR
Salesforce B2B Commerce developers
integrate open source component libraries into stores
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Agentforce Vibes automatic installation
Installs: Complete Salesforce Skills Library; skills are automatically installed and updated. The listed paths are a bounded set of positively documented mappings, not the complete inventory. · Agentforce Vibes
Use Agentforce Vibes. The Salesforce skills are automatically installed and automatically updated; no terminal command is documented as necessary.
Installs: Complete forcedotcom/sf-skills repository bundle. The listed paths are a bounded set of positively documented mappings, not the complete inventory. · OpenCode, Claude Code, Codex, Cursor
Before you start
OpenCode, Claude Code, Codex, or Cursor with Agent Skills support
Run this command in a terminal to add the Salesforce Skills Library repository.
Replace <path-to-class.cls> with the path to an existing Apex .cls file.
Provide any relevant org or API constraints; the skill defaults to API version 66.0.
Salesforce CLI sf version 2.0.0 or later is documented by the skill.
Use the platform-apex-generate skill to review the existing Apex class at <path-to-class.cls>. Identify the three most important correctness, security, or maintainability issues and propose focused fixes, but do not modify or deploy any files.
Replace <path-to-object.object-meta.xml> with an existing Custom Object metadata file.
The skill documents a minimum API version of 60.0.
Use the platform-custom-object-generate skill to validate <path-to-object.object-meta.xml>. Report missing required elements and likely Metadata API deployment problems, but do not modify or deploy the file.
An available metadata-experts execute_metadata_action MCP tool at version 1.0.0 or later.
Access to the relevant Salesforce org schema for grounding.
No inflight custom metadata is needed for this standard-object example; use an empty inflightMetadata array.
Use the automation-flow-generate skill to create a scheduled-triggered Flow named Daily_Good_Morning that runs daily at 6:00 AM and sends an email to the running user saying good morning. Run the documented three-step generation pipeline and return the generated Flow XML, but do not deploy or activate it.