groq-core-workflow-a

Execute Groq primary workflow: chat completions with tool use and JSON mode. Use when implementing chat interfaces, function calling, structured output, or building AI features with Groq's fast inference. Trigger with phrases like "groq chat completion", "groq tool use", "groq function calling", "groq JSON mode".

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 highly actionable, mostly concise code skill with executable examples for every pattern and useful reference tables. Its weaknesses are workflow_clarity (no inline validation/feedback checkpoints) and progressive_disclosure (all detail inline with no bundle-file split).

Suggestions

Add inline validation/feedback checkpoints in the multi-step tool-use flow (e.g., verify tool_calls before executing, retry with lower temperature on malformed JSON) rather than relegating recovery to a separate table.

Split the five recipe steps or the model-selection/error-handling tables into one-level-deep reference files (e.g., references/tool-use.md) so SKILL.md reads as an overview with well-signaled pointers.

Trim the overview's LPU marketing line ('delivers sub-200ms time-to-first-token...') and the vague 'Understanding of Groq model capabilities' prerequisite, which add context Claude does not need.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight executable TypeScript with minimal prose; it does not re-explain concepts Claude already knows, and every section earns its place, though the overview's LPU marketing line is mildly optional.	3 / 3
Actionability	All five steps are fully executable, import-complete, copy-paste-ready code with a concrete model-selection table and an error-handling table, matching the 'fully executable code; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1-5, with A/B/C sub-steps for tool use), but there are no inline validation checkpoints or feedback loops in the flow itself; recovery guidance lives only in a separate error-handling table.	2 / 3
Progressive Disclosure	Sections are well-organized, but the full detailed recipe content lives inline in SKILL.md with no progression to one-level-deep bundle files — only external doc URLs and a sibling-skill pointer — fitting the 'content that should be separate is inline' anchor.	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.

A strong, third-person description that states concrete capabilities, provides an explicit "Use when" clause, and lists natural trigger phrases scoped to Groq. It cleanly matches the rubric's good examples with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "chat completions with tool use and JSON mode", "function calling, structured output" — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both 'what' ("Execute Groq primary workflow: chat completions with tool use and JSON mode") and 'when' via an explicit "Use when..." clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases users would say ("groq chat completion", "groq tool use", "groq function calling", "groq JSON mode") cover the main variations of the intent.	3 / 3
Distinctiveness Conflict Risk	Groq-specific niche with distinct branded triggers ("groq ..." phrases) makes it unlikely to fire for the wrong skill.	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.