Agent skill · software engineering · jeremylongshore
gamma-multi-env-setup
Configure Gamma across development, staging, and production environments.
Why this skill is useful
Provides specific environment configuration patterns and API key management for the Gamma SaaS that the AI wouldn't reliably generate on its own.
What it needs
Requires aws, gcloud, vault installed locally. Requires gamma account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Gamma Multi-Environment Setup Output Record environment identity references, approved destinations, policy version, validation result, owner, and rollback path. Do not include credentials or content. Examples Use a fictional staging deck to prove the development credential cannot publish to production, rotate the staging credential, and retain only redacted control evidence. Overview Configure Gamma API access across development, staging, and production environments. Since Gamma is a SaaS API with no self-hosted option, environment separation is achieved through separate workspaces (API keys), mock servers for development, and environment-aware client configuration. Prerequisites Separate Gamma workspaces (or at minimum separate API keys) per environment Secret management solution Completed gamma-install-auth setup Environment Architecture Instructions Step 1: Environment Configuration Step 2: Environment-Aware Client Factory Step 3: Environment Files Step 4: Production Secret Management Step 5: Environment Guards Step 6: CI/CD Environment Configuration Environment Checklist Check Dev Test Staging Production ------- ----- ------ --------- ------------ API key source .env file Not needed (mock) GitHub Secret Secret Manager Mock mode Optional Yes No No Debug logging On On On Off Credit consumption Optional None Real (staging workspace) Real Secret manager No No Optional Required Error Handling Issue Cause Solution ------- ------- ---------- Wrong API key for env Env var mismatch Verify NODEENV and matching key Credits consumed in dev Mock mode off Set GAMMAMOCK=true in development Secret fetch fails IAM permissions Check secret manager access policy Production data in dev No env guard Add blockProduction() guards Resources 12-Factor App Config Gamma API Key Management AWS Secrets Manager Next Steps Proceed to gamma-observability for monitoring setup.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/gamma-multi-env-setup--08dc58