documenso-reference-architecture

Implement Documenso reference architecture with best-practice project layout. Use when designing new Documenso integrations, reviewing project structure, or establishing architecture standards for document signing applications. Trigger with phrases like "documenso architecture", "documenso best practices", "documenso project structure", "how to organize documenso".

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.

A well-organized, token-efficient architectural overview with concrete structure and an executable setup script, but it stops short of full actionability and clear progressive disclosure because the implementation-guide.md reference is orphaned and no validation checkpoints frame the setup workflow.

Suggestions

Add a clearly signaled link to references/implementation-guide.md (e.g., a '## Implementation guide' section: 'See [implementation-guide.md](references/implementation-guide.md) for full TypeScript client, service, and error-handling code') so the detailed code is discoverable.

Append a validation step to the setup workflow, such as running the verify-connection.ts health check or a 'tree src' sanity check, with explicit pass/fail guidance before proceeding.

Pull one small executable code snippet (e.g., the singleton client wrapper or a webhook verify snippet) inline so the body demonstrates the core pattern without requiring the reference.

Dimension	Reasoning	Score
Conciseness	The body is dense and diagram/table-driven with no padding explaining basics Claude already knows; the overview, layer rules, and decision tables each earn their place.	3 / 3
Actionability	The setup script and exact file tree are concrete and executable, but the actual implementation code (client, services, errors) lives only in the unreferenced implementation-guide.md, so the body's guidance is incomplete.	2 / 3
Workflow Clarity	A setup sequence and request/webhook data-flow sequences are present, but there are no validation checkpoints (e.g., the setup script never verifies the scaffold or runs the health check) and the skill is architectural rather than procedural.	2 / 3
Progressive Disclosure	The body is well-sectioned and keeps implementation detail out of the overview, but the bundle's primary reference file implementation-guide.md is never linked from SKILL.md, so navigation to the detailed content is missing.	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, well-formed description that states concrete capabilities, gives explicit 'Use when' triggers plus natural trigger phrases, and occupies a clearly distinct niche. It uses the third-person/imperative voice matching the rubric's good examples.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Implement Documenso reference architecture', 'designing new Documenso integrations', 'reviewing project structure', 'establishing architecture standards' — rather than vague language.	3 / 3
Completeness	Clearly answers both what ('Implement Documenso reference architecture with best-practice project layout') and when (an explicit 'Use when...' clause with concrete triggering situations).	3 / 3
Trigger Term Quality	Explicit 'Trigger with phrases like' clause gives natural terms a user would say ('documenso architecture', 'documenso best practices', 'documenso project structure', 'how to organize documenso').	3 / 3
Distinctiveness Conflict Risk	The Documenso niche is specific and all triggers are scoped to documenso, making conflict with unrelated skills unlikely.	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: 4 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.