Agent skill · operations · jeremylongshore
documenso-incident-runbook
Manage incident response for Documenso integration issues.
Why this skill is useful
Adds executable scripts for diagnosing and responding to Documenso integration incidents that are not available in public documentation.
What it needs
Requires docker, jq installed locally. Requires documenso account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Documenso Incident Runbook Instructions 1. Declare the incident scope, commander, affected documents/signers/environment, and safe communication channel. 2. Stabilize with the approved pause, access-revocation, or rollback action before deep diagnosis. 3. Collect only redacted correlation/state/audit evidence; preserve document/signature integrity and chain of custody. 4. Verify recovery, notify owners, and create follow-up work for root cause and prevention. Output A time-stamped incident record with scope, owner, mitigation, redacted evidence, and verified recovery or escalation. Examples For unauthorized document access, restrict affected credentials or sharing immediately, capture opaque document/correlation IDs and redacted audit state, and verify access is restored only to the intended role. Escalate according to policy; do not share documents, signing links, or signer PII in incident chat. Overview Step-by-step procedures for responding to Documenso integration incidents. Covers cloud outages, self-hosted issues, and integration failures. Prerequisites Access to monitoring dashboards Documenso dashboard access Application log access On-call escalation contacts defined Severity Levels Level Description Examples Response Time ------- ------------- ---------- --------------- P1 Complete signing outage All API calls failing, no documents can be sent < 15 min P2 Degraded functionality Slow responses, intermittent errors, webhooks delayed < 1 hour P3 Minor issue, workaround available Single document stuck, UI glitch < 4 hours P4 Non-urgent Feature request, documentation gap Next business day Quick Diagnostic Commands Incident Response Procedures Scenario 1: Documenso Cloud Outage (5xx Errors) Symptoms: High error rate, 500/502/503 from Documenso API. Actions: 1. Check status page: https://status.documenso.com 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/documenso-incident-runbook--a82db5