CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-local-dev-loop

Configure Groq local development with hot reload, mocking, and testing. Use when setting up a Groq development environment, configuring mocked vs live test workflows, or establishing a fast iteration cycle with Groq. Trigger with phrases like "groq dev setup", "groq local development", "groq dev environment", "develop with groq".

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is well-structured with executable code, a clear seven-step workflow, and excellent progressive disclosure to real reference files. The main improvement is adding an explicit validation/verification checkpoint in the steps.

Suggestions

Add an explicit verification step (e.g., "Run `npm run test:watch` to confirm the scaffold works") as step 8 so the workflow has a clear validation checkpoint.

Trim the Dev Tips section of guidance Claude already infers (e.g., temperature: 0 for determinism) to improve token efficiency.

Show a minimal snippet of models.ts (the MODELS map) inline since it is central to the dev-loop quota-conservation story, rather than only describing it in a step.

DimensionReasoningScore

Conciseness

The body is mostly efficient with an inline skeleton and pointers to reference files, but includes minor over-explanation (e.g. "Set temperature: 0 for deterministic outputs") that could be trimmed; matches anchor 4.

4 / 5

Actionability

Provides copy-paste-ready client.ts code, concrete npm scripts, specific model IDs, env vars, and executable bash commands covering the common cases; matches anchor 5.

5 / 5

Workflow Clarity

Seven steps are clearly sequenced in order and the Examples section doubles as verification, but there is no explicit validation checkpoint within the steps themselves; matches anchor 4.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview with well-signaled, one-level-deep references to real files (implementation.md, examples.md) that hold the full code; content is appropriately split and easy to navigate, matching anchor 5.

5 / 5

Total

18

/

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 clearly and completely answers both what the skill does and when to use it, with concrete actions and natural trigger phrases. Minor gains are possible by adding a few more trigger synonyms.

DimensionReasoningScore

Specificity

"Configure Groq local development with hot reload, mocking, and testing" names several concrete actions (hot reload, mocking, testing), matching anchor 4; not 5 because only three capabilities are listed rather than comprehensive coverage.

4 / 5

Completeness

It explicitly states the "what" (configure Groq local dev with hot reload, mocking, testing) and the "when" ("Use when setting up...") plus concrete trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases ("groq dev setup", "groq local development", "groq dev environment", "develop with groq") give good keyword coverage with synonyms; not 5 because a few natural variations are missing and there are no file-extension-style triggers.

4 / 5

Distinctiveness Conflict Risk

Groq-specific local-development niche with distinct groq-prefixed triggers means minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

18

/

20

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.