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
83%
Does it follow best practices?
Impact
—
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. Its main weakness is that the specificity of capabilities could be improved by listing more concrete actions beyond 'diagnose and fix'. The explicit trigger phrase list and clear 'Use when' clause make it highly effective for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'parse error responses, handle rate limiting (429), validate API keys, fix authentication errors, resolve timeout issues' to improve specificity.
| 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 provided. | 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 — specifically targets Groq API errors, which is unlikely to conflict with other skills. The Groq-specific trigger terms and error code references (e.g., 'groq 429') make it clearly distinguishable from general API debugging or other LLM provider skills. | 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 error reference skill with executable code examples across multiple languages and clear diagnostic workflows. Its main weakness is length — at ~150 lines of content, some sections (SDK examples, rate limit headers) could be extracted to supporting files for better progressive disclosure. The content is mostly efficient but has room for tightening.
Suggestions
Extract SDK-specific error handling examples into a separate GROQ_SDK_ERRORS.md reference file to reduce the main skill's token footprint
Trim the overview sentence and remove phrases like 'Comprehensive reference for' — jump straight into the error response format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but the rate limit headers table and some explanatory text (e.g., 'Comprehensive reference for Groq API error codes, their root causes, and proven fixes') add moderate bloat. The deprecated models table and SDK error examples are useful but could be tighter. | 2 / 3 |
Actionability | Excellent actionability throughout — provides fully executable bash commands for diagnostics, copy-paste ready TypeScript and Python error handling code, 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 is well-sequenced with explicit steps. The rate limit handler includes a retry pattern (feedback loop). Each error section follows a consistent Causes → Fix pattern that serves as an implicit workflow. | 3 / 3 |
Progressive Disclosure | The skill references external resources (Groq docs, status page) and a 'groq-debug-bundle' skill, which is good. However, the content is fairly long and monolithic — the SDK-specific error examples and rate limit headers table could reasonably be split into separate reference files. No bundle files exist to support progressive disclosure. | 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
a04d1a2
- 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.