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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-prod-checklist85
Quality
83%
Does it follow best practices?
Impact
86%
1.32xAverage score across 3 eval scenarios
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 is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it mentions 'checklist and rollback procedures' but doesn't enumerate what those actually include, which could help Claude better understand the skill's full capabilities.
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'Execute Documenso production deployment checklist including environment verification, database migrations, webhook configuration, and rollback procedures.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso production deployment) and mentions actions (deployment checklist, rollback procedures), but doesn't list specific concrete actions like 'verify environment variables', 'run database migrations', or 'configure webhooks'. | 2 / 3 |
Completeness | Clearly answers both what (execute deployment checklist and rollback procedures) and when (deploying to production, preparing for launch, go-live procedures) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'documenso production', 'deploy documenso', 'documenso go-live', 'documenso launch checklist'. Good coverage of variations including 'launch', 'deploy', and 'go-live'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Documenso production deployments specifically. The product name 'Documenso' combined with deployment-specific terms creates clear distinctiveness unlikely to conflict with general deployment or other product skills. | 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 production deployment checklist with excellent actionability and workflow clarity. The step-by-step procedures with validation checkpoints and rollback procedures are well-designed. However, the skill is lengthy and could benefit from splitting detailed implementations (health checks, metrics) into separate reference files to improve token efficiency.
Suggestions
Extract the health check implementation (Step 3) and metrics collector (Step 4) into separate reference files like HEALTH_CHECK.md and METRICS.md, keeping only brief summaries in the main skill
Consider condensing the alert configuration section - the YAML example duplicates information already in the table above it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections. The health check and metrics collector implementations are quite lengthy and could be condensed or referenced externally. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, TypeScript code, kubectl commands, and curl examples. All code is copy-paste ready with specific commands for each deployment step. | 3 / 3 |
Workflow Clarity | Clear 5-step deployment procedure with explicit validation checkpoints (health checks, monitoring canary, error rate checks). Includes rollback procedures and post-deployment verification with specific timing guidance. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~250 lines) with substantial inline code that could be split into separate reference files. The health check and metrics implementations could be in separate files with links. References to external resources are present but internal structure could be better organized. | 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 | |
- 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.