groq-debug-bundle
Collect Groq debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Groq problems. Trigger with phrases like "groq debug", "groq support bundle", "collect groq logs", "groq diagnostic".
85
83%
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, clear 'when' guidance, and a distinct niche. Its main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., collecting logs, system info, configuration files) rather than the general 'collect debug evidence'.
Suggestions
Add specific concrete actions describing what evidence is collected, e.g., 'Collects system logs, configuration files, error traces, and hardware status for Groq debug evidence.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Groq debug evidence) and a general action (collect debug evidence for support tickets and troubleshooting), but doesn't list multiple specific concrete actions like what types of evidence are collected (logs, configs, metrics, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Groq debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'groq debug', 'groq support bundle', 'collect groq logs', 'groq diagnostic', plus contextual phrases like 'support tickets', 'troubleshooting', and 'diagnostic information'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Groq-specific debug evidence collection is unlikely to conflict with other skills. The trigger terms are highly specific to this particular use case. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, highly actionable skill with executable code throughout and a clear sequential workflow. Its main weakness is length — the full bash script across 6 steps plus a TypeScript alternative makes it token-heavy for a skill file, though most of that content earns its place. The redaction guidance and bundle contents table are valuable additions that demonstrate security awareness.
Suggestions
Consider extracting the full bash debug bundle script into a separate referenced file (e.g., `groq-debug-bundle.sh`) and keeping only a summary and invocation command in SKILL.md to improve conciseness and progressive disclosure.
The TypeScript diagnostic could similarly be referenced as a separate file rather than inline, reducing the SKILL.md to an overview with clear pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The 'Current State' section with shell commands at the top is a nice touch, but the overall content is lengthy for what is essentially a script generation task. The TypeScript alternative adds value but also adds bulk. The table and redaction checklist are useful but could be tighter. | 2 / 3 |
Actionability | Excellent actionability — every step contains fully executable bash commands and a complete TypeScript diagnostic script. The curl commands are copy-paste ready with proper headers, the sed redaction patterns are specific, and the bundle packaging is complete. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow for creating the debug bundle, with each step building on the previous one (creating directory → collecting data → packaging). The redaction steps serve as validation checkpoints, and the 'Review before sharing' warning at the end is an explicit verification step before the destructive action of sharing potentially sensitive data. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a summary table, but it's quite long for a single SKILL.md file. The bash script steps could potentially be a referenced script file rather than inline. The reference to 'groq-rate-limits' at the end is good progressive disclosure, but the bulk of the content is monolithic within this file. | 2 / 3 |
Total | 10 / 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
70e9fa4
- 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.