Individual skill
documenso-incident-runbook
Manage incident response for Documenso integration issues. Use when diagnosing production incidents, handling outages, or responding to Documenso service disruptions. Trigger with phrases like "documenso incident", "documenso outage", "documenso down", "documenso troubleshooting".
plugins/saas-packs/documenso-pack/skills/documenso-incident-runbook/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- documenso Declared skill tag
- incident-response Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,483 bytesSKILL.mdcore · 8,483 bytesSKILL.mdcore · 8,483 bytesSKILL.mdcore · 8,483 bytesreferences/implementation-guide.mddoc · 7,680 bytes
Read excerpt
# 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
