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".
85
83%
Does it follow best practices?
Impact
Pending
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 'when' guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., updating import paths, replacing deprecated model IDs with specific replacements, updating configuration files). Overall it's effective for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Updates import paths, replaces deprecated model IDs (e.g., mixtral-8x7b-32768 → mixtral-saba-24b), and adjusts API call parameters' 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 very specific SDK (groq-sdk) with specific concerns (version upgrades, model deprecations, model ID migration). Unlikely to conflict with other skills. | 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, actionable skill with clear step-by-step workflows, executable code, and good validation checkpoints including rollback procedures. The main weaknesses are moderate verbosity (the file is long with inline reference tables that could be externalized) and some time-sensitive deprecation dates that will need maintenance. The error handling table and resource links are valuable additions.
Suggestions
Consider moving the deprecation timeline table and current model IDs table to a separate reference file (e.g., GROQ_MODELS.md) to keep the main skill leaner and easier to maintain as models change.
Remove the 'SDK Changelog Highlights' section — it's vague guidance that Claude can infer, and the GitHub releases link in Resources already covers this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements like the 'Overview' paragraph explaining what Groq does, and the SDK Changelog Highlights section is somewhat vague. The deprecation table with specific dates is useful but time-sensitive. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands and TypeScript code throughout. The grep patterns for scanning deprecated models, the migration map, the integration test, and the rollback command are all copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence from checking current state through validation and rollback. Includes explicit validation in Step 5 (run tests, verify models via API, integration test), a feedback loop via rollback in Step 6, and the migration scanner in Step 4 serves as a checkpoint before proceeding. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's quite long for a single file. The model deprecation tables and error handling tables could potentially be split into referenced files. The 'Next Steps' reference to groq-ci-integration is good but the main file is somewhat monolithic. | 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
70e9fa4
- 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.