Skip to content
TrustedSkillsbeta
Back to all skills

Sf Deploy

Listed
jaganpro·vlatest·devops·MIT

Automates Salesforce deployments from Git repositories using Jaganpro's streamlined sf-deploy tool.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

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

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jaganpro

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: domain.my.salesforce.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    domain.my.salesforce.comundeclaredsoap.sforce.comnamespace identifier

    What it found

    • skills/sf-deploy/references/agent-deployment-guide.md:425contacts domain.my.salesforce.com
      curl -s -X POST "https://DOMAIN.my.salesforce.com/services/oauth2/token" \

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jaganpro/sf-skills at 53c9956c42.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
53c9956c42
Manifest
skills/sf-deploy/SKILL.md
Scanned
10 files, 2,027 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Sf Deploy skill automates Salesforce deployments from Git repositories using the sf-deploy tool, streamlining your DevOps workflow. It orchestrates deployment processes including dry-run validation, targeted or manifest-based deploys, CI/CD guidance, scratch-org management, failure triage, and safe rollout sequencing for Salesforce metadata. This skill leverages the Salesforce CLI (v2) to manage deployments and retrieve information about your Salesforce orgs.

When to use it

  • Automated Deployments: To execute deployment workflows as part of a CI/CD pipeline.
  • Targeted Metadata Updates: When you need to deploy specific components like Apex, Flows, or permission sets.
  • Deployment Validation: Before deploying changes to a Salesforce org, perform dry-run validations to identify potential issues.
  • Release Sequencing: To manage the order of deployment for objects, permission sets, Apex, and Flows, preventing dependency failures.
  • Troubleshooting Deployments: To assist in identifying and resolving deployment failure issues.

Key capabilities

  • Supports sf project deploy start, quick, report, and retrieval workflows.
  • Manages release sequencing across various Salesforce metadata types (objects, permission sets, Apex, Flows).
  • Provides CI/CD gate integration and test-level selection for deployments.
  • Generates deployment reports to track changes and identify potential issues.
  • Handles failure triage and dependency ordering during deployments.
  • Offers a default deployment order prioritizing metadata components (Custom objects/fields -> Permission sets -> Apex -> Flows as Draft -> Flow activation).

Example prompts

  • "Can you perform a dry-run deployment of the force-app directory to my Salesforce org with alias <alias>?"
  • "What is the recommended CI/CD workflow for deploying changes using a manifest file named manifest/package.xml?"
  • "Deploy the permission sets in my Salesforce org."

Tips & gotchas

  • Salesforce CLI Version: The skill requires Salesforce CLI version 2 (sf CLI v2).
  • Explicit Scope Required: When deploying to non-source-tracking orgs, you must specify a deployment scope like --source-dir, --metadata, or --manifest.
  • Dry-Run First: Always perform a dry-run (--dry-run) before executing actual deployments. For Flows, deploy safely and activate only after validation.