Agent skill · software engineering · jeremylongshore
lindy-multi-env-setup
Configure Lindy AI across development, staging, and production environments.
Why this skill is useful
Adds executable scripts for environment-specific configurations and validation that aren't in public docs.
What it needs
Requires aws, gcloud, vault installed locally. Requires lindy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Multi-Environment Setup Overview Isolate Lindy AI agents across development, staging, and production using separate workspaces, dedicated API keys, and environment-specific webhook configurations. Lindy agents live in workspaces — each environment should use its own workspace to prevent cross-environment data leakage. Prerequisites Multiple Lindy workspaces (one per environment) or Enterprise plan Secret management solution (env vars, Vault, AWS/GCP secrets) CI/CD pipeline with environment-aware deployment Application with environment detection logic Environment Strategy Environment Workspace API Key Source Agent Config ------------- ----------- --------------- ------------- Development dev-workspace .env.local Debug prompts, test integrations Staging staging-workspace CI/CD secrets Production-like, test data Production prod-workspace Secret manager Hardened prompts, live integrations Instructions Step 1: Create Separate Workspaces 1. Log in at 2. Create workspace for each environment: [company]-dev, [company]-staging, [company]-prod 3. Generate separate API keys in each workspace 4. Store each key in the appropriate secret store Step 2: Environment Configuration Step 3: Startup Validation Step 4: Secret Management Step 5: Agent Promotion (Dev to Staging to Prod) Critical: OAuth tokens, webhook URLs, and phone numbers do NOT transfer between workspaces. Each must be reconfigured per environment. Step 6: CI/CD Integration Output Produce an environment register listing each workspace, public callback host, credential reference, integration owner, promotion source, last smoke-test result, and rollback target. Record only secret identifiers and redacted URL forms; never copy credential values, private webhook paths, customer data, or production connection exports between environments. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-multi-env-setup