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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with executable commands and code, and workflows are well sequenced with checkpoints, rollback, and a checklist. Its main weakness is progressive disclosure: a real reference file is never linked and a referenced target does not exist, and some detail duplicates the reference file.

Suggestions

Link references/implementation-guide.md explicitly from the body (e.g., 'For full API version differences and detailed migration steps, see references/implementation-guide.md') instead of leaving it unconnected.

Resolve the dangling 'documenso-ci-integration' reference in Next Steps — either create that bundle file or replace it with a real, linked reference path.

Trim the inline API version comparison and before/after migration blocks that duplicate implementation-guide.md, keeping the body as an overview that points to the deeper reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no preamble on what Documenso is), but the API version comparison table, inline before/after migration code, and the error-handling table substantially duplicate content found in references/implementation-guide.md; it could be tightened by pushing detail to the reference. Not the top 'every token earns its place' anchor (3), but not padded with concepts Claude already knows (1).	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (npm install, docker pull/compose) and complete TypeScript examples with env vars and SDK imports, matching the top anchor rather than pseudocode (2) or abstract direction (1).	3 / 3
Workflow Clarity	Five numbered steps are clearly sequenced, the feature-flag rollout includes explicit monitor/checkpoint stages (1→10%→100%), a rollback procedure is given, and a checkbox migration checklist closes the loop; matches the clear-sequence-with-validation anchor over the listed-but-gaps anchor (2).	3 / 3
Progressive Disclosure	Sections are reasonably organized, but there is a real structural gap: the bundle file references/implementation-guide.md is never linked from the body, and the body's 'Next Steps' points to 'documenso-ci-integration' which is not a real bundle file — references are present but not clearly signaled rather than a clean one-level-deep structure (3).	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is concrete, third-person, and includes explicit 'Use when' triggers covering both what the skill does and when to invoke it. It is specific to Documenso with natural trigger phrases and low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'upgrading from v1 to v2 API, updating SDK versions, or migrating between Documenso versions' — matches the anchor for specific concrete actions rather than vague domain naming (2).	3 / 3
Completeness	Explicitly answers what ('Manage Documenso API version upgrades and SDK migrations') and when ('Use when upgrading...') with explicit triggers, matching the top anchor; not capped at 2 since the 'Use when' clause is present.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('documenso upgrade', 'documenso v2 migration', 'update documenso SDK', 'documenso API version'); good coverage rather than just a few relevant keywords (2).	3 / 3
Distinctiveness Conflict Risk	Documenso-specific niche with distinct triggers tied to a named product/API version, unlikely to conflict with other skills; not merely 'Works with document files' (2).	3 / 3
	Total	12 / 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
Commit: 02d6341

Reviewed: 1 day 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.