Agent skill · software engineering · jeremylongshore
instantly-multi-env-setup
Separate Instantly development, staging, and production workspaces, keys, data, and webhook routes. Use when designing environment isolation or eliminating shared credentials and callbacks. Trigger with "separate Instantly environments", "create an Instantly staging workspace", or "isolate Instantly webhook routes".
Why this skill is useful
Adds a comprehensive setup script for managing multi-environment configurations with Instantly API that includes environment-specific API keys and webhook endpoints.
What it needs
Requires npm installed locally. Requires instantly account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Instantly Multi-Environment Isolation Overview Design environment isolation and promotion without fake vendor endpoints or accidental cross-workspace mutations. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result. Prerequisites The target repository, Instantly workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved API v2 key only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output. Current Contract Use separate workspaces and keys where isolation requirements demand it. Workspace-group delegation uses x-as-workspace and increases cross-tenant risk. Environment names are not proof of identity; validate opaque workspace IDs and read-only probes. Authentication Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions. Instructions 1. Document environment-to-workspace IDs, owners, scopes, data classes, domains, and webhook URLs. 2. Use local fakes for development and synthetic records for staging. 3. Store one scoped key reference per environment; never use fallback production credentials. 4. Add startup guards that compare the expected opaque workspace ID before mutation. 5. Promote code and schemas separately from campaigns, leads, accounts, or webhooks. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/instantly-multi-env-setup