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".
68
83%
Does it follow best practices?
Impact
—
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 is a solid description with clear 'when' triggers and good distinctiveness due to the named product focus. Its main weakness is that the 'what' could be more specific — listing concrete checklist items or rollback steps would strengthen it. The explicit trigger phrases section is a strong addition that aids skill selection.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Runs pre-deployment health checks, verifies environment variables, executes database migrations, and performs version rollback if errors are detected.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso production deployment) and mentions some actions ('deployment checklist', 'rollback procedures'), but doesn't list specific concrete actions like what the checklist entails or what rollback steps involve. | 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 trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'documenso production', 'deploy documenso', 'documenso go-live', 'documenso launch checklist'. Good coverage of natural variations for this specific domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific product (Documenso) and a specific phase (production deployment/rollback). Unlikely to conflict with other skills due to the narrow, named-product focus. | 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 — the verification script, rollback commands, and specific alerting thresholds make it immediately usable. The workflow is well-sequenced with validation checkpoints and error recovery paths. The main weakness is that the content is somewhat long for a single SKILL.md and could benefit from splitting self-hosted and compliance sections into separate referenced files.
Suggestions
Consider splitting the self-hosted production section into a separate referenced file to reduce the main skill's length and improve progressive disclosure.
Remove parenthetical explanations that Claude would already know (e.g., '(not creating new client per request)', '(emails actually deliver)') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient for a checklist-style skill, but some sections are somewhat verbose. The checklist items are well-structured, though the error handling table and some explanatory parentheticals (e.g., '(not creating new client per request)', '(emails actually deliver)') add minor bloat. The verification script is appropriately detailed without being wasteful. | 2 / 3 |
Actionability | The skill provides a fully executable verification bash script, concrete kubectl/vercel rollback commands, specific threshold values for alerting (>5% for 5 min, p95 >5s), and actionable checklist items with specific tools named. The rollback procedure has copy-paste ready commands. | 3 / 3 |
Workflow Clarity | The skill presents a clear multi-step deployment workflow: prerequisites → checklist verification → pre-deployment script → go-live → error response → rollback. The rollback procedure includes explicit validation steps (verify rollback with health check, investigate, fix and re-deploy). The error handling table provides clear condition → response mappings for post-deployment issues. | 3 / 3 |
Progressive Disclosure | The skill references other skills (`documenso-ci-integration`, `documenso-observability`, `documenso-upgrade-migration`) and external resources, which is good. However, the content is quite long (~150 lines of checklist items) and some sections like the self-hosted items could potentially be split out. No bundle files are provided to support the references, though the cross-skill references are reasonable. | 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
a04d1a2
- 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.