Documenso Multi Env SetupSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: documenso-multi-env-setup description: 'Configure Documenso across multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows. Trigger with phrases like "documenso environments", "documenso staging", "documenso dev setup", "multi-environment documenso". ' allowed-tools: Read, Write, Edit version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - documenso - api - workflow compatibility: Designed for Claude Code --- # 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 ``` ┌─────────────────────────────────────────────────────────────┐ │ Development │ │ API: stg-app.documenso.com (or localhost:3000 self-hosted) │ │ Key: DOCUMENSO_API_KEY=api_dev_xxx │ │ Webhooks: ngrok tunnel │ ├─────────────────────────────────────────────────────────────┤ │ Staging │ │ API: stg-app.documenso.com │ │ Key: DOCUMENSO_API_KEY=api_stg_xxx │ │ Webhooks: staging.yourapp.com/webhooks/documenso │ ├─────────────────────────────────────────────────────────────┤ │ Production │ │ API: app.documenso.com (or sign.yourcompany.com) │ │ Key: DOCUMENSO_API_KEY=api_prod_xxx │ │ Webhooks: api.yourapp.com/webhooks/documenso │ └─────────────────────────────────────────────────────────────┘ ``` ## Instructions ### Step 1: Environment Configuration Files ```bash # .env.development DOCUMENSO_API_KEY=api_dev_xxxxxxxxxxxx DOCUMENSO_BASE_URL=https://stg-app.documenso.com/api/v2 DOCUMENSO_WEBHOOK_SECRET=whsec_dev_xxxxxxxxxxxx LOG_LEVEL=debug NODE_ENV=development # .env.staging DOCUMENSO_API_KEY=api_stg_xxxxxxxxxxxx DOCUMENSO_BASE_URL=https://stg-app.documenso.com/api/v2 DOCUMENSO_WEBHOOK_SECRET=whsec_stg_xxxxxxxxxxxx LOG_LEVEL=info NODE_ENV=staging # .env.production DOCUMENSO_API_KEY=api_prod_xxxxxxxxxxxx DOCUMENSO_BASE_URL=https://app.documenso.com/api/v2 DOCUMENSO_WEBHOOK_SECRET=whsec_prod_xxxxxxxxxxxx LOG_LEVEL=warn NODE_ENV=production ``` ### Step 2: Environment-Aware Client Factory ```typescript // src/documenso/factory.ts import { Documenso } from "@documenso/sdk-typescript"; interface EnvConfig { apiKey: string; baseUrl: string; webhookSecret: string; } function getConfig(): EnvConfig { const apiKey = process.env.DOCUMENSO_API_KEY; if (!apiKey) throw new Error("DOCUMENSO_API_KEY required"); return { apiKey, baseUrl: process.env.DOCUMENSO_BASE_URL ?? "https://app.documenso.com/api/v2", webhookSecret: process.env.DOCUMENSO_WEBHOOK_SECRET ?? "", }; } let client: Documenso | null = null; export function getClient(): Documenso { if (!client) { const config = getConfig(); client = new Documenso({ apiKey: config.apiKey, serverURL: config.baseUrl, }); } return client; } export function getWebhookSecret(): string { return getConfig().webhookSecret; } // Reset for testing export function resetClient(): void { client = null; } ``` ### Step 3: Environment Guards ```typescript // src/guards.ts function requireProduction() { if (process.env.NODE_ENV !== "production") { throw new Error("This operation requires production environment"); } } function blockProduction(operation: string) { if (process.env.NODE_ENV === "production") { throw new Error(`${operation} is blocked in production`); } } // Usage async function deleteAllDrafts(client: Documenso) { blockProduction("deleteAllDrafts"); // Safety guard // ... only runs in dev/staging } async function sendBulkContracts(client: Documenso) { requireProduction(); // Only send real contracts in prod // ... } ``` ### Step 4: Mock Client for Development ```typescript // src/documenso/mock.ts import { vi } from "vitest"; export function createMockClient() { let docCounter = 0; return { documents: { createV0: vi.fn().mockImplementation(async ({ title }) => ({ documentId: ++docCounter, title, status: "DRAFT", })), setFileV0: vi.fn().mockResolvedValue(undefined), findV0: vi.fn().mockResolvedValue({ documents: [] }), getV0: vi.fn().mockResolvedValue({ status: "DRAFT", recipients: [] }), sendV0: vi.fn().mockResolvedValue(undefined), deleteV0: vi.fn().mockResolvedValue(undefined), }, documentsRecipients: { createV0: vi.fn().mockResolvedValue({ recipientId: 100 }), }, documentsFields: { createV0: vi.fn().mockResolvedValue({ fieldId: 200 }), }, }; } ``` ### Step 5: Template Promotion Between En
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__documenso-multi-env-setup.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Documenso Multi Env Setup skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Documenso Multi Env Setup safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Documenso Multi Env Setup access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Documenso Multi Env Setup work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.