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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/documenso-pack/skills/documenso-reference-architecture/SKILL.md

Quality

Content

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

The body is well-organized and offers a concrete, executable scaffold script with clear architectural rules, but it keeps full implementation detail inline while leaving its actual bundle file (implementation-guide.md) unreferenced, and it provides no executable implementation code or explicit validated workflow for the webhook/signing operations it describes.

Suggestions

Link references/implementation-guide.md from the body (e.g. 'For full implementation code and per-layer details, see [implementation-guide.md](references/implementation-guide.md)') and trim the duplicated project-structure/layer-architecture trees from SKILL.md to an overview.

Add an explicit numbered workflow for a signing or webhook integration (scaffold → implement client → implement service → wire webhook → verify) with a validation checkpoint (e.g. run scripts/verify-connection.ts) before proceeding.

Include at least one copy-paste-ready executable code example for a core operation (e.g. the webhook verify.ts secret check or a document-service create call) rather than only describing file responsibilities.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the full project-structure tree and layer-architecture diagram duplicate content that lives in the bundled references/implementation-guide.md, and the large ASCII data-flow diagrams add tokens Claude largely doesn't need — it could be tightened.	2 / 3
Actionability	The setup script is concrete and executable, and the structure/rules are specific, but there is no executable service/client implementation code — the skill describes layer responsibilities and references filenames rather than giving copy-paste-ready code for the actual signing or webhook logic.	2 / 3
Workflow Clarity	There is no explicit numbered end-to-end workflow; the 'Setup Script' gives a one-shot scaffold with no validation checkpoint, and webhook processing — a batch/external operation — lacks a validate-then-proceed feedback loop, capping clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	The bundle file references/implementation-guide.md exists but is never linked or signaled from the body, and the body duplicates its project-structure and layer-architecture content inline; the only 'see ...' pointers target other skills (documenso-sdk-patterns, documenso-multi-env-setup) that are not in the bundle, leaving a monolithic inline body with the bundled detail orphaned.	1 / 3
	Total	7 / 12 Passed

Description

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

The description is well-crafted: third-person voice, concrete actions, an explicit 'Use when' trigger clause, and natural trigger phrases tied to a distinct Documenso niche. It hits the high anchor on all four dimensions without verbosity or over-claiming.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'designing new Documenso integrations, reviewing project structure, or establishing architecture standards for document signing applications' — three distinct, specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' ('Implement Documenso reference architecture with best-practice project layout') and 'when' via an explicit 'Use when...' clause with concrete triggers, meeting the completeness bar for a 3.	3 / 3
Trigger Term Quality	Provides explicit natural trigger phrases a user would actually say: 'documenso architecture', 'documenso best practices', 'documenso project structure', 'how to organize documenso' — good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Documenso document-signing architecture) with distinct triggers tied to 'documenso' — unlikely to conflict with generic document or signing 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
Path: plugins/saas-packs/documenso-pack/skills/documenso-reference-architecture/SKILL.md
Commit: 0540a62

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