groq-sdk-patterns
Apply production-ready Groq SDK patterns for TypeScript and Python. Use when implementing Groq integrations, refactoring SDK usage, or establishing team coding standards for Groq. Trigger with phrases like "groq SDK patterns", "groq best practices", "groq code patterns", "idiomatic groq".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/groq-pack/skills/groq-sdk-patterns/SKILL.mdQuality
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 'what/when' guidance. Its main weakness is that the specific capabilities could be more concrete—listing actual SDK patterns or operations rather than high-level activities like 'implementing integrations' and 'refactoring SDK usage'. Overall it performs well for skill selection purposes due to its distinct niche and explicit triggers.
Suggestions
Add more concrete actions to improve specificity, e.g., 'configure streaming responses, implement error handling, set up authentication, manage rate limits' rather than generic phrases like 'implementing Groq integrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Groq SDK patterns for TypeScript and Python) and mentions some actions (implementing integrations, refactoring SDK usage, establishing coding standards), but the actions are somewhat generic and don't list concrete specific capabilities like 'configure streaming responses, handle rate limits, set up error retries'. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Groq SDK patterns for TypeScript and Python) and 'when' (implementing Groq integrations, refactoring SDK usage, establishing team coding standards) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases ('groq SDK patterns', 'groq best practices', 'groq code patterns', 'idiomatic groq') and includes relevant keywords like 'Groq integrations', 'TypeScript', 'Python', and 'team coding standards'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on Groq SDK specifically, combined with the language-specific mention (TypeScript and Python) and the explicit trigger terms, makes this highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable reference for Groq SDK patterns with excellent executable code examples covering key use cases (singleton, streaming, error handling, retry, Python). Its main weaknesses are the monolithic structure that could benefit from splitting into focused files, the misleading sequential 'Step' framing for independent patterns, and some unnecessary explanatory content that Claude doesn't need. The lack of validation checkpoints between steps and no bundle files to support progressive disclosure limit its score.
Suggestions
Remove the sequential 'Step N' framing and use descriptive section headers instead (e.g., '## Client Singleton', '## Streaming'), since these are independent patterns not a workflow.
Split Python patterns into a separate file (e.g., PYTHON.md) and reference it from the main SKILL.md to improve progressive disclosure and reduce monolithic content.
Add a quick validation step such as a health-check snippet (e.g., a minimal API call to verify the key works) that users should run before adopting the more complex patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements: the Prerequisites section explains things Claude already knows (async/await, error handling), the Overview explains what OpenAI SDK compatibility means, and the comparison table restates information already demonstrated in the code. The 'Steps' framing adds slight overhead for what are really independent patterns. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript and Python with proper imports, type annotations, and realistic patterns. The error handling, retry logic, streaming, and client singleton patterns are concrete and complete with specific Groq SDK types and methods. | 3 / 3 |
Workflow Clarity | The numbered 'Steps' suggest a sequential workflow but these are really independent patterns that can be adopted in any order. There are no validation checkpoints—for instance, no step to verify the API key works, no guidance on testing the client singleton, and no feedback loop for when patterns fail in integration. The step numbering implies a sequence that doesn't truly exist. | 2 / 3 |
Progressive Disclosure | The content is a monolithic file with ~180 lines of inline code that could benefit from splitting (e.g., Python patterns in a separate file, error handling patterns in another). References to external resources and 'groq-core-workflow-a' exist but no bundle files support them. The comparison tables and resource links provide some structure but the main body is dense. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.