documenso-hello-world

Create a minimal working Documenso example. Use when starting a new Documenso integration, testing your setup, or learning basic document signing patterns. Trigger with phrases like "documenso hello world", "documenso example", "documenso quick start", "simple documenso code", "first document".

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.

The body is highly actionable with executable, well-structured code and useful reference tables, but it carries redundant language variants and an unlinked, duplicated reference file. Adding a pre-send verification step would raise the workflow's safety.

Suggestions

Link references/implementation-guide.md from the body and move the duplicated detail (overview, steps, field/error tables) there so the reference is one level deep and signaled, rather than duplicated inline.

Keep one primary language (TypeScript) inline and move the Python and curl equivalents into the reference file to reduce redundant tokens across three full reimplementations of the same workflow.

Add an explicit pre-send validation checkpoint before sendV0 (e.g. verify the recipient and at least one signature field exist) so an irreversible signing request is not sent against a malformed document.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but providing three full reimplementations (TypeScript, Python, curl) of the same 5-step workflow means not every token earns its place; it could be tightened by keeping one primary example and offloading the others.	2 / 3
Actionability	Code is fully executable and copy-paste ready with real SDK calls, specific run commands ("npx tsx documenso-hello.ts"), concrete field coordinates, and a working curl variant.	3 / 3
Workflow Clarity	The 5-step sequence (create, upload, recipient, field, send) is clearly ordered, but there is no validation checkpoint before the irreversible sendV0 call, which caps workflow clarity at 2 per the destructive/outward-operation guideline.	2 / 3
Progressive Disclosure	Sections are well organized, but the provided references/implementation-guide.md is never linked from the body and duplicates the body's content rather than splitting detail one level deep.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 cleanly answers both what and when with natural, distinctive trigger phrases in third-person voice. Its only weakness is that the capability statement describes a single action rather than enumerating the concrete operations the skill performs.

Dimension	Reasoning	Score
Specificity	The phrase "Create a minimal working Documenso example" names the domain and one concrete action, but it does not list multiple specific capabilities (e.g. create document, add recipient, send for signing) the way a score-3 anchor does.	2 / 3
Completeness	It explicitly states what the skill does ("Create a minimal working Documenso example") and when to use it ("Use when starting a new Documenso integration, testing your setup, or learning basic document signing patterns") with explicit trigger phrases.	3 / 3
Trigger Term Quality	Triggers like "documenso hello world", "documenso example", and "documenso quick start" are natural phrases a user would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (Documenso document signing) with Documenso-prefixed triggers, making it unlikely to fire for unrelated skills.	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
Commit: 02d6341

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