Agent skill · software engineering · jeremylongshore
salesforce-prod-checklist
Gate a Salesforce integration or metadata change for production with contract, security, capacity, validation, canary, reconciliation, and rollback evidence. Use when preparing for go-live. Trigger with "review Salesforce production readiness".
Why this skill is useful
Adds specific deployment scripts and procedures for Salesforce integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Production Readiness Gate Overview Convert a release candidate into an evidence-backed go or no-go decision with named owners, bounded execution, and tested recovery. Prerequisites Immutable release candidate, change record, production org, maintenance window, and business owner Validated metadata and integration dependencies, API versions, permissions, limits, data mappings, and test evidence Canary, reconciliation, rollback or compensating action, communications, and Salesforce Support plans Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce release behavior depends on org metadata, automation, permissions, seasonal version, API support, entitlements, and shared capacity. Validation in a lower org reduces risk but does not prove production parity. Authentication Use separate named non-production and production authorization with minimum deployment and verification permissions. Production credentials must be protected, short-lived where supported, auditable, and unavailable to fork-origin code. Instructions 1. Freeze the candidate SHA, metadata manifest, adapter artifact, dependency lock, API contract, and generated outputs. 2. Compare production and validation orgs for edition, features, packages, schema, permissions, sharing, automation, limits, and data assumptions. 3. Review security, privacy, segregation-of-duties, destructive-change, backfill, event, and support impacts. 4. Run static checks, unit tests, Apex or Flow tests, deployment validation, contract tests, and synthetic integration checks. 5. Approve a small canary with explicit users, objects, records, time box, stop signals, and rollback owner. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-prod-checklist