documenso-upgrade-migration
Manage Documenso API version upgrades and SDK migrations. Use when upgrading from v1 to v2 API, updating SDK versions, or migrating between Documenso versions. Trigger with phrases like "documenso upgrade", "documenso v2 migration", "update documenso SDK", "documenso API version".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 well-structured skill description with excellent completeness and distinctiveness. It clearly identifies both what the skill does and when to use it, with explicit trigger phrases. The main weakness is that the specific capabilities could be more granular — listing concrete migration actions rather than staying at the category level of 'upgrades and migrations'.
Suggestions
Add more specific concrete actions such as 'update endpoint URLs, refactor authentication flows, migrate webhook configurations, update request/response schemas' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso API) and some actions (version upgrades, SDK migrations), but doesn't list specific concrete actions like 'update endpoint URLs', 'refactor authentication calls', or 'migrate webhook handlers'. The actions remain at a general category level. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Documenso API version upgrades and SDK migrations) and 'when' (upgrading from v1 to v2 API, updating SDK versions, migrating between versions) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'documenso upgrade', 'documenso v2 migration', 'update documenso SDK', 'documenso API version', 'v1 to v2 API', 'SDK versions'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Documenso), specific task type (API version upgrades/SDK migrations), and specific version transitions (v1 to v2). Very unlikely to conflict with other 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 solid migration skill with excellent actionability—concrete before/after code, Docker commands, and test examples make it immediately usable. The workflow is well-sequenced with proper validation (parity tests, gradual rollout, rollback). The main weakness is that the content is somewhat long for a SKILL.md and could be more concise by trimming obvious prerequisites and splitting detailed code into referenced files.
Suggestions
Remove the Prerequisites section—Claude doesn't need to be told to have a working integration and test environment before migrating.
Consider moving the detailed migration code examples (feature flag pattern, parity tests) into a separate MIGRATION-PATTERNS.md file and referencing it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements like the prerequisites section (Claude knows to have a working integration and test environment) and the overview explanation of what v1 and v2 are could be tighter. The API version comparison table is useful but some rows like 'Authentication' (same for both) add little value. | 2 / 3 |
Actionability | Provides fully executable code examples for SDK upgrade commands, before/after migration code in TypeScript, feature flag implementation, Docker upgrade commands, and parity tests. The code is copy-paste ready with concrete examples throughout. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow with explicit validation checkpoints: testing parity between v1/v2, gradual rollout with feature flags (staging → 10% → 100%), Docker log verification, health check curl, and rollback instructions. The migration checklist provides an additional verification layer. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's quite long (~150 lines of substantive content) and could benefit from splitting detailed code examples (migration patterns, test templates) into separate reference files. The single reference to 'documenso-ci-integration' is good but more could be externalized. | 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
70e9fa4
- 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.