groq-reference-architecture

Implement Groq reference architecture with model routing, streaming pipelines, and fallbacks. Use when designing new Groq integrations, reviewing project structure, or establishing architecture standards for Groq applications. Trigger with phrases like "groq architecture", "groq best practices", "groq project structure", "how to organize groq", "groq design".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The body is a well-organized architectural skill: concise tables and ordered build steps with explicit dependencies, and excellent progressive disclosure that offloads full source and examples to verified reference files. The main gaps are minor redundancy between the Instructions and Output sections and the absence of an explicit build/test verification checkpoint.

Suggestions

Add a final verification step (e.g. 'run the test suite / typecheck') to the five-step Instructions so the workflow has an explicit success checkpoint.

Trim the 'Output' section to avoid restating behavior already described in 'Instructions', or merge runtime outcomes into the Integration Patterns context.

Inline a complete ModelSpec type and one full MODELS entry so the registry skeleton is copy-paste ready without opening implementation.md.

Dimension	Reasoning	Score
Conciseness	Largely lean — tables, terse bullets, and domain-specific guidance assume Claude's competence; held below 5 because the 'Output' section restates outcomes already implied by 'Instructions' and the Overview prose could be tightened slightly.	4 / 5
Actionability	Concrete file names, function signatures, and an executable Model Registry skeleton plus runnable example snippets give mostly executable guidance; the inline registry skeleton uses placeholder comments rather than a full ModelSpec, and full source is deliberately offloaded to references, so it is not fully copy-paste ready inline.	4 / 5
Workflow Clarity	Five numbered build steps with explicit dependency ordering ('router depends on the registry; middleware and fallback depend on the client') form a clear sequence; missing an explicit verify/test checkpoint keeps it just below 5, though the destructive/batch cap does not apply to this code-generation skill.	4 / 5
Progressive Disclosure	The body is an overview that points to three real, one-level-deep bundle files (architecture.md, implementation.md, examples.md) via clearly signaled markdown links, with content appropriately split — a strong match for the top anchor.	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.

The description is well-constructed: it states concrete capabilities, gives an explicit 'Use when' clause with multiple natural trigger phrases, and occupies a distinct Groq-specific niche. Voice is appropriately imperative/infinitive (matching accepted good examples), with no first- or second-person phrasing.

Dimension	Reasoning	Score
Specificity	Names the Groq domain plus three concrete architectural concerns ('model routing, streaming pipelines, and fallbacks'), matching the 'several specific actions; minor gaps' anchor; not a 5 because coverage is architectural rather than an exhaustive list of discrete actions.	4 / 5
Completeness	Explicitly answers both what ('Implement Groq reference architecture with model routing, streaming pipelines, and fallbacks') and when ('Use when designing new Groq integrations, reviewing project structure, or establishing architecture standards'), plus concrete trigger phrases — a textbook match for the top anchor.	5 / 5
Trigger Term Quality	Provides five natural user phrases ('groq architecture', 'groq best practices', 'groq project structure', 'how to organize groq', 'groq design'); good coverage but a few natural synonyms (e.g. 'groq integration', 'groq setup') are missing, placing it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Groq-specific niche with distinct, vendor-qualified triggers ('groq architecture', 'groq project structure'), giving minimal overlap risk with unrelated skills.	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/claude-code-plugins-plus-skills
Path: plugins/saas-packs/groq-pack/skills/groq-reference-architecture/SKILL.md
Commit: 8585d6d

Reviewed: 7 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.