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
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., updating import paths, replacing model IDs, modifying API calls). Overall it's effective for skill selection in a multi-skill environment.
Suggestions
Add more specific concrete actions, e.g., 'replaces deprecated model IDs with current equivalents, updates import paths, and adjusts API call signatures' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (groq-sdk) and some actions (upgrade versions, handle deprecations), but doesn't list comprehensive concrete actions like specific migration steps, code changes, or configuration updates. | 2 / 3 |
Completeness | Clearly answers both 'what' (upgrade groq-sdk versions, handle model deprecations) and 'when' (explicit 'Use when...' clause plus a 'Trigger with phrases like...' section with concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'upgrade groq', 'groq migration', 'groq breaking changes', 'update groq SDK', 'groq deprecated model'. These are phrases users would naturally say when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific SDK (groq-sdk) with specific operations (version upgrades, model deprecation handling). Very unlikely to conflict with other skills due to the narrow, well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with a well-sequenced workflow including validation and rollback steps. Its main weakness is length — the deprecation timeline tables and model listings add bulk that will become stale over time and could be externalized. The executable code examples and scanning commands are excellent and immediately useful.
Suggestions
Consider moving the model deprecation timeline and current model ID tables into a separate referenced file (e.g., GROQ_MODELS.md) to keep the main skill focused on the upgrade workflow and reduce staleness risk.
Remove or trim the 'SDK Changelog Highlights' section — it's generic advice that Claude already knows about checking changelogs for type/API changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The model deprecation timeline with specific dates is time-sensitive information that will become stale, and the SDK changelog highlights section is somewhat generic advice Claude already knows. The dynamic shell commands at the top are a nice touch, but the overall document could be tightened. | 2 / 3 |
Actionability | Excellent actionability throughout — every step has executable bash commands or TypeScript code that is copy-paste ready. The grep patterns for scanning deprecated models, the migration map, the integration test, and the rollback command are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced from discovery through upgrade, migration, validation, and rollback. Step 5 includes explicit validation (run tests, verify models via API, integration test), and Step 6 provides a rollback path — this is a proper feedback loop for a potentially destructive upgrade operation. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a fairly long monolithic document. The model deprecation tables and current model lists could potentially be split into a referenced file to keep the main skill leaner. The reference to 'groq-ci-integration' at the end is good but there are no bundle files to support it. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
a04d1a2
- 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.