documenso-common-errors

Diagnose and resolve common Documenso API errors and issues. Use when encountering Documenso errors, debugging integration issues, or troubleshooting failed operations. Trigger with phrases like "documenso error", "documenso 401", "documenso failed", "fix documenso", "documenso not working".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The content is highly actionable and concise, with concrete code and commands for each error scenario. It loses points on workflow clarity (no integrated diagnostic flow with validation feedback loops) and progressive disclosure (the available implementation-guide.md bundle is orphaned rather than referenced, while detailed content is inlined).

Suggestions

Add a short top-level diagnostic workflow or decision tree (e.g., check status code -> map to scenario -> apply fix -> verify) so the independent scenarios form a coherent sequence with a validate-fix-retry loop.

Link the existing references/implementation-guide.md from the body (e.g., 'For full per-error cause/solution detail, see implementation-guide.md') and move the duplicated detailed scenarios out of SKILL.md to reduce inline bulk.

Resolve the dangling 'documenso-debug-bundle' / 'documenso-install-auth' / 'documenso-rate-limits' references so every cited resource either exists in the bundle or is clearly marked as a sibling skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence, giving concrete diagnostic facts (e.g., 'pageX and pageY are PERCENTAGE-based (0-100), not pixel-based') without explaining concepts Claude already knows; only minor table redundancy keeps it from being perfectly tight, but it does not fall to the 'unnecessary explanation' level 2.	3 / 3
Actionability	It provides executable WRONG/CORRECT TypeScript blocks, copy-paste curl commands, and specific values/enums ('SIGNER, VIEWER, APPROVER, CC'; 'pageX: 10 // 10% from left edge'), meeting the copy-paste-ready bar.	3 / 3
Workflow Clarity	Individual scenarios include useful pre-checks (verifying doc status before modifying, checking file size before upload), but there is no overarching diagnostic sequence or validate-fix-retry feedback loop tying the scenarios into a coherent multi-step workflow.	2 / 3
Progressive Disclosure	The body is well-sectioned, but all ~195 lines of detailed scenarios are inlined while the existing bundle file (references/implementation-guide.md) is never linked from the body; 'Next Steps' instead points to a non-present 'documenso-debug-bundle', so the real bundle is not clearly signaled.	2 / 3
	Total	10 / 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.

A strong description: it explicitly covers both the what and when, lists natural trigger phrases, and occupies a distinct niche. Its only weakness is that the capability statement relies on two general verbs rather than a richer enumeration of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('common Documenso API errors and issues') and concrete actions ('Diagnose and resolve'), but uses only two general verbs rather than enumerating multiple distinct concrete actions, so it does not reach the comprehensive level 3.	2 / 3
Completeness	It states what the skill does ('Diagnose and resolve common Documenso API errors and issues') and gives an explicit 'Use when' clause covering when to invoke it, satisfying both requirements.	3 / 3
Trigger Term Quality	Natural user phrasings are explicitly listed ('documenso error', 'documenso 401', 'documenso failed', 'fix documenso', 'documenso not working'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (Documenso API errors) with Documenso-specific 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: 1 day 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.