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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A strong, highly actionable reference architecture with executable code and clean organization. Its main weaknesses are the lack of explicit validation checkpoints in the workflow and a monolithic structure that keeps content inline rather than splitting into bundle files.

Suggestions

Add an explicit validation/retry checkpoint for batch and fallback operations (e.g., verify the routed model satisfies the request's constraints before invoking, and validate streaming output before yielding 'done').

Move the full code implementations (models.ts, router.ts, middleware.ts, fallback.ts, streaming.ts) into a references/ bundle and keep SKILL.md as an overview with clearly signaled one-level-deep links.

Tighten the inline TypeScript where possible (e.g., the duplicated cache-key hashing in middleware.ts) to further improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dense and efficient — diagram, file tree, executable TypeScript, and tables — with no padding explaining concepts Claude already knows; each section earns its place as concrete reference implementation.	3 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript for the registry, router, middleware, fallback, and streaming layers, plus concrete model IDs and a feature-mapped integration table.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced and the fallback chain includes error recovery, but there are no explicit validation checkpoints for the batch/destructive-style operations, capping clarity at the 'validation gaps' anchor.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is monolithic — all five full code implementations, tables, and the diagram live inline in a ~320-line SKILL.md with no one-level-deep bundle references, matching 'content that should be separate is inline'.	2 / 3
	Total	10 / 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.

The description is specific, complete, and well-triggered with a clear Groq niche. It uses third-person voice and avoids fluff, satisfying the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'model routing, streaming pipelines, and fallbacks', 'designing new Groq integrations', 'reviewing project structure', 'establishing architecture standards' — rather than vague language.	3 / 3
Completeness	Explicitly answers what ('Implement Groq reference architecture with model routing, streaming pipelines, and fallbacks') and when ('Use when designing... reviewing... or establishing...', plus trigger phrases), satisfying the anchor for explicit triggers.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say — 'groq architecture', 'groq best practices', 'groq project structure', 'how to organize groq', 'groq design' — with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to the Groq niche with Groq-prefixed triggers, making it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: 3022dd3

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