clerk-upgrade-migration
Manage Clerk SDK version upgrades and handle breaking changes. Use when upgrading Clerk packages, migrating to new SDK versions, or handling deprecation warnings. Trigger with phrases like "upgrade clerk", "clerk migration", "update clerk SDK", "clerk breaking changes".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 during a Clerk SDK upgrade. The explicit trigger phrases and narrow domain focus make it highly effective for skill selection.
Suggestions
Add more specific concrete actions like 'update import paths, replace deprecated API calls, migrate authentication middleware, update Clerk component usage' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk SDK) and some actions (version upgrades, breaking changes, deprecation warnings), but doesn't list specific concrete actions like 'update import paths', 'replace deprecated API calls', or 'modify authentication hooks'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Clerk SDK version upgrades and handle breaking changes) and 'when' (upgrading Clerk packages, migrating to new SDK versions, handling deprecation warnings), with an explicit 'Trigger with phrases like...' clause. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'upgrade clerk', 'clerk migration', 'update clerk SDK', 'clerk breaking changes', plus contextual terms like 'deprecation warnings' and 'migrating to new SDK versions' that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clerk SDK upgrades and migrations, which is a clear niche unlikely to conflict with other skills. The combination of 'Clerk' + 'upgrade/migration' creates distinct triggers. | 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 excellent workflow clarity and concrete, executable examples for Clerk SDK migration. Its main weakness is length — the document packs a lot of inline content that could benefit from progressive disclosure via separate reference files. The conciseness could be improved by trimming redundant commentary and the Prerequisites/Output sections.
Suggestions
Move the detailed v5→v6 migration patterns and the automated migration script into a separate file (e.g., CLERK_V5_TO_V6.md) and reference it from the main skill
Remove the Prerequisites and Output sections — Claude already knows to check for clean git state and the output section just restates what the steps accomplish
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete code examples, but includes some unnecessary elements like the Prerequisites section (Claude knows to check for clean git state), commented-out BEFORE/AFTER patterns that are somewhat verbose, and the Output section which restates what the steps already cover. The migration script at the end adds value but the overall document could be tightened. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes executable bash commands or TypeScript code. The grep commands for finding affected files, the sed-based migration script, and the specific version migration patterns (v5→v6) are all copy-paste ready and immediately useful. | 3 / 3 |
Workflow Clarity | Clear 7-step sequential workflow with explicit validation checkpoints: Step 6 includes build verification, test execution, and manual testing checklist for critical flows. Step 7 provides a concrete rollback plan. The workflow has a proper feedback loop — if the build fails, you can rollback and retry. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's a fairly long monolithic document. The error handling table, migration script, and detailed v5→v6 patterns could be split into referenced files. The Resources section at the end provides external links but no internal file references for advanced content. | 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
3e83543
- 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.