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".
88
87%
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 and clear completeness. The explicit 'Use when' and 'Trigger with' clauses make it easy for Claude to select appropriately. The main weakness is that the specific capabilities could be more detailed — listing concrete actions like handling rate limits, authentication errors, or specific error code ranges would strengthen specificity.
Suggestions
Add more specific concrete actions beyond 'diagnose and fix', such as 'resolve rate limiting (429), authentication failures (401), parse error responses, and suggest retry strategies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Groq API errors) and some actions (diagnose, fix), mentions 'real error codes and solutions', but doesn't list specific concrete actions like 'parse error responses, handle rate limits, validate API keys, retry failed requests'. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix Groq API errors with real error codes and solutions) and 'when' (encountering Groq errors, debugging failed requests, troubleshooting integration issues), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'groq error', 'fix groq', 'groq not working', 'debug groq', 'groq 429'. These are realistic phrases a user would type when encountering Groq issues. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Groq API specifically is unlikely to conflict with other skills. The trigger terms are all Groq-specific, making false positive matches with other API debugging skills unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, well-organized error reference skill with excellent actionability — every error code has concrete, executable diagnostic steps and fixes. The structure supports both quick scanning and deep reference. Minor verbosity in some areas (rate limit headers table, boilerplate SDK patterns) slightly reduces token efficiency, but overall the content earns its place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some content Claude likely knows (e.g., the rate limit header table is standard HTTP convention, and the SDK error handling patterns are fairly boilerplate). The deprecated model table and error response format are genuinely useful additions. Could be tightened by ~20%. | 2 / 3 |
Actionability | Excellent actionability throughout — provides executable bash commands for diagnostics, copy-paste ready TypeScript and Python code for error handling, specific curl commands for testing, and concrete model replacement mappings. Every error code has a concrete fix. | 3 / 3 |
Workflow Clarity | The Quick Diagnostic section provides a clear 3-step sequence for triaging issues. The escalation path at the end provides a clear sequence for unresolved issues. Each error section follows a consistent pattern (error message → causes → fix) making it easy to follow. The rate limit handler includes a retry pattern. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections for quick diagnosis vs. detailed error reference. Links to external resources (Groq docs, status page) are clearly signaled. References to the `groq-debug-bundle` skill for deeper debugging is a clean one-level-deep reference. Content is appropriately organized for scanning. | 3 / 3 |
Total | 11 / 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
c8a915c
- 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.