documenso-prod-checklist

Execute Documenso production deployment checklist and rollback procedures. Use when deploying Documenso integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "documenso production", "deploy documenso", "documenso go-live", "documenso launch checklist".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with executable scripts and well-sequenced rollback/validation steps, and it avoids explaining concepts Claude already knows. Its weaknesses are minor internal redundancy and a missing link to the bundled implementation-guide.md that already contains the detailed deployment procedure.

Suggestions

Add a clearly signaled link to references/implementation-guide.md (e.g., 'For the full deployment procedure with canary rollout, see [implementation-guide.md](references/implementation-guide.md)') so the bundle file is discoverable instead of orphaned.

Remove the duplicate 'Error Handling' table at the end or merge it into section 2 to eliminate redundancy and tighten token usage.

Consider moving the pre-deployment verification script into the implementation guide to keep SKILL.md a lean overview, or explicitly justify keeping it inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with terse checklists and code blocks, but it could be tightened: the 'Error Handling' table near the end duplicates section 2's checklist, and the inline verification/rollback scripts overlap content that also lives in the implementation guide.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance: a complete bash verification script, concrete kubectl rollback commands, and specific thresholds ('> 5% for 5 minutes', 'p95 > 5s', 'openssl rand -hex 32').	3 / 3
Workflow Clarity	The rollback procedure is clearly sequenced with a verify step and a fix-and-redeploy loop, and the pre-deployment verification script plus go-live checklist supply explicit validation checkpoints for a risky operation.	3 / 3
Progressive Disclosure	Sections are organized and one reference file exists (references/implementation-guide.md), but the body never links to it, and the verification/rollback scripts are inline rather than split out — matching anchor 2 (references present but not clearly signaled, content that could be separate is inline).	2 / 3
	Total	10 / 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.

The description is well-constructed: it states the capability, gives an explicit 'Use when' clause, and lists natural trigger phrases in third person. Its only weakness is specificity, since it names just two rather generic actions instead of a richer set of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the Documenso domain and a couple of actions ('Execute Documenso production deployment checklist and rollback procedures'), but these are only two fairly generic actions rather than a comprehensive list of concrete capabilities, matching anchor 2.	2 / 3
Completeness	Explicitly answers both what ('Execute Documenso production deployment checklist and rollback procedures') and when ('Use when deploying Documenso integrations to production, preparing for launch, or implementing go-live procedures' plus trigger phrases), matching the anchor 3 example.	3 / 3
Trigger Term Quality	Provides good natural-language coverage users would actually say ('documenso production', 'deploy documenso', 'documenso go-live', 'documenso launch checklist') alongside 'Use when deploying... preparing for launch... go-live procedures'.	3 / 3
Distinctiveness Conflict Risk	'Documenso production' is a clear niche with distinct, product-specific triggers, making it unlikely to fire for unrelated 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: 3 days 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.