salesforce-multi-env-setup
Configure Salesforce across Developer, Sandbox, and Production environments with proper org management. Use when setting up multi-environment deployments, configuring per-environment credentials, or implementing sandbox-to-production promotion flows. Trigger with phrases like "salesforce environments", "salesforce sandbox", "salesforce dev prod", "salesforce org management", "salesforce sandbox types". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Salesforce Multi-Environment Setup ## Overview Configure Salesforce integrations across Developer, Sandbox, and Production orgs with environment-specific credentials, login URLs, and deployment promotion flows. ## Prerequisites - Production Salesforce org (Enterprise+ for Full sandbox) - Salesforce CLI authenticated to all environments - Secret management solution (Vault, AWS/GCP Secrets Manager) ## Instructions ### Step 1: Salesforce Environment Types | Environment | Org Type | Login URL | Purpose | Data | |------------|---------|-----------|---------|------| | Development | Developer Edition or Scratch Org | login.salesforce.com | Local dev | Sample data | | QA | Developer Sandbox | test.salesforce.com | Testing | Subset of prod | | Staging | Full Sandbox | test.salesforce.com | Pre-prod validation | Copy of prod | | Production | Production Org | login.salesforce.com | Live traffic | Real data | ### Step 2: Sandbox Types | Sandbox Type | Data | Metadata | Refresh Interval | Use Case | |-------------|------|----------|-------------------|----------| | Developer | None | Copy of prod | 1 day | Feature development | | Developer Pro | None | Copy of prod | 1 day | Integration testi
- Overview
- Prerequisites
- Instructions
- Step 1: Salesforce Environment Types
- Step 2: Sandbox Types
- Step 3: Environment Configuration
- Step 4: Authenticate to Multiple Orgs
- Step 5: Secret Management by Environment
- Step 6: Deployment Promotion Flow
- Step 7: Environment Guards
- Output
- Error Handling
- Resources
- Next Steps
Authenticate to each environment with aliases sf org login web --alias sf-dev --instance-url https://login.salesforce.com sf org login web --alias sf-staging --instance-url https://test.salesforce.com sf org login web --alias sf-prod --instance-url https://login.salesforce.com For CI — use JWT (no browser needed) sf org login jwt \ List all authenticated orgs sf org list --all Set default org sf config set target-org sf-dev
What does the salesforce-multi-env-setup skill do?
Configure Salesforce across Developer, Sandbox, and Production environments with proper org management. Use when setting up multi-environment deployments, configuring per-environment credentials, or implementing sandbox-to-production promotion flows. Trigger with phrases like "salesforce environments", "salesforce sandbox", "salesforce dev prod", "salesforce org management", "salesforce sandbox types". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill salesforce-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.