Agent skill · software engineering · jeremylongshore
ramp-multi-env-setup
Configure isolated Ramp sandbox, staging, and production environments with separate applications, credentials, hosts, data, webhooks, and evidence. Use when preventing cross-environment access or promoting an integration. Trigger with "Ramp environments" or "separate Ramp sandbox and prod".
Why this skill is useful
Provides specific API call patterns and error handling for integrating with Ramp's corporate card management system that the AI wouldn't reliably generate on its own.
What it needs
Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ramp Sandbox and Production Isolation Overview Make environment selection a typed security boundary. Keep credentials and data from crossing it, verify resolved hosts before token exchange, and require an explicit interlock before production writes. Prerequisites Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary. Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation. Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved. Prepare approved secret storage and a sanitized evidence location. Current Contract Ramp sandbox uses demo.ramp.com and demo-api.ramp.com; production uses app.ramp.com and api.ramp.com. Tokens are valid only in the environment where issued, and sandbox and production applications have independent credentials and settings. Production Embedded Cards origins must be exact verified HTTPS origins; localhost is not accepted for production integrations. Sandbox cannot move real money, but its successful behavior does not prove production authorization or data equivalence. Instructions 1. Define a closed environment enum with host, application ID, secret references, redirect URIs, parent origins, webhook endpoints, entity allowlists, and write policy. 2. Create separate Ramp applications and secret-manager namespaces; prohibit a configuration from carrying credentials or webhook secrets across environments. 3. Validate host allowlists, TLS, redirect/origin exactness, and token environment before each startup; print only non-secret environment identity. 4. Run synthetic and sandbox tests, then promote the same artifact and reviewed configuration schema without copying sandbox data or credentials. 5. Require a time-bound production-write enablement with owner, entity, operation, rollback, and automatic fail-closed behavior. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-multi-env-setup