What is platform-quick-deploy?

A guide for promoting a previously validated Salesforce deployment to a production org without running the validation tests again.

It is for quick deploys, promoting validated changes, and shipping Salesforce metadata to production.

It avoids repeating checks when an eligible validation job already exists, while verifying that the target is truly production.

platform-quick-deploy — Skill for Claude Code and Codex by forcedotcom: A guide for promoting a previously validated Salesforce deployment…

Install

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.

agentmods

npx agentmods add skills/forcedotcom/sf-skills/platform-quick-deploy

Any agent

npx skills add forcedotcom/sf-skills --skill platform-quick-deploy

Clone the repo

git clone --depth 1 https://github.com/forcedotcom/sf-skills

Made for: Claude Code, Codex.

Or install salesforce-development, the plugin that ships this one along with the rest of its 37 skills, 13 commands, 2 agents, 3 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/forcedotcom/sf-skills/platform-quick-deploy.svg)](https://agentmods.dev/skills/forcedotcom/sf-skills/platform-quick-deploy)

Your own site

<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/platform-quick-deploy"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/platform-quick-deploy.svg" alt="Measured on agentmods" height="20"></a>

Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,144 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00117	$0.01144
Opus 5	$0.00059	$0.00572
Sonnet 5	$0.00023	$0.00229
Haiku 4.5	$0.00012	$0.00114

Measured today against content hash 916a7669e6ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

platform-quick-deploy 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 today.

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.

plugins/builder/salesforce-development/skills/platform-quick-deploy/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick Deploying to Prod

Promote a validated deploy to a Production org using the job ID from a prior sf project deploy validate. No tests re-run, no components re-validated — just the promotion.

Preconditions (gate strictly)

Before doing ANYTHING, verify all four:

Target is Production
```
sf org display --target-org <alias> --json
```
Confirm the target really is production. The reliable check is the gate's classifier (returns production|sandbox|scratch|trial|devhub|unknown):
```
sf org display --target-org <alias> --json | "${CLAUDE_PLUGIN_ROOT}/scripts/sf-deploy-gate" classify
```
Production means isSandbox=false AND isScratch=false AND instance URL has no -- (sandbox marker) AND no test.salesforce.com AND it is not a trial/Developer Edition host (orgfarm-*, *.develop.my.salesforce.com, *.pc-rnd.*, or a trialExpirationDate in the response — these report isSandbox/isScratch as null and must not be taken for production).

If target is NOT production (classifier returns anything other than production) → STOP and redirect to platform-metadata-deploy (which handles non-prod natively).
A validation exists
- Read .sfdx/last-validation.json if it exists (left there by platform-deploy-validate)
- OR ask the user for the job ID
- OR fall back to --use-most-recent (validates within last 3 days)
Validation is fresh enough
- Explicit --job-id: must be ≤10 days old per Salesforce's quick-deploy window
- --use-most-recent: must be ≤3 days old
- If the recorded createdAt exceeds the window → STOP and run platform-deploy-validate first
Explicit user confirmation
- Print a confirmation block (alias, instance URL, edition, validated component count, test results) and ask: "Confirm deploy to PRODUCTION? (yes/no)"
- Do NOT proceed without an explicit "yes"

Workflow

Step 1 — Display the production confirmation banner

Format exactly:

Read the full file on GitHub · 106 lines

Changes

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.

today First seen · 106 lines · 117 tokens per session scan A 916a7669e6ce

Subscribe to this mod's changes

platform-quick-deploy is a skill published in the GitHub repository forcedotcom/sf-skills (961 stars, last pushed yesterday), licensed Apache-2.0. It adds 117 tokens to every session and 1,144 once invoked, about $0.0006 per session on Opus 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-09-03.

DevOps and cloud

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens