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".

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and presents a clearly sequenced migration workflow with validation and rollback. Its main weakness is progressive disclosure: a detailed implementation-guide.md bundle file is present but never referenced from the body, while overlapping content stays inline.

Suggestions

Add a clearly signaled one-level-deep link to references/implementation-guide.md (e.g. an '## Advanced migration' section: 'For recipient, field, template, and webhook migration plus the adapter pattern, see [implementation-guide.md](references/implementation-guide.md)') so the bundle file is discoverable.

Move the duplicated v1/v2 comparison and SDK update detail out of the body into the implementation guide, keeping the SKILL.md body as a concise overview to reduce overlap.

Replace the bare 'see documenso-ci-integration' next-step pointer with an explicit reference path or skill name format so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and domain-specific (e.g. "v1 (legacy, document-centric) and v2 (recommended, envelope-based)") with no generic concept explanations; every section earns its place; not below 3 because nothing is padded.	3 / 3
Actionability	Concrete executable code and commands throughout ("npm install @documenso/sdk-typescript@latest", "client.documents.createV0({ title: \"Contract\" })", "docker pull documenso/documenso:latest") are copy-paste ready; not below 3 because examples are complete and specific.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with validation checkpoints ("Monitor error rates", Step 4 "Verify" via docker logs and curl health, Step 5 parity tests) plus rollback and a migration checklist; not below 3 because feedback loops exist for the risky rollout.	3 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists with substantial detail but is never signaled or linked from the body, and overlapping content (v1/v2 comparison, SDK update, gradual migration) is kept inline; not 3 because the reference is not clearly navigated to, not 1 because the body is well-sectioned rather than a monolithic wall.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description with explicit what/when structure, natural trigger phrases, and a clear Documenso-specific niche. The only weakness is that the capability statement names two fairly abstract action areas rather than enumerating several concrete operations.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Documenso API version upgrades and SDK migrations" name the domain and two action areas (upgrades, migrations), but stop short of the multiple concrete actions a score-3 anchor lists; not below 2 because it is not vague.	2 / 3
Completeness	Answers what ("Manage Documenso API version upgrades and SDK migrations") and when ("Use when upgrading from v1 to v2 API, updating SDK versions, or migrating between Documenso versions") with explicit trigger guidance; not below 3 because both what and when are explicit.	3 / 3
Trigger Term Quality	Explicit trigger phrases "documenso upgrade", "documenso v2 migration", "update documenso SDK", "documenso API version" are natural terms a user would say; not below 3 because coverage is good rather than partial.	3 / 3
Distinctiveness Conflict Risk	The Documenso-specific niche and version-scoped triggers ("documenso v2 migration") make conflict with other skills unlikely; not below 3 because the niche is clear and distinct.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/documenso-pack/skills/documenso-upgrade-migration/SKILL.md
Commit: 8585d6d

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.