Agent skill

Sf Deploy

Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills.

Install Sf Deploy

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-deploy .claude/skills/sf-deploy && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .claude/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy

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

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-deploy .agents/skills/sf-deploy && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .agents/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-deploy .cursor/skills/sf-deploy && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .cursor/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-deploy

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-deploy .gemini/skills/sf-deploy && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .gemini/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy

Installs 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).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-deploy .github/skills/sf-deploy && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .github/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-deploy -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-deploy --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-deploy .opencode/skills/sf-deploy && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-deploy into .opencode/skills/sf-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-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: sf-deploy
GitHub stars: 424
Token cost: ~2k tokens
SKILL.md length: 658 words
Files: 12 (incl. references, assets)
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/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

Sf Deploy is an agent skill from Jaganpro/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/LWC code (use sf-apex/sf-lwc), creating metadata XML (use sf-metadata), or querying org data (use sf-data).

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files and assets (for example `CREDITS.md`, `README.md` and `references/agent-deployment-guide.md`).

It sits in DevOps & Cloud, covering Deployment, CRM management and CI/CD. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

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

“/sf-deploy”

Requirements

A Bash shell
A credential in INVALID_CROSS_REFERENCE_KEY

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Preflight
Validate first
If validation succeeds, offer the next safe workflow
Deploy the smallest correct scope
Verify
Report clearly

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. 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

Sf Deploy loads about 2k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 658 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~90
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~16k

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 Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 658 words, ~2,022 tokens.

Download SKILL.mdSave it as .claude/skills/sf-deploy/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.

name: sf-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/LWC code (use sf-apex/sf-lwc), creating metadata XML (use sf-metadata), or querying org data (use sf-data).
license: MIT
metadata.version: 2.3.0
metadata.author: Jag Valaiyapathy

sf-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 sf-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 or LWC code → sf-apex, sf-lwc
creating metadata definitions → sf-metadata
building Flows → sf-flow
doing org data operations → sf-data
authoring Agent Script logic → sf-ai-agentscript

Critical Operating Rules

Use sf CLI v2 only.
On non-source-tracking orgs, deploy/retrieve commands require an explicit scope such as --source-dir, --metadata, or --manifest.
Prefer --dry-run first before real deploys.
For Flows, deploy safely and activate only after validation.
Keep test-data creation guidance delegated to sf-data after 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:

bash

sf --version
sf org list
sf org display --target-org <alias> --json
test -f sfdx-project.json

Recommended Workflow

1. Preflight

Confirm auth, repo shape, package directories, and target scope.

2. Validate first

bash

sf project deploy start --dry-run --source-dir force-app --target-org <alias> --wait 30 --json

Use 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 sf-data
run tests / smoke checks
orchestrate multiple post-deploy steps in order

4. Deploy the smallest correct scope

bash

# 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> --json

5. Verify

bash

sf project deploy report --job-id <job-id> --target-org <alias> --json

Then 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

Show full SKILL.md (306 more words)Show less

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

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 RunRelevantTests for Apex-heavy deployments.
Pair this with modern Apex test annotations such as @IsTest(testFor=...) and @IsTest(isCritical=true) as documented in sf-apex.

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 skills for authoring decisions:

sf-ai-agentscript for .agent authoring and validation
sf-ai-agentforce for Agent Builder / Prompt Builder / metadata config

For full agent DevOps details, including Agent: pseudo metadata, publish/activate, and sync-between-orgs, see:

references/agent-deployment-guide.md

Cross-Skill Integration

Need	Delegate to	Reason
custom object / field creation	sf-metadata	define metadata before deploy
Apex compile / review / fixes	sf-apex	code authoring and repair
Flow creation / repair	sf-flow	Flow authoring and activation guidance
test data or seed records	sf-data	describe-first data setup and cleanup
Agent Script build/publish readiness	sf-ai-agentscript	agent-specific correctness

Reference Map

Start here

Specialized deployment safety

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

text

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>

Files

SKILL.md and 11 other files (references, assets) in skills/sf-deploy of Jaganpro/sf-skills.

SKILL.md
CREDITS.md
LICENSE
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 53c9956

Compare with similar skills

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

Sf Deploy compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Deploy this skillJaganpro/sf-skills	424	—	~2k	Automated safety check: Pass	MIT	5 mo ago
Platform Metadata Deployforcedotcom/sf-skills	1.1k	—	~2.4k	Automated safety check: Pass	Apache-2.0	5 days ago
Omnistudio Datapacks Deployforcedotcom/sf-skills	1.1k	—	~2k	Automated safety check: Pass	Apache-2.0	5 days ago
Consumer Goods Accruals Datakit Deployforcedotcom/sf-skills	1.1k	—	~5.1k	Automated safety check: Pass	Apache-2.0	5 days ago
Dx Code Analyzer Configureforcedotcom/sf-skills	1.1k	—	~5.6k	Automated safety check: Pass	Apache-2.0	5 days ago
Dx Devops Pipeline Manageforcedotcom/sf-skills	1.1k	—	~4.9k	Automated safety check: Pass	Apache-2.0	5 days ago

Similar skills

Platform Metadata Deploy
forcedotcom/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.
1.1k GitHub stars~2.4k tokensUpdated 5 days ago
DevOps & CloudAuto-check passed
Omnistudio Datapacks Deploy
forcedotcom/sf-skills
Salesforce Industries DataPack deployment automation using Vlocity Build.
1.1k GitHub stars~2k tokensUpdated 5 days ago
DevOps & CloudAuto-check passed
Consumer Goods Accruals Datakit Deploy
forcedotcom/sf-skills
A skill your agent uses to deploy the TPM Liability Accruals data kit end to end to a Salesforce org.
1.1k GitHub stars~5.1k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
Dx Code Analyzer Configure
forcedotcom/sf-skills
Set up, configure, and troubleshoot Salesforce Code Analyzer for any project.
1.1k GitHub stars~5.6k tokensUpdated 5 days ago
DevOps & CloudAuto-check passed
Dx Devops Pipeline Manage
forcedotcom/sf-skills
A skill your agent uses to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or…
1.1k GitHub stars~4.9k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
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.
12k GitHub stars~1.9k tokensUpdated 4 days ago
DevelopmentAuto-check passed

Questions about Sf Deploy

What does Sf Deploy do?

Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills. Sf Deploy is an agent skill from Jaganpro/sf-skills. Salesforce DevOps automation using sf CLI v2.

When should I use Sf Deploy?

Sf 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 Sf Deploy in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-deploy -a claude-code`. Or copy the skill folder (skills/sf-deploy in Jaganpro/sf-skills) into .claude/skills/sf-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Sf Deploy in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-deploy -a codex`. Or copy the skill folder (skills/sf-deploy in Jaganpro/sf-skills) into .agents/skills/sf-deploy in your project. Codex loads it when a task matches its description.

Can I use Sf 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 Jaganpro/sf-skills --skill sf-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/sf-deploy, .gemini/skills/sf-deploy, .github/skills/sf-deploy and .opencode/skills/sf-deploy in your project.

What does Sf Deploy need to run?

Going by SKILL.md and its folder, Sf 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 Sf 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 Sf 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 Sf Deploy use?

Sf Deploy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Deploy use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Sf Deploy?

Skills that share tags, products or a category with Sf Deploy: Platform Metadata Deploy (forcedotcom/sf-skills, 1.1k stars), Omnistudio Datapacks Deploy (forcedotcom/sf-skills, 1.1k stars), Consumer Goods Accruals Datakit Deploy (forcedotcom/sf-skills, 1.1k stars) and Dx Code Analyzer Configure (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Deploy?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/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.

Install Sf Deploy

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sf-deploy: Comprehensive Salesforce DevOps Automation

When This Skill Owns the Task

Critical Operating Rules

Default deployment order

Required Context to Gather First

Recommended Workflow

1. Preflight

2. Validate first

3. If validation succeeds, offer the next safe workflow

4. Deploy the smallest correct scope

5. Verify

6. Report clearly

High-Signal Failure Patterns

CI/CD Guidance

Agentforce Deployment Note

Cross-Skill Integration

Reference Map

Start here

Specialized deployment safety

Score Guide

Completion Format

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Deploy