documenso-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-common-errorsDiagnose 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
85%This is a strong troubleshooting skill with excellent actionability and clear organization. The error reference table combined with detailed code examples makes it highly practical. Minor verbosity in comments and unnecessary prerequisites section slightly reduce token efficiency, but overall the skill provides comprehensive, executable guidance for Documenso error resolution.
Suggestions
Remove the Prerequisites section - Claude already understands SDK basics and API keys
Trim obvious code comments like '// Recipient exists - find and update' that duplicate the surrounding context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally efficient with good use of tables and code examples, but includes some unnecessary elements like the 'Prerequisites' section (Claude knows what API keys are) and verbose comments explaining obvious things like 'Recipient exists - find and update'. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples for every error scenario, specific curl commands for debugging, and copy-paste ready solutions including retry logic, queue implementations, and validation functions. | 3 / 3 |
Workflow Clarity | Clear debugging checklist with numbered steps, explicit validation patterns (try/catch with status code checks), and proper feedback loops in retry logic. The error reference table provides quick navigation while detailed sections offer step-by-step resolution paths. | 3 / 3 |
Progressive Disclosure | Well-structured with quick reference table at top for fast lookup, detailed sections for deep dives, and clear one-level-deep references to external resources (status page, API docs, debug bundle). Content is appropriately organized for both quick scanning and detailed troubleshooting. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is the somewhat generic capability description - it could benefit from listing specific error types or troubleshooting actions rather than just 'diagnose and resolve common errors'.
Suggestions
Add specific concrete actions like 'resolve authentication (401) errors, fix webhook delivery failures, debug rate limiting issues, troubleshoot document signing failures'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso API) and general actions (diagnose, resolve errors, debugging), but doesn't list specific concrete actions like 'fix authentication errors, handle rate limits, resolve webhook failures'. | 2 / 3 |
Completeness | Clearly answers both what (diagnose and resolve Documenso API errors) and when (explicit 'Use when...' clause plus 'Trigger with phrases like...' providing concrete trigger guidance). | 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 match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Documenso' as a specific product name appearing in all triggers. Unlikely to conflict with other skills unless another Documenso skill exists. | 3 / 3 |
Total | 11 / 12 Passed |
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.