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

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/documenso-pack/skills/documenso-hello-world/SKILL.md

Quality

Content

65%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.

Highly actionable with executable examples, but it spends tokens on triple-language duplication, lacks inline validation checkpoints, and fails to wire its existing reference file into the body.

Suggestions

Pick one primary language (TypeScript) inline and move the Python and curl equivalents into references/implementation-guide.md, linking to them from the body.

Add a verification checkpoint after document creation (e.g., "Confirm doc.documentId is set before uploading the PDF") and reference the error-handling table inline at each risky step.

Link the existing references/implementation-guide.md from a dedicated section so the bundle file is discoverable.

Dimension	Reasoning	Score
Conciseness	The body is code-focused and avoids explaining concepts Claude already knows, but it ships three full language equivalents (TypeScript, Python, curl) of the same workflow, which is more token budget than a hello-world skill needs.	2 / 3
Actionability	It provides fully executable, copy-paste-ready code with concrete commands (`npx tsx documenso-hello.ts`), real API endpoints, and specific field coordinates — no pseudocode.	3 / 3
Workflow Clarity	Steps are clearly sequenced and numbered, but there are no explicit validation checkpoints (e.g., confirm the document ID before adding a recipient) and the error-handling table is reference material rather than inline feedback loops.	2 / 3
Progressive Disclosure	The bundle contains references/implementation-guide.md, but the body never links to or signals it, and reference material (field types, lifecycle, error handling) is inline rather than split out.	2 / 3
	Total	9 / 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-formed description with explicit trigger guidance and a distinct niche; the only weakness is that the capability statement is singular and somewhat abstract rather than enumerating concrete actions.

Suggestions

Replace the single action "Create a minimal working Documenso example" with a concrete list, e.g. "Create a document, upload a PDF, add a recipient and signature field, and send it for signing."

Trim the formulaic "Trigger with phrases like..." list to the 2–3 most natural terms to reduce redundancy.

Dimension	Reasoning	Score
Specificity	The phrase "Create a minimal working Documenso example" names the domain and a single action, but does not enumerate multiple concrete capabilities (e.g., create document, add recipient, add field, send) the way the anchor-3 example does.	2 / 3
Completeness	It states what ("Create a minimal working Documenso example") and an explicit when ("Use when starting a new Documenso integration, testing your setup, or learning basic document signing patterns"), satisfying both requirements.	3 / 3
Trigger Term Quality	It lists natural trigger phrases a user would say — "documenso hello world", "documenso example", "documenso quick start", "simple documenso code", "first document" — covering the common variations for a hello-world skill.	3 / 3
Distinctiveness Conflict Risk	"Documenso" is a clearly scoped niche with dedicated trigger phrases, 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
Path: plugins/saas-packs/documenso-pack/skills/documenso-hello-world/SKILL.md
Commit: 4c47e33

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