Agent skill · software engineering · jeremylongshore
intercom-multi-env-setup
Configure Intercom across development, staging, and production workspaces.
Why this skill is useful
Adds a complete multi-environment setup script for Intercom with environment-specific configurations and safety guards that the AI wouldn't generate on its own.
What it needs
Requires aws, gcloud, vault installed locally. Requires intercom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Multi-Environment Setup Overview Configure separate Intercom workspaces for development, staging, and production with environment-specific access tokens, webhook URLs, and safety guards. This skill establishes a single config loader, an environment-aware client factory, per-platform secret storage, and production guards so the same codebase behaves correctly in every environment. The full step-by-step code lives in references/implementation.md; this file carries the workflow and the Step 1 skeleton so you can follow it end to end, then drill into the reference for depth. Prerequisites Separate Intercom workspaces (or at minimum, separate apps in Developer Hub) Secret management solution (Vault, AWS Secrets Manager, GCP Secret Manager) CI/CD pipeline with environment variable support Environment Strategy Environment Workspace Token Type Data Webhooks ------------- ----------- ----------- ------ ---------- Development Dev/sandbox workspace Dev access token Test data localhost via ngrok Staging Staging workspace Staging token Seed data staging.example.com Production Production workspace Production token Real data api.example.com Instructions Work through six steps. Read the Step 1 skeleton below to see the shape of the config, then open references/implementation.md for the complete code of every step. 1. Environment Configuration — a single loadConfig() reads NODEENV and merges shared secrets with per-environment defaults (debug, cache TTL, rate-limit concurrency). Skeleton below. 2. Environment-Aware Client Factory — a lazily-initialised getClient() that throws a clear, environment-named error when the token is missing. 3. Secret Management by Platform — store tokens in git-ignored .env.<environment> files locally and in GitHub Actions, AWS Secrets Manager, GCP Secret Manager, or HashiCorp Vault in CI/prod. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-multi-env-setup