deepgram-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill deepgram-debug-bundleCollect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. Trigger with phrases like "deepgram debug", "deepgram support", "collect deepgram logs", "deepgram diagnostic", "deepgram debug bundle".
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
65%This skill provides highly actionable, executable debug collection scripts with good coverage of environment, connectivity, logging, and audio analysis. However, it lacks validation checkpoints between steps (e.g., checking if scripts exist before running the bundle collector) and could be more concise by removing the redundant high-level instructions section. The monolithic structure with extensive inline code would benefit from better progressive disclosure.
Suggestions
Add validation checkpoints to the Complete Debug Bundle Script (e.g., check if prerequisite scripts exist, verify each step succeeded before proceeding)
Remove the redundant 'Instructions' section (Steps 1-4) since the detailed implementations immediately follow and are self-explanatory
Consider splitting the individual debug scripts into referenced files rather than inline code blocks to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the high-level 'Instructions' section (Steps 1-4) is immediately followed by detailed implementations of the same steps, making the overview somewhat unnecessary. The content is mostly lean but could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash scripts, TypeScript code, and complete command examples. All code is copy-paste ready with proper shebang lines, imports, and error handling. The support ticket template is immediately usable. | 3 / 3 |
Workflow Clarity | Steps are listed and sequenced, but validation checkpoints are missing. The 'Complete Debug Bundle Script' assumes prerequisite scripts exist without verifying them. No explicit validation that each step succeeded before proceeding, and no error recovery guidance if a step fails. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic file with ~200 lines of code that could benefit from splitting into separate files (e.g., scripts in a scripts/ directory). The reference to 'deepgram-rate-limits' at the end is good, but inline code blocks are extensive. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - it describes the general purpose (collect debug evidence) but doesn't enumerate what specific artifacts or data it collects. The Deepgram-specific focus makes it highly distinctive.
Suggestions
Add specific concrete actions like 'gather API request logs', 'capture SDK version info', 'export error traces', or 'collect configuration settings' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram debug/support) and general action (collect evidence/diagnostic information), but doesn't list specific concrete actions like 'gather API logs', 'capture request traces', or 'export configuration settings'. | 2 / 3 |
Completeness | Clearly answers both what (collect debug evidence for support/troubleshooting) and when (preparing support tickets, investigating issues, collecting diagnostic information) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'deepgram debug', 'deepgram support', 'collect deepgram logs', 'deepgram diagnostic', 'deepgram debug bundle' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Deepgram' as a specific product name and clear niche around debug/diagnostic collection. Very unlikely to conflict with other skills due to the specific product focus. | 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.