CtrlK
BlogDocsLog inGet started
Tessl Logo

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

67

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.

A highly actionable catalog of executable Groq SDK patterns with clear sequencing and useful comparison tables. Its main weaknesses are modest redundancy of concepts Claude already knows and the absence of validation checkpoints and progressive file splitting for the larger reference material.

Suggestions

Trim restated-known-concept prose (e.g. OpenAI-compatibility explanations and obvious inline comments) to lift conciseness toward 3.

Add explicit validation/retry feedback loops to the error-handling and retry steps — e.g. verify the retry-after value and confirm success before proceeding — so workflow clarity reaches 3.

Move the comparison tables and per-step reference detail into reference bundle files (e.g. references/sdk-differences.md) and link to them from the body so progressive disclosure reaches 3.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code blocks and comparison tables, but it includes explanation Claude likely already knows (e.g. 'The Groq SDK mirrors the OpenAI SDK interface', 'Groq is API-compatible', 'Reads GROQ_API_KEY from env') and inline comments restating obvious behavior, so it could be tightened.

2 / 3

Actionability

Provides complete, executable TypeScript and Python code for singleton clients, completions, streaming, error handling, retry-with-backoff, and multi-tenant factories — copy-paste ready with concrete model names and headers.

3 / 3

Workflow Clarity

Seven numbered steps give a clear progression, but the retry/error-handling steps lack explicit validation checkpoints or feedback loops (validate -> fix -> retry), and the destructive/batch-relevant multi-tenant factory has no verification guidance, capping clarity at 2.

2 / 3

Progressive Disclosure

Well-organized with clear sections and a one-level external Resources list, but all detail lives inline in a single ~250-line file with no bundle files to split advanced reference material into, so content that should be separate stays monolithic.

2 / 3

Total

9

/

12

Passed

Description

100%

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 strong description that concisely states concrete capabilities for both TypeScript and Python, gives an explicit Use-when clause, and supplies natural trigger phrases. It is specific, complete, and clearly distinct from generic SDK skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Apply production-ready Groq SDK patterns for TypeScript and Python', 'implementing Groq integrations', 'refactoring SDK usage', 'establishing team coding standards' — naming both language targets and specific engineering activities rather than vague phrasing.

3 / 3

Completeness

Explicitly answers both what (apply production-ready Groq SDK patterns for TS/Python) and when (explicit 'Use when...' clause plus a 'Trigger with phrases like...' list), satisfying both halves of the dimension.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say — 'groq SDK patterns', 'groq best practices', 'groq code patterns', 'idiomatic groq' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Groq-specific niche, named SDK, and Groq-branded trigger terms make it clearly distinguishable from generic coding or OpenAI skills and unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

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.