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".
89
88%
Does it follow best practices?
Impact
Pending
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 strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capabilities described are somewhat generic ('diagnose and resolve') without listing specific error types or concrete troubleshooting actions. The Documenso-specific focus makes it highly distinctive.
Suggestions
Add more specific concrete actions, e.g., 'Diagnose authentication failures (401), permission errors (403), rate limits, webhook delivery issues, and malformed API requests for Documenso.'
| 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 | Documenso is a specific product, making this highly distinctive. The trigger terms are all Documenso-specific, so there's very low risk of conflicting with other skills unless there are multiple Documenso-related skills. | 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 strong troubleshooting skill with excellent actionability — the WRONG/CORRECT code patterns, percentage-based field coordinates, and curl debugging commands are exactly what Claude needs. The HTTP error reference table provides efficient lookup. The main weakness is the lack of a unified diagnostic workflow that sequences how to approach an unknown error, though individual scenarios are well-handled.
Suggestions
Add a brief top-level diagnostic flowchart or decision tree (e.g., 'Check HTTP status → match scenario → apply fix → verify with curl command') to improve workflow clarity for unknown errors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section addresses a specific error scenario with concrete code examples. No unnecessary explanations of what Documenso is or how APIs work in general — it jumps straight to actionable troubleshooting. | 3 / 3 |
Actionability | Each scenario provides fully executable TypeScript code with clear WRONG/CORRECT patterns, copy-paste ready curl commands for debugging, and specific checklists. The field coordinate example (percentage vs pixel) is particularly valuable and concrete. | 3 / 3 |
Workflow Clarity | Individual scenarios are clear, but there's no overarching diagnostic workflow (e.g., 'first check X, then try Y'). The webhook troubleshooting checklist is well-sequenced, but scenarios like modifying sent documents lack explicit validation/retry loops — it tells you to check status but doesn't show a complete recovery workflow. | 2 / 3 |
Progressive Disclosure | Well-structured with a summary table up front, detailed scenarios in the middle, and clear one-level-deep references to related skills (`documenso-install-auth`, `documenso-rate-limits`, `documenso-debug-bundle`) and external resources. Content is appropriately scoped without being monolithic. | 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
c8a915c
- 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.