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, clearly specifying both what the skill does and when to use it with explicit trigger phrases. The main weakness is that the capability description could be more specific about the concrete actions performed during a migration (e.g., updating endpoints, changing authentication patterns, refactoring API calls). Overall it is a strong description for skill selection purposes.
Suggestions
Add more specific concrete actions like 'update API endpoints, 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 high 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. | 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'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Documenso), a specific task (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, actionable migration guide with excellent concrete code examples and a well-sequenced workflow including validation and rollback steps. Its main weakness is that it's somewhat lengthy for a single SKILL.md file—the detailed code examples for feature flags, Docker upgrades, and parity tests could be split into separate referenced files. Minor verbosity in explanatory sections could be trimmed.
Suggestions
Consider splitting the feature flag migration code, Docker upgrade commands, and parity test into separate bundle files (e.g., migration-pattern.ts, docker-upgrade.sh, parity-test.ts) and referencing them from SKILL.md to improve progressive disclosure.
Trim the prerequisites section and overview paragraph—Claude doesn't need to be told to have a working integration or test environment, and the v1/v2 distinction is adequately conveyed by the comparison table.
| 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 paragraph explaining what v1 and v2 are could be tighter. The API version comparison table is useful but some rows (like Authentication being 'same') add little value. The gradual rollout comments (10%, monitor, roll to 100%) are somewhat verbose. | 2 / 3 |
Actionability | The skill provides fully executable code examples for every step: bash commands for SDK upgrades, complete TypeScript before/after migration code, Docker commands for self-hosted upgrades, and a vitest parity test. The feature flag migration pattern is copy-paste ready with a concrete implementation. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from SDK upgrade through testing, with explicit validation checkpoints: checking current version first, verifying via docker logs and health endpoint, parity testing between v1/v2, and a comprehensive migration checklist. The rollback procedure for self-hosted upgrades and the gradual rollout strategy with feature flags provide good error recovery paths. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's quite long for a single file with no bundle files to offload detail into. The complete migration code examples, Docker commands, and test files could be split into referenced files. The single reference to 'documenso-ci-integration' at the end is appropriate but the inline content is heavy. | 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
3a2d27d
- 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.