CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-migration-deep-dive

Use when you are moving a codebase off OpenAI, Anthropic, or another LLM provider onto Groq (or between Groq model generations) and want a zero-downtime, feature-flagged cutover with a benchmark and rollback plan. Trigger with phrases like "migrate to groq", "switch to groq", "groq migration", "openai to groq", "groq replatform".

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

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.

A well-structured, actionable migration skill that leans on progressive disclosure to keep the body scannable while preserving concrete inline examples. Slight gains available by trimming marketing prose and surfacing validation criteria inline.

Suggestions

Drop or relocate the '10-50x faster inference' marketing claim to tighten conciseness.

Inline at least the benchmark pass/fail threshold and the rollback trigger condition so the validation checkpoint is explicit rather than deferred to references.

DimensionReasoningScore

Conciseness

Mostly efficient — tables and code earn their place — but includes minor trimmable padding such as 'The reward is 10-50x faster inference' and an explanatory overview paragraph; not enough to drop to 3, clearly above the midpoint.

4 / 5

Actionability

Provides copy-paste-ready BEFORE/AFTER TypeScript and a concrete MODEL_MAP with prerequisites and commands, but the executable guidance for Steps 3-7 is deferred to reference files rather than inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clear Steps 1-7 sequence with an explicit canary → benchmark → ramp → rollback checkpoint flow and an error-handling table; validation is present (benchmark, rollback) so the destructive/batch cap does not apply, though detailed validation criteria live in the references.

4 / 5

Progressive Disclosure

SKILL.md is a scannable overview that moves Steps 3-7 verbatim into one-level-deep, clearly signaled references (references/implementation.md and references/examples.md, both verified to exist), with explicit links and a stated rationale for keeping the file lean.

5 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, specific description with explicit what/when structure and a comprehensive set of natural trigger phrases. The only weakness is second-person voice ('you are moving'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person (e.g., 'Migrates a codebase off OpenAI, Anthropic, or another LLM provider onto Groq...') to avoid the second-person voice penalty and lift the specificity score.

DimensionReasoningScore

Specificity

Names multiple concrete actions/outcomes — 'moving a codebase off OpenAI, Anthropic, or another LLM provider onto Groq', 'zero-downtime, feature-flagged cutover with a benchmark and rollback plan' — which would anchor at 5, but reduced by 1 per the rubric guideline because the voice is second person ('Use when you are moving...').

4 / 5

Completeness

Clearly answers both 'what' (migrate a codebase onto Groq with a zero-downtime, feature-flagged cutover, benchmark, and rollback plan) and 'when' (an explicit 'Use when...' clause plus concrete trigger phrases).

5 / 5

Trigger Term Quality

Explicitly lists natural trigger phrases a user would say — 'migrate to groq', 'switch to groq', 'groq migration', 'openai to groq', 'groq replatform' — giving comprehensive coverage of natural terms including synonyms.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche — LLM-provider-to-Groq migration — with distinct, provider-specific triggers ('openai to groq', 'groq replatform') that make overlap with unrelated skills unlikely.

5 / 5

Total

19

/

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.