CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-common-errors

Diagnose and fix Groq API errors with real error codes and solutions. Use when encountering Groq errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "groq error", "fix groq", "groq not working", "debug groq", "groq 429".

68

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

80%

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

A dense, actionable reference with executable code for every error class and tight, token-efficient prose. Its weak spots are the diagnostic workflow's implicit validation checkpoints and the absence of any file-split progressive disclosure structure.

Suggestions

Add explicit validation checkpoints to the Quick Diagnostic (e.g., 'If the models list is empty, check API key permissions before continuing') to give the workflow a clear feedback loop.

Consider moving the per-language SDK error-handling examples into a bundled reference file (e.g., scripts/ or references/) and linking to it from the body, so the core SKILL.md stays a lean overview.

Cross-link each error-code section to its corresponding Quick Diagnostic step so users follow a clear diagnose-then-fix sequence.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable code blocks and tables; it avoids explaining concepts Claude already knows and nearly every line earns its place.

3 / 3

Actionability

Provides copy-paste-ready curl diagnostics, a TypeScript retry handler, Python exception handling, and bash key checks, all concrete and executable.

3 / 3

Workflow Clarity

The Quick Diagnostic and Escalation Path are numbered sequences, but the diagnostic lacks explicit validation feedback loops; checkpoints like "Should return 200" are implicit within fix sections rather than the main workflow.

2 / 3

Progressive Disclosure

The body is well-organized with clear section headers (avoiding a monolithic wall), but no bundle files exist and all error reference and SDK content is inline in a single ~150-line file rather than split into one-level-deep references.

2 / 3

Total

10

/

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.

A well-constructed description that uses third-person voice, answers both what and when, and supplies natural trigger phrases with a specific error code. The only weakness is modest action specificity, relying on the generic verbs 'diagnose' and 'fix'.

DimensionReasoningScore

Specificity

Names the domain and two actions ("Diagnose and fix Groq API errors with real error codes and solutions"), but the verbs are generic and it does not list multiple distinct concrete actions like the score-3 anchor.

2 / 3

Completeness

Explicitly answers what ("Diagnose and fix Groq API errors...") and when ("Use when encountering Groq errors, debugging failed requests, or troubleshooting integration issues") with explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides natural phrases users would actually say ("groq error", "fix groq", "groq not working", "debug groq", "groq 429"), including a real status code, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Groq-specific niche and code-bearing triggers ("groq 429", "fix groq") make it clearly distinguishable and unlikely to fire for unrelated skills.

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.