Agent skill · software engineering · jeremylongshore
salesforce-multi-env-setup
Build Salesforce development, scratch-org, sandbox, staging, and production environments with explicit promotion and drift controls. Use when designing org topology. Trigger with "set up Salesforce environments".
Why this skill is useful
Provides specific commands and configurations for managing Salesforce environments that the AI wouldn't reliably generate on its own.
What it needs
Requires salesforce-cli, vault 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 Multi-Environment and Org Topology Overview Map each environment to a purpose, fidelity level, data policy, authorization boundary, lifecycle, and promotion contract. Prerequisites Business release model, Salesforce DX project, package strategy, org inventory, and environment owners Dev Hub, scratch-org, sandbox, staging, and production capabilities actually available to the customer Data seeding, masking, refresh, drift, namespace, dependency, promotion, rollback, and support requirements 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 Scratch orgs are disposable source-driven environments configured from project definitions; sandboxes provide different production fidelity and lifecycle characteristics. Available types, features, refreshes, data, and limits depend on the customer org. Authentication Give each environment separate aliases, apps or policies, principals, permissions, and secret references. Never copy production tokens or unmasked production data into development or CI. Instructions 1. Inventory every org and environment with purpose, edition, features, packages, namespace, data class, owner, lifecycle, and authority. 2. Choose scratch org, developer sandbox, partial or full sandbox, or other approved environment from fidelity and data requirements. 3. Define source, metadata, package, settings, seed, masking, and post-refresh automation contracts. 4. Create environment-specific app, principal, permission, limit, event, endpoint, and secret-reference matrices. 5. Automate deterministic creation or refresh where supported, then verify org identity before any deployment or data load. 6. Promote immutable source and artifacts through validation gates; never promote mutable org state as the source of truth. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-multi-env-setup