Sf Deploy
Jaganpro/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills.
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.
Install Platform Metadata Deploy
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills platform-metadata-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-metadata-deploy .claude/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .claude/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills platform-metadata-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-metadata-deploy .agents/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .agents/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills platform-metadata-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-metadata-deploy .cursor/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .cursor/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/platform-metadata-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills platform-metadata-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-metadata-deploy .gemini/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .gemini/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills platform-metadata-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-metadata-deploy .github/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .github/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills platform-metadata-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-metadata-deploy .opencode/skills/platform-metadata-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "platform-metadata-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-metadata-deploy into .opencode/skills/platform-metadata-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-metadata-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
platform-metadata-deploy- GitHub stars
- 1.1k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 695 words
- Files
- 10 (incl. references, assets)
- Skills in repo
- 251
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.
- Works in 6 steps: Preflight → Validate first → If validation succeeds, offer the next… → …
- : user deploys metadata
- SKILL.md covers When This Skill Owns the Task, Critical Operating Rules, Required Context to Gather First and Recommended Workflow, plus 7 more sections
- Runs Shell scripts from its folder; calls sf; needs INVALID_CROSS_REFERENCE_KEY
What it does
Platform Metadata Deploy is an agent skill from forcedotcom/sf-skills. Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage).
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files and assets (for example `README.md`, `references/agent-deployment-guide.md` and `references/deploy.sh`).
It sits in DevOps & Cloud, covering Deployment, CRM management and CI/CD. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.
When your agent uses it
- : user deploys metadata
- Creates/manages scratch orgs
- Sets up CI/CD pipelines
- Troubleshoots deployment errors with sf project deploy
Example prompts
- “/platform-metadata-deploy”
Requirements
- A Bash shell
- A credential in INVALID_CROSS_REFERENCE_KEY
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Shell), which the agent can run.
Shell commands in SKILL.md call:
sf
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
INVALID_CROSS_REFERENCE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Platform Metadata Deploy loads about 2.4k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 695 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 695 words, ~2,447 tokens.
Download SKILL.mdSave it as
.claude/skills/platform-metadata-deploy/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- platform-metadata-deploy
- description
- Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage).
- metadata.version
- 1.1
- metadata.domains
- Platform, Developer Experience
- metadata.relatedSkills
- agentforce-generate, agentforce-test, automation-flow-generate, experience-lwc-generate, integration-connectivity-connected-app-configure…
platform-metadata-deploy: Comprehensive Salesforce DevOps Automation
Use this skill when the user needs deployment orchestration: dry-run validation, targeted or manifest-based deploys, CI/CD workflow advice, scratch-org management, failure triage, or safe rollout sequencing for Salesforce metadata.
When This Skill Owns the Task
Use platform-metadata-deploy when the work involves:
sf project deploy start,quick,report, or retrieval workflows- release sequencing across objects, permission sets, Apex, and Flows
- CI/CD gates, test-level selection, or deployment reports
- troubleshooting deployment failures and dependency ordering
Delegate elsewhere when the user is:
- authoring Apex code → platform-apex-generate
- authoring LWC components → experience-lwc-generate
- creating custom objects or fields → platform-custom-object-generate, platform-custom-field-generate
- building Flows → automation-flow-generate
- doing org data operations → platform-data-manage
- authoring or testing Agentforce agents → agentforce-generate
Critical Operating Rules
- Use
sfCLI v2 only. - On non-source-tracking orgs, deploy/retrieve commands require an explicit scope such as
--source-dir,--metadata, or--manifest. - Prefer
--dry-runfirst before real deploys. - For Flows, deploy safely and activate only after validation.
- Keep test-data creation guidance delegated to
platform-data-manageafter metadata is validated or deployed.
Default deployment order
| Phase | Metadata |
|---|---|
| 1 | Custom objects / fields |
| 2 | Permission sets |
| 3 | Apex |
| 4 | Flows as Draft |
| 5 | Flow activation / post-verify |
This ordering prevents many dependency and FLS failures.
Required Context to Gather First
Ask for or infer:
- target org alias and environment type
- deployment scope: source-dir, metadata list, or manifest
- whether this is validate-only, deploy, quick deploy, retrieve, or CI/CD guidance
- required test level and rollback expectations
- whether special metadata types are involved (Flow, permission sets, agents, packages)
Preflight checks:
sf --version
sf org list
sf org display --target-org <alias> --json
test -f sfdx-project.jsonRecommended Workflow
1. Preflight
Confirm auth, repo shape, package directories, and target scope.
2. Validate first
sf project deploy start --dry-run --source-dir force-app --target-org <alias> --wait 30 --jsonUse manifest- or metadata-scoped validation when the change set is targeted.
3. If validation succeeds, offer the next safe workflow
After a successful validation, guide the user to the correct next action:
- deploy now
- assign permission sets
- create test data via platform-data-manage
- run tests / smoke checks
- orchestrate multiple post-deploy steps in order
4. Deploy the smallest correct scope
# source-dir deploy
sf project deploy start --source-dir force-app --target-org <alias> --wait 30 --json
# manifest deploy
sf project deploy start --manifest manifest/package.xml --target-org <alias> --test-level RunLocalTests --wait 30 --json
# manifest deploy with Spring '26 relevant-test selection
sf project deploy start --manifest manifest/package.xml --target-org <alias> --test-level RunRelevantTests --wait 30 --json
# quick deploy after successful validation
sf project deploy quick --job-id <validation-job-id> --target-org <alias> --json5. Verify
sf project deploy report --job-id <job-id> --target-org <alias> --jsonThen verify tests, Flow state, permission assignments, and smoke-test behavior.
6. Report clearly
Summarize what deployed, what failed, what was skipped, and what the next safe action is.
Output template: references/deployment-report-template.md
High-Signal Failure Patterns
| Error / symptom | Likely cause | Default fix direction |
|---|---|---|
FIELD_CUSTOM_VALIDATION_EXCEPTION | validation rule or bad test data | adjust data or rule timing |
INVALID_CROSS_REFERENCE_KEY | missing dependency | include referenced metadata first |
CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY | trigger / Flow / validation side effect | inspect automation stack and failing logic |
| tests fail during deploy | broken code or fragile tests | run targeted tests, fix root cause, revalidate |
| field/object not found in permset | wrong order | deploy objects/fields before permission sets |
| Flow invalid / version conflict | dependency or activation problem | deploy as Draft, verify, then activate |
Full workflows: references/orchestration.md, references/trigger-deployment-safety.md
Show full SKILL.md (251 more words)Show less
CI/CD Guidance
Default pipeline shape:
- authenticate
- validate repo / org state
- static analysis
- dry-run deploy
- tests + coverage gates
- deploy
- verify + notify
- When org policy and release risk allow it, consider
--test-level RunRelevantTestsfor Apex-heavy deployments. - Pair this with modern Apex test annotations such as
@IsTest(testFor=...)and@IsTest(isCritical=true)— see platform-apex-generate for authoring guidance.
Static analysis now uses Code Analyzer v5 (sf code-analyzer), not retired sf scanner.
Deep reference: references/deployment-workflows.md
Agentforce Deployment Note
Use this skill to orchestrate deployment/publish sequencing around agents, but use the agent-specific skill for authoring decisions:
- agentforce-generate for
.agentauthoring, Agent Builder, Prompt Builder, and metadata config
For full agent DevOps details, including Agent: pseudo metadata, publish/activate, and sync-between-orgs, see:
Cross-Skill Integration
| Need | Delegate to | Reason |
|---|---|---|
| custom object creation | platform-custom-object-generate | define objects before deploy |
| custom field creation | platform-custom-field-generate | define fields before deploy |
| Apex authoring / fixes | platform-apex-generate | code authoring and repair |
| run tests after deployment | platform-apex-test-run | post-deploy test execution and coverage |
| Flow creation / repair | automation-flow-generate | Flow authoring and activation guidance |
| test data or seed records | platform-data-manage | describe-first data setup and cleanup |
| Agent authoring and publish readiness | agentforce-generate | agent-specific correctness |
Reference Map
Start here
- references/orchestration.md
- references/deployment-workflows.md
- references/deployment-report-template.md
Specialized deployment safety
Asset templates
- assets/package.xml — manifest template covering common metadata types
- assets/destructiveChanges.xml — template for removing metadata from target orgs
Score Guide
| Score | Meaning |
|---|---|
| 90+ | strong deployment plan and execution guidance |
| 75–89 | good deploy guidance with minor review items |
| 60–74 | partial coverage of deployment risk |
| < 60 | insufficient confidence; tighten plan before rollout |
Completion Format
Deployment goal: <validate / deploy / retrieve / pipeline>
Target org: <alias>
Scope: <source-dir / metadata / manifest>
Result: <passed / failed / partial>
Key findings: <errors, ordering, tests, skipped items>
Next step: <safe follow-up action>© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references, assets) in skills/platform-metadata-deploy of forcedotcom/sf-skills.
- SKILL.md
- README.md
- assets/destructiveChanges.xml
- assets/package.xml
- references/agent-deployment-guide.md
- references/deploy.sh
- references/deployment-report-template.md
- references/deployment-workflows.md
- references/orchestration.md
- references/trigger-deployment-safety.md
Open the folder on GitHubat commit e5164d9
Compare with similar skills
Platform Metadata Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Platform Metadata Deploy this skillforcedotcom/sf-skills | 1.1k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Sf DeployJaganpro/sf-skills | 424 | — | ~2k | Automated safety check: Pass | MIT | |
| Sf Vlocity Build DeployJaganpro/sf-skills | 424 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Salesforce DeveloperJeffallan/claude-skills | 12k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Sf DataJaganpro/sf-skills | 424 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Web Console Local Tracesforcedotcom/salesforcedx-vscode | 1k | — | ~796 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Sf Vlocity Build Deploy
Jaganpro/sf-skills
Salesforce Industries DataPack deployment automation using Vlocity Build.
Salesforce Developer
Jeffallan/claude-skills
Writes Apex, Lightning Web Components and SOQL for the Salesforce platform, with bulkified triggers, governor-limit checks, 90% test coverage and Salesforce DX deployment.
Sf Data
Jaganpro/sf-skills
Salesforce data operations with 130-point scoring. An agent skill from Jaganpro/sf-skills.
Web Console Local Traces
forcedotcom/salesforcedx-vscode
Unblock hosted Web Console OTLP to localhost:4318. An agent skill from forcedotcom/salesforcedx-vscode.
Sf Industry Cme Epc Model
Jaganpro/sf-skills
Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.
More from forcedotcom/sf-skills
All 251 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Platform Metadata Deploy
What does Platform Metadata Deploy do?
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills. Platform Metadata Deploy is an agent skill from forcedotcom/sf-skills. Salesforce DevOps automation using sf CLI v2.
When should I use Platform Metadata Deploy?
Platform Metadata Deploy fits situations like: : user deploys metadata; creates/manages scratch orgs; sets up CI/CD pipelines; troubleshoots deployment errors with sf project deploy.
How do I install Platform Metadata Deploy in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a claude-code`. Or copy the skill folder (skills/platform-metadata-deploy in forcedotcom/sf-skills) into .claude/skills/platform-metadata-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Platform Metadata Deploy in Codex?
Run `npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a codex`. Or copy the skill folder (skills/platform-metadata-deploy in forcedotcom/sf-skills) into .agents/skills/platform-metadata-deploy in your project. Codex loads it when a task matches its description.
Can I use Platform Metadata Deploy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill platform-metadata-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-metadata-deploy, .gemini/skills/platform-metadata-deploy, .github/skills/platform-metadata-deploy and .opencode/skills/platform-metadata-deploy in your project.
What does Platform Metadata Deploy need to run?
Going by SKILL.md and its folder, Platform Metadata Deploy needs a shell for the scripts in its folder, the command-line tools its instructions call (sf) and credentials named INVALID_CROSS_REFERENCE_KEY. Our summary lists: A Bash shell; A credential in INVALID_CROSS_REFERENCE_KEY.
Does Platform Metadata Deploy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Platform Metadata Deploy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Platform Metadata Deploy use?
Platform Metadata Deploy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Platform Metadata Deploy use?
About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.
What are the alternatives to Platform Metadata Deploy?
Skills that share tags, products or a category with Platform Metadata Deploy: Sf Deploy (Jaganpro/sf-skills, 424 stars), Sf Vlocity Build Deploy (Jaganpro/sf-skills, 424 stars), Salesforce Developer (Jeffallan/claude-skills, 12k stars) and Sf Data (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Platform Metadata Deploy?
forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.
Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.