documenso-migration-deep-dive
Execute comprehensive Documenso migration strategies for platform switches. Use when migrating from other signing platforms, re-platforming to Documenso, or performing major infrastructure changes. Trigger with phrases like "migrate to documenso", "documenso migration", "switch to documenso", "documenso replatform", "replace docusign".
79
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-migration-deep-dive/SKILL.mdQuality
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 description with strong trigger terms and clear 'what/when' guidance. Its main weakness is the lack of specific concrete actions—'comprehensive migration strategies' is vague and could be improved by listing actual migration steps like data export, template migration, or API reconfiguration. The explicit trigger phrase list is a notable strength.
Suggestions
Replace 'comprehensive migration strategies' with specific concrete actions like 'export documents, migrate templates, transfer user accounts, reconfigure API integrations' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Documenso migration, platform switches) and mentions some actions like 'migrating from other signing platforms' and 'major infrastructure changes', but it doesn't list multiple specific concrete actions (e.g., data export, template migration, API key setup, user account transfer). 'Comprehensive migration strategies' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute migration strategies for platform switches) and 'when' (migrating from other signing platforms, re-platforming, major infrastructure changes) with explicit trigger phrases listed separately. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would say: 'migrate to documenso', 'documenso migration', 'switch to documenso', 'documenso replatform', 'replace docusign'. These are realistic user queries and include a competitor name (DocuSign) which is a strong natural trigger. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Documenso-specific migration. The product name 'Documenso' and migration-specific triggers make it very unlikely to conflict with other skills. Even among Documenso-related skills, the migration focus is distinct. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured migration guide with clear phasing, a solid rollback strategy, and useful reference tables. Its main weaknesses are that the code examples are illustrative rather than truly executable (missing imports, undefined dependencies), and the content is too long for a single SKILL.md without supporting bundle files to offload reference material. The workflow clarity is the strongest dimension, with explicit phases and error recovery guidance.
Suggestions
Make code examples more executable by including actual Documenso SDK imports and realistic client initialization, or explicitly mark them as templates to be adapted rather than presenting them as runnable code.
Split the feature mapping table, template definitions, and error handling table into separate bundle files (e.g., FEATURE_MAP.md, TEMPLATES.md, TROUBLESHOOTING.md) and reference them from the main SKILL.md to improve progressive disclosure.
Remove the `!npm list` current state check at the top — it's unclear how this helps the migration process and adds noise.
Trim the MigrationAssessment interface example in Step 1 — Claude doesn't need a full TypeScript interface to understand what to inventory; a checklist would be more concise and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes unnecessary verbosity in several places — the ASCII diagrams, while helpful, are somewhat redundant with the timeline table. The feature mapping table and template definitions are useful but could be tighter. The `MigrationAssessment` interface in Step 1 is more illustrative than actionable. Some explanatory text (e.g., 'Comprehensive guide for migrating...') could be trimmed. | 2 / 3 |
Actionability | The TypeScript code examples are concrete and illustrative but not fully executable — they reference undefined functions (sendViaDocumenso, sendViaLegacy, documensoClient) and interfaces without imports or setup. The template migration step explicitly says 'create each template in the Documenso UI' rather than providing API calls. The rollback procedure with bash commands is actionable, but overall the code is closer to pseudocode with types than copy-paste ready. | 2 / 3 |
Workflow Clarity | The multi-step migration process is clearly sequenced across 6 steps with a timeline table, explicit phases (shadow → pilot → expand → cutover → decommission), and a rollback procedure. The parallel/shadow testing phase serves as a validation checkpoint, and the error handling table addresses common failure modes with solutions. The feature flag approach provides a clear feedback loop for gradual rollout. | 3 / 3 |
Progressive Disclosure | The content is a long monolithic document (~200 lines) with no bundle files to offload detail into. The feature mapping table, template definitions, and error handling tables could be split into separate reference files. References to external resources exist but there are no internal file references for deeper content. The mention of 'documenso-install-auth' as a prerequisite skill is good but the overall structure would benefit from splitting. | 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 | |
- 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.