documenso-upgrade-migration
Execute 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-upgrade-migration80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 that the capabilities could be more specific about what concrete actions the skill performs during migrations (e.g., endpoint updates, authentication changes, schema modifications).
Suggestions
Add 2-3 specific concrete actions like 'updates authentication flows, refactors deprecated endpoints, migrates webhook configurations' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso API/SDK) and general actions (upgrades, migrations), but lacks specific concrete actions like 'update authentication methods', 'refactor endpoint calls', or 'modify request/response handling'. | 2 / 3 |
Completeness | Clearly answers both what (execute API upgrades and SDK migrations) and when (upgrading v1 to v2, updating SDK versions, migrating between versions) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'documenso upgrade', 'documenso v2 migration', 'update documenso SDK', 'documenso API version'. Good coverage of variations including version-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Documenso' as a specific product name, combined with version-specific triggers (v1, v2). Unlikely to conflict with generic upgrade or migration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 guide with excellent actionability - the before/after code examples are comprehensive and executable. However, it's overly long for a SKILL.md file, mixing quick-reference migration steps with detailed implementation patterns that could be in separate files. The workflow lacks explicit validation checkpoints critical for production migrations.
Suggestions
Add explicit validation checkpoints after each migration step (e.g., 'Test document creation works before proceeding to Step 5')
Move the 'Gradual Migration Strategy' and 'Adapter Pattern' sections to a separate MIGRATION_PATTERNS.md file, keeping only a brief reference in the main skill
Add a pre-migration checklist with verification steps (e.g., 'Verify v2 SDK installed: npm list @documenso/sdk-typescript')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the gradual migration strategy section which is quite verbose, and the week-by-week rollout plan that could be condensed. The comparison table and code examples are well-structured but the overall document is longer than necessary. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples showing before/after patterns for each migration step. Commands are copy-paste ready, and the code covers all major operations (documents, recipients, fields, templates, webhooks). | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints between steps. For a migration involving potentially destructive changes to production integrations, there should be explicit 'verify this works before proceeding' checkpoints after each step rather than just a testing section at the end. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is monolithic at ~300 lines. The adapter pattern and gradual migration strategy sections could be split into separate reference files. References to external resources are present but inline content is heavy. | 2 / 3 |
Total | 9 / 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.