CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with executable scripts and a clear step sequence, but it is held back by a missing pre-share validation checkpoint for the sensitive-bundle workflow and by keeping large scripts inline with no progressive-disclosure file structure.

Suggestions

Add an explicit verification step before packaging/sharing — e.g., 'grep -r "gsk_" "$BUNDLE_DIR" and confirm no matches before tar' — to turn the implicit redaction into a real validation checkpoint.

Move the bash bundle script and TypeScript diagnostic into a scripts/ file and reference them from SKILL.md so the overview stays lean and follows progressive disclosure.

Tighten Step 2 by running the /models request once and reusing the result, instead of curling the endpoint twice.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but it could be tightened: the models endpoint is curled twice (Step 2), and full multi-step scripts are inlined rather than referenced, so not every token earns its place.

2 / 3

Actionability

It provides fully executable bash with real curl/jq commands and a complete TypeScript diagnostic that is copy-paste ready, matching the score-3 anchor rather than pseudocode.

3 / 3

Workflow Clarity

The six-step sequence is clearly ordered, but packaging and sharing a redacted bundle is a risky/batch operation with no explicit validation checkpoint (e.g., a command that verifies no secrets remain); the rubric caps such workflows at 2.

2 / 3

Progressive Disclosure

The skill is well-organized with clear sections, but it is over 50 lines with large inline scripts and no bundle files in references/scripts/assets — content that would read better split into one-level-deep reference files, fitting the score-2 anchor.

2 / 3

Total

9

/

12

Passed

Description

90%

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 strong, clearly scoping a Groq debugging niche with explicit 'Use when' guidance and natural trigger phrases. The only weakness is specificity — it describes 'collecting evidence/diagnostics' broadly rather than naming several concrete actions.

DimensionReasoningScore

Specificity

The description names the domain and a couple of actions ('Collect Groq debug evidence', 'collecting diagnostic information'), but it stays at a general level rather than enumerating multiple distinct concrete actions like the score-3 anchor ('extract, fill forms, merge').

2 / 3

Completeness

It answers both 'what' (collect Groq debug evidence for support tickets) and 'when' with an explicit 'Use when...' clause plus trigger phrases, matching the score-3 anchor.

3 / 3

Trigger Term Quality

It explicitly lists multiple natural trigger phrases a user would say ('groq debug', 'groq support bundle', 'collect groq logs', 'groq diagnostic'), giving good coverage rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

It targets a clear Groq-specific niche with distinct triggers, making it unlikely to fire for unrelated skills; not the generic overlap of the score-2 anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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