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".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger terms and completeness. Its main weakness is that the capability description stays at a general level ('diagnose and resolve common errors') without enumerating specific error types or resolution actions. The Documenso-specific focus makes it highly distinctive and unlikely to conflict with other skills.
Suggestions
Add specific concrete actions like 'resolve 401 authentication errors, fix webhook delivery failures, debug document signing issues, troubleshoot API rate limits' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Documenso API errors) and general actions (diagnose, resolve), but doesn't list specific concrete actions like 'fix authentication errors, handle rate limits, debug webhook failures'. The actions remain at a high level. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and resolve common Documenso API errors) and 'when' (encountering errors, debugging integration issues, troubleshooting failed operations) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'documenso error', 'documenso 401', 'documenso failed', 'fix documenso', 'documenso not working'. These are realistic phrases a user would type when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Documenso is a specific product, and the focus on API errors/troubleshooting creates a clear niche. Very unlikely to conflict with other skills unless there's another Documenso skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality troubleshooting skill that provides concrete, executable solutions for common Documenso API errors. The WRONG/CORRECT code pattern is particularly effective for teaching error resolution. The main weakness is the lack of explicit feedback loops or retry-then-verify patterns in the multi-step scenarios, though this is a minor issue given the diagnostic nature of the skill.
Suggestions
Add a verify step after fixes in Scenarios 1-4 (e.g., 'After fixing the header, re-run the curl test from Debugging Quick Commands to confirm 200 response').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose with concrete code examples and tables. No unnecessary explanations of what APIs are or how HTTP works — it jumps straight to error-specific solutions. | 3 / 3 |
Actionability | Fully executable TypeScript code examples with clear WRONG/CORRECT patterns, copy-paste ready curl commands for debugging, and specific enum values and coordinate systems. Every scenario provides concrete, immediately usable solutions. | 3 / 3 |
Workflow Clarity | Individual scenarios are clear and well-sequenced, but the skill lacks explicit validation/feedback loops. For example, Scenario 3 mentions checking status before modifying but doesn't show a complete retry/recovery workflow. The webhook checklist is good but linear without error recovery steps. | 2 / 3 |
Progressive Disclosure | Well-structured with a quick-reference table up front, detailed scenarios in the middle, and clear references to related skills (`documenso-install-auth`, `documenso-rate-limits`, `documenso-debug-bundle`) and external resources. Content is appropriately organized for a single file with no need for splitting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
a04d1a2
- Reviewed
Table of Contents
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.