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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable runbook with concrete commands and code, but it underperforms on conciseness, workflow validation, and progressive disclosure by keeping large blocks inline, duplicating the unreferenced bundle, and omitting explicit verify-then-retry checkpoints in its procedures.

Suggestions

Move the full diagnostic bash script and the TypeScript circuit-breaker class into references/ files and link to them from SKILL.md, keeping only the essential quick-start commands inline to improve conciseness and progressive disclosure.

Add explicit validation/verification checkpoints to the incident-response procedures (e.g., 'verify degraded mode took effect', 'after certificate restart, confirm signatures validate') and a validate→fix→retry loop for the destructive/risky steps.

Either reference references/implementation-guide.md from the body or remove the duplicate severity-table/diagnostic content so the bundle is actually signaled and navigated rather than orphaned.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (tables, checklists, code blocks, no concept-explaining fluff) but is long and keeps a full TypeScript circuit-breaker class and a complete diagnostic script inline that arguably belong in a reference file, with severity-table content duplicated in the unreferenced bundle.	2 / 3
Actionability	Provides concrete, executable guidance throughout — real curl/docker/openssl/kubectl commands with HTTP-code checks, a full copy-paste-ready diagnostic script with 'set -euo pipefail', and a complete TypeScript circuit-breaker class.	3 / 3
Workflow Clarity	Severity levels and scenario-based numbered actions give a clear sequence, but the response procedures lack explicit validate→fix→retry feedback loops for risky operations (degraded-mode enablement, certificate replacement, circuit-breaker auto-close), which caps the score per the rubric.	2 / 3
Progressive Disclosure	Sections are organized, but the body is fairly monolithic and the one provided bundle file (references/implementation-guide.md) is never referenced from the body while duplicating inline content; the only pointer is to a sibling skill, so the bundle is neither signaled nor navigated.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states purpose, gives an explicit 'Use when' trigger clause, and supplies four natural trigger phrases. Its only weakness is that the capability description is a general management verb rather than a list of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the Documenso incident-response domain and several actions ('diagnosing production incidents, handling outages, or responding to...service disruptions') but stays at a general management-verb level rather than listing multiple discrete concrete operations like the top anchor.	2 / 3
Completeness	Explicitly answers both 'what' ('Manage incident response for Documenso integration issues') and 'when' ('Use when diagnosing production incidents, handling outages...'), with explicit trigger guidance present.	3 / 3
Trigger Term Quality	Provides four natural trigger phrases ('documenso incident', 'documenso outage', 'documenso down', 'documenso troubleshooting') that a user would plausibly say during an incident, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Tied narrowly to Documenso with distinctive 'documenso incident/outage/down' triggers, giving it a clear niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.