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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is strong in completeness and distinctiveness, with explicit 'Use when' and 'Trigger with' clauses that clearly define when the skill should be selected. The main weakness is that the specific actions involved in incident management are not enumerated—it says 'manage incident response' but doesn't detail what that entails (e.g., checking logs, restarting services, escalating). Overall, it's a solid, well-structured description.
Suggestions
Add specific concrete actions like 'check API health endpoints, review error logs, identify root causes, coordinate rollbacks, and escalate to on-call engineers' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (incident response for Documenso integration) and a general action (manage incident response), but doesn't list specific concrete actions like 'check API status', 'review error logs', 'escalate to on-call', or 'rollback deployments'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage incident response for Documenso integration issues) and 'when' (diagnosing production incidents, handling outages, responding to service disruptions) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would actually say: 'documenso incident', 'documenso outage', 'documenso down', 'documenso troubleshooting', plus broader terms like 'production incidents', 'outages', and 'service disruptions'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Documenso' and 'incident response'. The trigger terms are narrowly scoped to Documenso-specific incidents, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong incident runbook with highly actionable, executable diagnostic commands and well-sequenced response procedures for multiple failure scenarios. The main weakness is that it's somewhat long for a single SKILL.md file — the circuit breaker code and communication template could be split into referenced files. Minor verbosity in areas like the severity table and error handling table (which partially duplicates scenario content) could be trimmed.
Suggestions
Consider moving the circuit breaker TypeScript code and communication template into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
The error handling summary table at the end largely duplicates information from the scenario sections — consider removing it or replacing the scenarios with just the table to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some sections that could be tightened — the severity level table with response times and the communication template are somewhat boilerplate that Claude could generate on demand. The circuit breaker code is lengthy but arguably necessary as a concrete reference. Some redundancy exists between the error handling table and the scenario sections. | 2 / 3 |
Actionability | Highly actionable with executable bash diagnostic scripts, specific docker commands, concrete TypeScript circuit breaker implementation, and step-by-step procedures for each scenario. Commands are copy-paste ready with proper error handling (set -euo pipefail, fallback echo statements). | 3 / 3 |
Workflow Clarity | Each incident scenario follows a clear sequence with explicit validation checkpoints — the diagnostic script runs numbered checks, Scenario 1 has a branching decision tree based on status page results, Scenario 4 includes a verify step after fix. The post-incident checklist provides a feedback loop for ensuring completeness. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and scenarios, but it's a long monolithic file (~180 lines of content) that could benefit from splitting detailed scenarios or the circuit breaker code into separate referenced files. The single reference to 'documenso-data-handling' at the end is good but the main body could be better decomposed. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.