Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Documenso Incident Runbook · jeremylongshore | DecimalAI

devopsby jeremylongshore

Documenso Incident Runbook

jeremylongshore/documenso-incident-runbook

Source jeremylongshore/claude-code-plugins-plus-skills ↗License MIT

Manage incident response for Documenso integration issues.

SkillScore73Maintained

Automatic

DevOps & SRE pack

Last verified 9/8/2026

What it changes

Passed 16 of 22 test cases with the skill, and 5 of 22 without it.

Without skill23%

With skill73%

Checks it passed that the model alone missed

The response specifies taking 5 sample latency requests.
The response classifies the incident as Severity Level P2.
The response specifies a target response time of under 1 hour.

and 10 more in the full report

11 fixed5 passed either way6 still failing0 broke

Pass-rate lift: +50 pp
Tokens: +105%
Agent turns: 0%
Response time: -4%

Model gemini-3.6-flashMeasured 9/8/2026v216 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/jeremylongshore-documenso-incident-runbook/SKILL.md https://app.decimal.ai/s/jeremylongshore-documenso-incident-runbook/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add jeremylongshore-documenso-incident-runbook, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/jeremylongshore-documenso-incident-runbook/ and pins it in .decimal/skills.lock

decimalai skills add jeremylongshore-documenso-incident-runbook

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/jeremylongshore-documenso-incident-runbook/SKILL.md https://app.decimal.ai/s/jeremylongshore-documenso-incident-runbook/SKILL.md

Raw file: /s/jeremylongshore-documenso-incident-runbook/SKILL.md ↗ · machine-readable summary at /s/jeremylongshore-documenso-incident-runbook.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 11

Prompt

Our self-hosted Documenso application container is failing to store document records, and database connectivity issues are suspected. Provide the exact Docker command to test PostgreSQL health on the documenso-db container.

What was checked, without and with the skill
Checked	Without skill	With skill
The response uses `docker exec documenso-db pg_isready -U documenso` to check database health.	Missed	Passed

case-10 · gemini-3.6-flash · 9/8/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md231 lines2 files

Documenso Incident Runbook

Instructions

Declare the incident scope, commander, affected documents/signers/environment, and safe communication channel.
Stabilize with the approved pause, access-revocation, or rollback action before deep diagnosis.
Collect only redacted correlation/state/audit evidence; preserve document/signature integrity and chain of custody.
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

Track record

Benchmark

16 / 22

test cases passed, vs 5 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/8/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

jeremylongshore / claude-code-plugins-plus-skills

skills/.curated/documenso-incident-runbook/SKILL.md

View on GitHub ↗

License MITImported 9/8/2026Version v2Bundled 1 file

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Documenso Incident Runbook

Instructions

Output

Examples

Overview

Prerequisites

Severity Levels

Quick Diagnostic Commands

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills