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 development environment, configuring 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".

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is a tight, actionable dev-setup guide with complete executable code and clean sectioning. Its only gap is workflow clarity: the steps are well-ordered but lack explicit validation checkpoints or feedback loops spelling out how to verify and recover.

Suggestions

Add an explicit validation checkpoint after setup, e.g. 'Run `npm test` to verify the mock suite passes before touching live API tests', with a fix-retry loop referencing the Error Handling table.

Make the integration-test gating an explicit step rather than only implicit via describe.skipIf - state 'Run `npm run test:integration` only in CI with GROQ_INTEGRATION=1' as a numbered checkpoint.

Resolve the dangling 'groq-sdk-patterns' reference at the end - either link a real bundle file or remove it to avoid pointing at a non-existent resource.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable code with tight headers and minimal prose; it avoids explaining concepts Claude already knows and nearly every token earns its place.

3 / 3

Actionability

Provides fully executable TypeScript for the client, model constants, unit and integration tests, plus package.json scripts and a .env template - all copy-paste ready.

3 / 3

Workflow Clarity

The seven steps are clearly sequenced, but there are no explicit validation checkpoints or fix-then-retry feedback loops in the workflow itself; verification is only implicit via the testing steps.

2 / 3

Progressive Disclosure

No bundle files exist; the single self-contained file is well-organized into clearly signaled sections with no nested references, satisfying the simple-skill organization bar.

3 / 3

Total

11

/

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 distinct: it names three concrete capabilities, gives explicit use-when guidance, and lists natural Groq-prefixed trigger phrases. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'hot reload, mocking, and testing' - matching the anchor for several specific capabilities rather than vague language.

3 / 3

Completeness

Explicitly states what it does ('Configure Groq local development...') and when to use it ('Use when setting up a development environment...') with explicit trigger phrases, answering both what and when.

3 / 3

Trigger Term Quality

Provides four natural trigger phrases ('groq dev setup', 'groq local development', 'groq dev environment', 'develop with groq') that a user would plausibly say, giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Groq-specific scope with Groq-prefixed triggers carves a clear niche unlikely to conflict with non-Groq development skills.

3 / 3

Total

12

/

12

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.