CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-upgrade-migration

Upgrade groq-sdk versions and handle Groq model deprecations. Use when upgrading SDK versions, detecting deprecated models, or migrating to new Groq model IDs. Trigger with phrases like "upgrade groq", "groq migration", "groq breaking changes", "update groq SDK", "groq deprecated model".

68

Quality

83%

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 migration skill: a lean overview with actionable commands, validation and rollback checkpoints, and clean one-level-deep reference files. The main gap is an explicit validate-and-retry loop in the body and some inline content that mirrors the reference.

Suggestions

Add an explicit 'if npm test or the /v1/models check fails, fix the flagged call sites and re-run Step 5' loop so the validate→fix→retry path is stated, not implied.

Trim the inline resolver skeleton or mark it clearly as a teaser for the full map in implementation.md to avoid duplicating content across files.

Surface the rollback trigger condition explicitly (e.g. 'roll back when tests fail after the bump') in the Step 6 heading rather than only 'Roll back if needed'.

DimensionReasoningScore

Conciseness

The body is lean — deprecation/model tables, a skeleton, and six-step instructions with no preamble explaining what Groq or an SDK is — with only minor trim opportunities such as the inline resolver skeleton duplicating the reference.

4 / 5

Actionability

Inline commands (git checkout -b, npm install groq-sdk@latest, grep sweep, curl /v1/models) and an executable TypeScript resolver skeleton are concrete; the full copy-paste command blocks are deferred to implementation.md, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

Six clearly sequenced steps include validation (npm test plus live /v1/models check) and a rollback path, so the destructive-operation cap does not apply; a validate→fix→re-run retry loop is only implicit rather than spelled out.

4 / 5

Progressive Disclosure

SKILL.md is an overview that signals one-level-deep references to the real references/implementation.md and references/examples.md files via inline links and a Resources section, with content appropriately split between the three files.

5 / 5

Total

17

/

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.

A well-constructed description: it states concrete capabilities, gives explicit 'Use when' guidance, and lists natural trigger phrases scoped tightly to Groq migrations. Minor room to expand trigger synonym coverage and make every action as concrete as the strongest ones.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Upgrade groq-sdk versions', 'detecting deprecated models', 'migrating to new Groq model IDs'), though 'handle Groq model deprecations' is slightly more abstract than the fully concrete actions.

4 / 5

Completeness

Explicitly answers both what ('Upgrade groq-sdk versions and handle Groq model deprecations') and when, with a 'Use when…' clause plus concrete trigger phrases — matching the top anchor.

5 / 5

Trigger Term Quality

Five natural trigger phrases ('upgrade groq', 'groq migration', 'groq breaking changes', 'update groq SDK', 'groq deprecated model') give good synonym coverage a user would actually say, with a few plausible variations (e.g. 'groq models', 'switch groq model') absent.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Groq SDK upgrades and model-ID migration with distinct, brand-specific triggers, so overlap with other skills is minimal.

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.