CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-migration-deep-dive

Migrate from OpenAI/Anthropic/other LLM providers to Groq, or migrate between Groq model generations with zero-downtime traffic shifting. Trigger with phrases like "migrate to groq", "switch to groq", "groq migration", "openai to groq", "groq replatform".

67

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

65%

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

The body is highly actionable with executable code and a clear step sequence, but it is monolithic and long with no progressive disclosure to reference files, and its validation checkpoints for risky traffic shifting are implicit rather than explicit.

Suggestions

Add explicit validation gates to the traffic-shifting workflow (e.g., 'at each percentage, check error rate and latency; only increase if within baseline') rather than relying on a comment-based schedule and a separate rollback block.

Move the provider abstraction classes, benchmark function, and scanner script into separate reference files (e.g., references/provider-abstraction.md, scripts/migration-scanner.sh) and link to them from SKILL.md so the main file stays a lean overview.

De-duplicate the near-identical GroqProvider and OpenAIProvider implementations — show one in full and note the other mirrors it, or factor the shared logic into a base class.

DimensionReasoningScore

Conciseness

It is code-forward and avoids explaining concepts Claude already knows, but the near-identical GroqProvider and OpenAIProvider classes plus the elaborate benchmark function could be tightened, and the skill runs long.

2 / 3

Actionability

Provides fully executable TypeScript (complete imports, calls, model IDs) and a runnable bash scanner script that are copy-paste ready with specific details.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced with a rollback plan and error-handling table, but for a risky production traffic shift the validation checkpoints are implicit (comment-based schedule and rollback) rather than explicit validate-before-proceed gates.

2 / 3

Progressive Disclosure

Sections are well organized, but no bundle files exist and ~277 lines of content — provider abstraction, benchmark, and scanner script — all live inline in SKILL.md rather than being split into one-level-deep reference files.

2 / 3

Total

9

/

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 strong: it states concrete capabilities, supplies explicit natural-language triggers, answers both what and when, and occupies a clear Groq-migration niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Migrate from OpenAI/Anthropic/other LLM providers to Groq', 'migrate between Groq model generations', and 'zero-downtime traffic shifting' — rather than vague language.

3 / 3

Completeness

Explicitly answers what it does (provider/generation migration with traffic shifting) and when to use it via an explicit 'Trigger with phrases like...' clause, satisfying both halves.

3 / 3

Trigger Term Quality

Provides five natural phrases a user would actually say: 'migrate to groq', 'switch to groq', 'groq migration', 'openai to groq', and 'groq replatform', giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly Groq-specific migration with distinct Groq-oriented trigger phrases, making it unlikely to fire for unrelated 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.