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".
88
87%
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 is a solid description with excellent completeness and distinctiveness due to the specific product name and deployment context. The trigger terms are well-chosen and naturally phrased. The main weakness is that the specific capabilities could be more detailed — listing concrete checklist items or rollback steps would strengthen the specificity dimension.
Suggestions
Add more specific concrete actions, e.g., 'Runs pre-deployment health checks, validates environment variables, executes database migrations, and performs 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 specific to Documenso production deployments — the combination of the product name 'Documenso' with 'production deployment' and 'rollback' creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 skill with excellent actionability through executable scripts, concrete commands, and specific thresholds. The workflow is well-sequenced with clear validation checkpoints and rollback procedures. Minor verbosity in some checklist annotations and slight redundancy between the error handling table and rollback section prevent a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with checklist format, but some items are somewhat verbose or explanatory where Claude could infer (e.g., 'not creating new client per request', 'HTTP rejected by Documenso'). The error handling table at the end partially duplicates the rollback section. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | The skill provides a fully executable verification bash script, concrete kubectl/vercel rollback commands, specific curl commands for health checks, and detailed checklists with specific tools and thresholds (e.g., 'p95 > 5s', '> 5% for 5 minutes'). The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The deployment workflow is clearly sequenced: prerequisites → checklist verification → pre-deployment script → go-live → rollback procedure. The rollback section includes explicit validation steps (verify rollback with curl, investigate, fix and re-deploy cycle). The go-live checklist enforces ordering with prerequisite checks. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external resources at one level deep: CI integration (`documenso-ci-integration`), observability (`documenso-observability`), upgrade migration (`documenso-upgrade-migration`), and external docs. The main content stays focused on the production checklist without inlining detailed sub-topics. | 3 / 3 |
Total | 11 / 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
c8a915c
- 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.