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/diagnostics) 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
Replace generic actions like 'troubleshooting complex issues' with more specific capabilities, e.g., 'inspect API logs, validate webhook configurations, check authentication tokens, analyze error responses'.
| 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 'inspect webhook payloads'. | 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 'Trigger with phrases like' providing concrete trigger guidance). | 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. Good coverage of variations around the debugging/troubleshooting domain for this specific tool. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Documenso' combined with the debugging/diagnostics focus. Very unlikely to conflict with other skills unless there are multiple Documenso-related skills. | 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 good code quality and practical error handling tables. Its main weaknesses are the monolithic structure (large code blocks inline rather than referenced) and the lack of explicit decision points or validation checkpoints between diagnostic steps. The content could be tightened by removing the redundant overview and prerequisites sections.
Suggestions
Add decision points between steps: e.g., 'If Step 1 connectivity test passes, skip to Step 3 for logging; if it fails, check the Error Handling table before proceeding.'
Extract the bash script, TypeScript diagnostic, and debug client into separate bundle files and reference them from SKILL.md to improve progressive disclosure.
Remove the 'Current State' shell commands at the top and the 'Overview' section which largely repeats the skill description — start directly with Prerequisites or Step 1.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the 'Current State' shell commands at the top (which are unusual and not clearly justified), the Overview section restating the description, and the Prerequisites section listing obvious requirements. The code examples themselves are well-sized but the overall document could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash and TypeScript scripts that are copy-paste ready. The connectivity test, diagnostic script, and debug logging wrapper are all complete, runnable code 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 use which step or how results from Step 1 should inform whether to proceed to Step 2. For a debugging toolkit involving API calls and write operations (create+delete), explicit verification steps and decision points would strengthen the flow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a long monolithic file with ~150+ lines of inline code that could benefit from being split into separate referenced files (e.g., the bash script, TypeScript diagnostic, and debug client could each be separate files). The single reference to 'documenso-rate-limits' at the end is good but minimal. | 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
3a2d27d
- 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.