Agent skill · software engineering · jeremylongshore

documenso-multi-env-setup

Configure Documenso across multiple environments (dev, staging, production).

Why this skill is useful

Provides specific environment configuration patterns and API key management for Documenso that the AI wouldn't reliably generate on its own.

What it needs

Requires documenso account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Documenso Multi-Environment Setup Output Isolated development, staging, and production workspaces with separate scoped identities, templates, signer controls, and audit boundaries. A promotion/rollback receipt based on synthetic validation rather than production document or signer experiments. Examples Validate a versioned template and callback in development using synthetic recipients, promote to staging with separate credentials, and record its lifecycle/authorization/alert results. Release production through an approved canary only; if any gate differs, restore the prior configuration and do not copy production keys or signing artifacts into lower environments. Overview Configure Documenso across development, staging, and production with environment isolation, secret management, and promotion workflows. Documenso cloud offers a staging environment at stg-app.documenso.com; self-hosted users run separate instances. Prerequisites Documenso accounts or instances for each environment Secret management solution (Vault, AWS Secrets Manager, or .env files) Completed documenso-install-auth setup Environment Architecture Instructions Step 1: Environment Configuration Files Step 2: Environment-Aware Client Factory Step 3: Environment Guards Step 4: Mock Client for Development Step 5: Template Promotion Between Environments Environment Checklist Check Dev Staging Production ------- ----- --------- ------------ Separate API key Yes Yes Yes Debug logging On On Off Webhook endpoint ngrok staging URL production URL Secret manager .env file .env file Vault/AWS SM Mock mode available Yes No No Cleanup scripts enabled Yes Yes No Error Handling Issue Cause Solution ------- ------- ---------- Wrong environment data Missing NODEENV Set explicitly in each environment Key mismatch Using dev key in prod Verify env var names per environment Webhook not received Wrong URL configured Update webhook URL in each Documenso environment Mock not working Wrong client injected Check factory retur …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/documenso-multi-env-setup

View the source on GitHub

Browse the @skills marketplace