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".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable overview that pushes detail into two one-level-deep reference files and includes thorough error-handling guidance. Weaknesses are minor: slight prose/table redundancy and the main shell script being only a partial skeleton inline.

Suggestions

Trim redundant prose: the Current State probe block and sentences that restate Output-table contents could be cut for token efficiency.

Inline the full six-step script (or at least Steps 2-5) so the bundle can be assembled without first opening references/implementation.md, raising actionability from 4 to 5.

Add an explicit 'verify the archive and confirm no gsk_ keys remain' checkpoint in the Package/Error-Handling step to make the validation gate concrete.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no concept-explainer filler, but has minor over-explanation: the Current State probe block and some prose restates what the Output table already shows.	4 / 5
Actionability	Concrete endpoints, header names, masking rules, and a runnable TypeScript snippet; however the main six-step shell script is only a partial skeleton inline ('# ... append ...') with the full script deferred to a reference, leaving a minor execution gap.	4 / 5
Workflow Clarity	A clearly sequenced six-step list plus an Error Handling section that enumerates failure modes and remediation steps; validation is present via the redaction checklist and printed review reminder, though an explicit 'verify tarball / verify redaction' checkpoint before sharing is implicit rather than stated.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with the full script and examples split into two well-signaled, one-level-deep reference files (references/implementation.md, references/examples.md), both verified to exist and free of nested-reference chains.	5 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, complete, and distinct, explicitly pairing a 'what' statement with a 'Use when' clause and four natural trigger phrases. Its main weakness is specificity: the listed actions are generic ('collect evidence') rather than enumerated concrete operations.

Dimension	Reasoning	Score
Specificity	Names the Groq-debug domain and 1-2 concrete actions ('Collect Groq debug evidence', 'preparing support tickets', 'collecting diagnostic information'), but the actions are generic rather than a comprehensive list of specific operations.	3 / 5
Completeness	Clearly answers both 'what' (Collect Groq debug evidence for support tickets) and 'when' (Use when encountering persistent issues, preparing support tickets) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicitly lists natural trigger phrases a user would say ('groq debug', 'groq support bundle', 'collect groq logs', 'groq diagnostic'); coverage is good though all share the 'groq' prefix and a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	'Groq debug evidence' with Groq-prefixed trigger phrases carves a clear niche unlikely to fire for unrelated skills, with minimal overlap risk.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/groq-pack/skills/groq-debug-bundle/SKILL.md
Commit: 9ba805c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.