documenso-core-workflow-a

Implement Documenso document creation and recipient management workflows. Use when creating documents, managing recipients, adding signature fields, or building signing workflows with Documenso. Trigger with phrases like "documenso document", "create document", "add recipient", "documenso signer", "signature field".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

Highly actionable with executable SDK code and a clear step sequence, but it loses points for repetitive examples, a missing pre-send validation checkpoint, and an orphaned local reference file that is never linked from the body.

Suggestions

Add an explicit validation checkpoint before sendV0 (e.g., verify recipients, fields, and document status are DRAFT) so the workflow has a feedback loop for this irreversible step.

Tighten Step 4 by showing one representative field creation and summarizing the other types in a compact table, and have Step 5 reuse the Step 1 setup rather than re-declaring the client, document, and file upload.

Link the bundled references/implementation-guide.md from the body (e.g., in a Resources or Advanced section) so the supplementary reference is discoverable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code with brief comments and no concept filler, but Step 4 repeats four near-identical createV0 field blocks and Step 5 re-establishes the client/document/file-upload already shown in Step 1, so it could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript using real SDK methods (createV0, setFileV0, sendV0, findV0, getV0) plus a v1 REST/fetch example, with imports and concrete arguments — copy-paste ready.	3 / 3
Workflow Clarity	Steps 1–7 are clearly sequenced and supported by a status-flow diagram and error table, but there is no explicit validation checkpoint before the consequential sendV0 call (sending to recipients is effectively irreversible), which caps this dimension at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned and links external docs and a sibling skill, but the bundled references/implementation-guide.md is never referenced from the body, so a real reference file goes unsignaled.	2 / 3
	Total	9 / 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.

A strong description: it states concrete capabilities, gives explicit "Use when…" guidance, lists natural trigger phrases, and is tightly scoped to the Documenso niche. No meaningful weaknesses under this rubric.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "document creation and recipient management workflows", "creating documents, managing recipients, adding signature fields, or building signing workflows" — rather than vague language.	3 / 3
Completeness	Explicitly states what ("Implement Documenso document creation and recipient management workflows") and when (an explicit "Use when…" clause plus a "Trigger with phrases like…" list), satisfying both halves.	3 / 3
Trigger Term Quality	Includes natural phrases a user would say — "create document", "add recipient", "documenso signer", "signature field" — giving good coverage of likely utterances.	3 / 3
Distinctiveness Conflict Risk	Scoped to Documenso with tool-specific triggers ("documenso document", "documenso signer"), carving a clear niche unlikely to fire for unrelated skills.	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: 3022dd3

Reviewed: about 2 hours 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.