documenso-debug-bundle
Comprehensive debugging toolkit for Documenso integrations. Use when troubleshooting complex issues, gathering diagnostic information, or creating support tickets for Documenso problems. Trigger with phrases like "debug documenso", "documenso diagnostics", "troubleshoot documenso", "documenso support ticket".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-debug-bundle/SKILL.mdQuality
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 solid skill description that clearly identifies its niche (Documenso debugging) and provides explicit trigger guidance. Its main weakness is that the specific capabilities listed are somewhat generic debugging actions rather than concrete, detailed operations. The explicit trigger phrases and 'Use when' clause make it highly functional for skill selection.
Suggestions
Add more specific concrete actions beyond general debugging terms, e.g., 'inspect API logs, validate webhook configurations, check authentication tokens, analyze signing workflow errors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso integrations debugging) and mentions some actions (troubleshooting, gathering diagnostic information, creating support tickets), but these are fairly general debugging activities rather than highly specific concrete actions like 'analyze API response codes' or 'validate webhook configurations'. | 2 / 3 |
Completeness | Clearly answers both 'what' (debugging toolkit for Documenso integrations: troubleshooting, gathering diagnostics, creating support tickets) and 'when' (explicit 'Use when' clause plus specific trigger phrases). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'debug documenso', 'documenso diagnostics', 'troubleshoot documenso', 'documenso support ticket' which are natural terms a user would say. The product name 'Documenso' is consistently mentioned, and variations of debugging terminology are covered. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is highly distinctive due to the specific product name 'Documenso' combined with debugging/diagnostics focus. It is very unlikely to conflict with other skills unless there are multiple Documenso-related skills, and even then the debugging focus narrows it further. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable debugging tools for Documenso integrations with complete bash and TypeScript scripts. Its main weaknesses are verbosity (the full code blocks make it quite long) and lack of explicit decision points between diagnostic steps. The error handling table and support ticket template add practical value but the overall structure could better guide Claude through a conditional debugging workflow.
Suggestions
Add explicit decision points between steps (e.g., 'If Step 1 fails with 401, skip to Error Handling table; if it passes, proceed to Step 2') to create a proper diagnostic workflow with feedback loops.
Move the full diagnostic script and debug client wrapper to referenced files (e.g., 'See scripts/documenso-diagnose.ts') and keep only key snippets or usage examples inline to reduce token usage.
Remove the 'Current State' shell commands at the top and the 'Overview' paragraph — Claude doesn't need to be told what the skill is about when the instructions themselves are clear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with some unnecessary elements (the 'Current State' shell commands at the top, the overview section explaining what the skill does, and the prerequisites section stating obvious requirements). The code examples themselves are well-written but the debug logging wrapper proxy pattern is quite verbose and could be trimmed. The support ticket template, while useful, adds significant length. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash and TypeScript scripts that can be copy-pasted directly. The connectivity test script, diagnostic script, and debug client wrapper are all complete and runnable with clear execution commands (e.g., `npx tsx scripts/documenso-diagnose.ts`). | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but there's no explicit validation checkpoint or feedback loop between steps. The workflow doesn't clearly state when to proceed to the next step based on results of the previous one — e.g., if Step 1 connectivity fails, should you skip Step 2? The error handling table at the end is helpful but disconnected from the workflow steps. | 2 / 3 |
Progressive Disclosure | The content is mostly inline in one large file with substantial code blocks that could be referenced as separate script files. The single reference to `documenso-rate-limits` at the end is good, but the skill would benefit from splitting the diagnostic script and debug client into referenced files rather than embedding them entirely. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.