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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured patterns skill that keeps the body as a navigable map and delegates full implementations to verified reference files. It is executable, concisely written, and cleanly layered, with only minor over-explanation and deferred-detail gaps.

Suggestions

Trim the Prerequisites bullets that restate Claude's existing knowledge ('Understanding of async/await and error handling', 'Familiarity with OpenAI SDK patterns') to push conciseness toward fully lean.

Inline one tiny verification cue (e.g. a one-line smoke-test call after the singleton) to add an explicit checkpoint to the build sequence.

For steps that currently defer entirely to references (e.g. steps 3 and 7), include a one-line executable snippet alongside the pointer so the body stands on its own for the common cases.

Dimension	Reasoning	Score
Conciseness	The body is a lean 'fast map' pointing to references with one-line step summaries and minimal inline code; minor over-explanation (e.g. 'Understanding of async/await', restating that Groq mirrors OpenAI) keeps it just below fully lean.	4 / 5
Actionability	Includes executable skeleton code (getGroq singleton), completion/streaming/Python examples, and a concrete error-handling matrix, but several steps defer to references with only one-line summaries, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly numbered 7-step layered build sequence with labeled steps; this is a patterns skill rather than a destructive/batch operation so the absence of explicit validation checkpoints is a minor gap, not a cap.	4 / 5
Progressive Disclosure	Clear overview with well-signaled, one-level-deep references to three real files (typescript-patterns.md, python-patterns.md, sdk-differences.md), each linked and described, with content appropriately split out of the main file.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, third-person description that clearly states capability, use-when guidance, and explicit trigger phrases. It is specific to the Groq niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions — 'implementing Groq integrations, refactoring SDK usage, or establishing team coding standards' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor better than the 1-2-action anchor at 3.	4 / 5
Completeness	Explicitly answers both what ('Apply production-ready Groq SDK patterns for TypeScript and Python') and when ('Use when implementing Groq integrations, refactoring SDK usage...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides four natural trigger phrases ('groq SDK patterns', 'groq best practices', 'groq code patterns', 'idiomatic groq') that users would plausibly say, giving good keyword coverage, though a few synonyms/extensions are missing so it stops short of a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Groq-specific niche with distinct triggers (groq SDK patterns, idiomatic groq) and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/saas-packs/groq-pack/skills/groq-sdk-patterns/SKILL.md
Commit: 88dcf65

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.