Agent skill

Documenso Prod Checklist

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Execute Documenso production deployment checklist and rollback procedures.

MITAuto-check: notesDevOps & Cloud

Install Documenso Prod Checklist

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-prod-checklist -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace documenso-prod-checklist --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/documenso-prod-checklist .claude/skills/documenso-prod-checklist && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
documenso-prod-checklist
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
520 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Execute Documenso production deployment checklist and rollback procedures.

  • Works in 7 steps: Authentication & Secrets → Error Handling → Performance → …
  • Deploying Documenso integrations to production
  • SKILL.md covers Instructions, Output, Examples and Overview, plus 8 more sections
  • Calls curl, jq and openssl; needs DOCUMENSO_API_KEY

What it does

Documenso Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute Documenso production deployment checklist and rollback procedures. Use when deploying Documenso integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "documenso production", "deploy documenso", "documenso go-live", "documenso launch checklist".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Deployment and Product launch strategy. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Deploying Documenso integrations to production
  • Preparing for launch
  • Implementing go-live procedures
  • With phrases like documenso production

Example prompts

  • “documenso production”
  • “deploy documenso”
  • “documenso go-live”
  • “/documenso-prod-checklist”

Requirements

  • A credential in DOCUMENSO_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Bash(kubectl:*), Bash(curl:*), Grep

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Authentication & Secrets
  2. Error Handling
  3. Performance
  4. Monitoring & Alerting
  5. Webhooks
  6. Data & Compliance
  7. Self-Hosted Production (if applicable)

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash(kubectl:*)
    • Bash(curl:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq
    • openssl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • status.documenso.com
    • docs.documenso.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • DOCUMENSO_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Documenso Prod Checklist loads about 1.7k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 520 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:57
    anager (Vault, AWS Secrets Manager, not `.env`)

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 520 words, ~1,707 tokens.

Download SKILL.mdSave it as .claude/skills/documenso-prod-checklist/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
documenso-prod-checklist
description
Execute Documenso production deployment checklist and rollback procedures. Use when deploying Documenso integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "documenso production", "deploy documenso", "documenso go-live", "documenso launch checklist".
allowed-tools
Read, Bash(kubectl:*), Bash(curl:*), Grep
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, documenso, deployment

Documenso Production Checklist

Instructions

  1. Complete evidence gates for workspace/identity, template/version review, signer authorization, data/retention, callbacks, audit, monitoring, and rollback.
  2. Validate the exact production role/audience and signing lifecycle with approved safe checks.
  3. Stop production enablement when any document, identity, security, or owner gate is unverified.
  4. Record the named go/no-go decision and post-release observation result.

Output

  • A production-readiness receipt with owners, evidence links, approved exceptions, and tested rollback path.

Examples

Validate a new template in staging with synthetic signers, verify the production access roles and callback endpoint under review, then release to an approved canary. If authorization, state, or audit behavior differs, halt the release and restore the prior approved template.

Overview

Complete checklist for deploying Documenso integrations to production, covering security, reliability, monitoring, and compliance readiness.

Prerequisites

  • Staging environment tested and verified
  • Production API keys available
  • Deployment pipeline configured (see documenso-ci-integration)
  • Monitoring ready (see documenso-observability)

Production Checklist

1. Authentication & Secrets
  • Production API key generated (not staging key)
  • API key stored in secret manager (Vault, AWS Secrets Manager, not .env)
  • Webhook secret configured and verified
  • Key rotation procedure documented
  • Old/unused keys revoked
  • Self-hosted: secrets generated with openssl rand -hex 32
  • Self-hosted: signing certificate from trusted CA mounted
2. Error Handling
  • All API calls wrapped in try/catch with typed errors
  • Exponential backoff for 429/5xx responses
  • Circuit breaker for Documenso outages
  • User-friendly error messages (no raw API errors exposed)
  • Error tracking integration (Sentry, Datadog, etc.)
3. Performance
  • Singleton client pattern (not creating new client per request)
  • Templates used for repetitive document creation
  • Bulk operations use concurrency control (p-queue)
  • Background processing for non-critical operations (Bull/BullMQ)
  • Document metadata cached (completed documents immutable)
4. Monitoring & Alerting
  • Health check endpoint: GET /health/documenso
  • API error rate alerting (> 5% for 5 minutes)
  • Latency monitoring (p95 > 5s)
  • Webhook delivery success rate tracking
  • Structured logging with sanitized PII
Show full SKILL.md (220 more words)Show less
5. Webhooks
  • HTTPS endpoint configured (HTTP rejected by Documenso)
  • Webhook secret verification using constant-time comparison
  • Idempotent event processing (handle duplicates)
  • Async processing (respond 200 immediately, process in background)
  • Dead letter queue for failed webhook processing
6. Data & Compliance
  • PII sanitized in all logs (emails, names)
  • Data retention policy implemented
  • GDPR access/erasure request process documented
  • Signed PDFs archived to durable storage
  • Self-hosted: document storage strategy defined
7. Self-Hosted Production (if applicable)
  • PostgreSQL with automated backups
  • HTTPS via reverse proxy (nginx, Caddy, Traefik)
  • Signing certificate from trusted CA (not self-signed)
  • SMTP configured and tested (emails actually deliver)
  • Container runs as non-root user (UID 1001)
  • Resource limits set (CPU, memory)
  • Automated container restarts (restart: unless-stopped)

Pre-Deployment Verification Script

bash
#!/bin/bash
set -euo pipefail
echo "=== Documenso Production Verification ==="

# Check API key
if [ -z "${DOCUMENSO_API_KEY:-}" ]; then
  echo "FAIL: DOCUMENSO_API_KEY not set"; exit 1
fi
echo "OK: API key configured"

# Test connection
BASE="${DOCUMENSO_BASE_URL:-https://app.documenso.com/api/v1}"
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer $DOCUMENSO_API_KEY" \
  "$BASE/documents?page=1&perPage=1")
[ "$STATUS" = "200" ] && echo "OK: API connection ($STATUS)" || echo "FAIL: API connection ($STATUS)"

# Test webhook endpoint
WEBHOOK_URL="${DOCUMENSO_WEBHOOK_URL:-}"
if [ -n "$WEBHOOK_URL" ]; then
  WH_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$WEBHOOK_URL")
  echo "Webhook endpoint: $WH_STATUS"
fi

# Check health endpoint
HEALTH_URL="${APP_URL:-http://localhost:3000}/health/documenso"
HEALTH=$(curl -s "$HEALTH_URL" 2>/dev/null | jq -r '.status' 2>/dev/null || echo "unreachable")
echo "Health check: $HEALTH"

echo "=== Verification Complete ==="

Rollback Procedure

text
If issues occur after deployment:

1. Immediate: revert to previous container image / deployment
   kubectl rollout undo deployment/signing-service
   # or: vercel rollback

2. Verify rollback:
   curl -s $APP_URL/health/documenso | jq '.status'

3. Investigate:
   - Check deployment diff (what changed?)
   - Review error logs for the deployment window
   - Test the failed version in staging

4. Fix and re-deploy:
   - Fix the root cause on a feature branch
   - Test in staging
   - Deploy with monitoring active

Go-Live Day Checklist

  • All checklist items above verified
  • Staging smoke test passed within last 24 hours
  • Team notified of deployment window
  • Monitoring dashboards open during deployment
  • Rollback procedure documented and accessible
  • Support contact for Documenso available (Discord or email)
  • First production document created and verified end-to-end

Error Handling

AlertConditionResponse
Deploy failedCI/CD errorCheck logs, fix, retry
Health check failedDocumenso unreachableVerify API key, check status page
Error spike post-deployBreaking changeExecute rollback procedure
Webhook delivery stoppedEndpoint misconfiguredCheck HTTPS URL, secret, event subscriptions

Resources

Next Steps

For version upgrades, see documenso-upgrade-migration.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/documenso-prod-checklist of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Documenso Prod Checklist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Documenso Prod Checklist compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Documenso Prod Checklist this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: NotesMIT
Shipping And Launchdzhalaevd/Donatello1355 repos~2.5kAutomated safety check: PassApache-2.0
Launch Runbookrampstackco/claude-skills945—~2kAutomated safety check: PassMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Mirrord Operatormetalbear-co/mirrord5.4k1 repos~4.6kAutomated safety check: PassMIT

Similar skills

  • Shipping And Launch

    dzhalaevd/Donatello

    Prepares production launches. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 5 repos~2.5k tokens
    DevOps & CloudAuto-check passed
  • Launch Runbook

    rampstackco/claude-skills

    Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures.

    945 GitHub stars~2k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Mirrord Operator

    metalbear-co/mirrord

    Help users install and configure the mirrord Operator for team/enterprise environments.

    5.4k GitHub starsUsed in 1 repo~4.6k tokens
    DevOps & CloudAuto-check passed
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Documenso Prod Checklist

What does Documenso Prod Checklist do?

Execute Documenso production deployment checklist and rollback procedures. Documenso Prod Checklist is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute Documenso production deployment checklist and rollback procedures.

When should I use Documenso Prod Checklist?

Documenso Prod Checklist fits situations like: deploying Documenso integrations to production; preparing for launch; implementing go-live procedures; with phrases like documenso production.

How do I install Documenso Prod Checklist in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-prod-checklist -a claude-code`. Or copy the skill folder (skills/.curated/documenso-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/documenso-prod-checklist in your project. Claude Code loads it when a task matches its description.

How do I install Documenso Prod Checklist in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-prod-checklist -a codex`. Or copy the skill folder (skills/.curated/documenso-prod-checklist in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/documenso-prod-checklist in your project. Codex loads it when a task matches its description.

Can I use Documenso Prod Checklist in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-prod-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documenso-prod-checklist, .gemini/skills/documenso-prod-checklist, .github/skills/documenso-prod-checklist and .opencode/skills/documenso-prod-checklist in your project.

What does Documenso Prod Checklist need to run?

Going by SKILL.md and its folder, Documenso Prod Checklist needs the command-line tools its instructions call (curl, jq and openssl) and credentials named DOCUMENSO_API_KEY. Our summary lists: A credential in DOCUMENSO_API_KEY. Its frontmatter pre-approves these tools: Read, Bash(kubectl:*), Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Documenso Prod Checklist access the network?

SKILL.md names 2 domains. As links in the text: status.documenso.com and docs.documenso.com. This is read from the text; nothing was executed.

Is Documenso Prod Checklist safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Documenso Prod Checklist use?

Documenso Prod Checklist is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Documenso Prod Checklist use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Documenso Prod Checklist?

Skills that share tags, products or a category with Documenso Prod Checklist: Shipping And Launch (dzhalaevd/Donatello, 135 stars), Launch Runbook (rampstackco/claude-skills, 945 stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars) and GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documenso Prod Checklist?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.