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".

72

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

92%

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

A highly actionable, well-sequenced migration guide with concrete code, validation checkpoints, and rollback handling. Its main shortcoming is progressive disclosure: substantial reference-grade detail (model tables, migration maps) is kept inline in a single file rather than offloaded to bundled reference files.

Suggestions

Move the deprecated/current model tables and the MODEL_MIGRATIONS map into a references/ file (e.g. references/models.md) and link to it from the body, keeping SKILL.md as an overview plus the workflow.

Extract the Step 4 scanner scripts into a scripts/ file so the body references an executable tool rather than embedding the full grep pipeline inline.

Add an explicit 'if validation fails, fix and re-run' loop in Step 5 alongside the existing rollback step to make the feedback loop fully self-contained.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable code blocks and tables with minimal concept-explanation padding; time-sensitive model data is correctly placed in deprecated/current sections rather than scattered inline.

3 / 3

Actionability

Provides fully executable guidance throughout — npm/git commands, a real MODEL_MIGRATIONS record with a resolveModel function, grep-based scanners, curl model verification, a node integration test, and an exact-version rollback pin.

3 / 3

Workflow Clarity

Six numbered steps are clearly sequenced with explicit validation in Step 5 (npm test, curl model list, integration test) and an explicit rollback/recovery step (Step 6) for a batch upgrade operation.

3 / 3

Progressive Disclosure

Sections are well-organized but the file is monolithic: the full migration map, large model tables, and scanner scripts are inline detail that could be split into reference files; no bundle files are provided and the only external pointer is to another skill.

2 / 3

Total

11

/

12

Passed

Description

90%

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 with explicit what/when guidance and a strong set of natural trigger phrases. Its only weakness is specificity, where the capability summary stays at two actions rather than enumerating the concrete migration activities the skill actually performs.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Upgrade groq-sdk versions and handle Groq model deprecations') but does not enumerate multiple specific actions comprehensively; the richer migration specifics live in the body, not the description.

2 / 3

Completeness

Explicitly answers both what ('Upgrade groq-sdk versions and handle Groq model deprecations') and when ('Use when upgrading SDK versions, detecting deprecated models, or migrating to new Groq model IDs').

3 / 3

Trigger Term Quality

Five natural trigger phrases are listed ('upgrade groq', 'groq migration', 'groq breaking changes', 'update groq SDK', 'groq deprecated model'), giving good coverage of terms a user would naturally say.

3 / 3

Distinctiveness Conflict Risk

The Groq-specific niche and distinct Groq-scoped triggers make it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.