customerio-upgrade-migration
Plan and execute Customer.io SDK upgrades and migrations. Use when upgrading customerio-node versions, migrating from legacy APIs, or updating to new SDK patterns. Trigger: "upgrade customer.io", "customer.io migration", "update customer.io sdk", "customer.io 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 completeness and distinctiveness. It clearly identifies the domain (Customer.io SDK), provides explicit trigger terms, and answers both what and when. The main weakness is that the specific capabilities could be more concrete — listing actual migration actions rather than general terms like 'upgrades' and 'migrations'.
Suggestions
Add more specific concrete actions, e.g., 'Updates deprecated API calls, migrates from TrackAPI to RegionalAPI, resolves breaking changes in customerio-node major version bumps'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Customer.io SDK) and some actions ('upgrades', 'migrations', 'updating to new SDK patterns'), but doesn't list specific concrete actions like 'update API calls from v1 to v2', 'replace deprecated methods', or 'update configuration files'. | 2 / 3 |
Completeness | Clearly answers both 'what' (plan and execute Customer.io SDK upgrades and migrations) and 'when' (upgrading customerio-node versions, migrating from legacy APIs, updating to new SDK patterns) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'upgrade customer.io', 'customer.io migration', 'update customer.io sdk', 'customer.io breaking changes', plus mentions 'customerio-node' package name and 'legacy APIs'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Customer.io SDK upgrades and migrations — a very clear niche that is unlikely to conflict with other skills. The specific product name and version migration context make it distinctly identifiable. | 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 solid, actionable migration guide with clear before/after examples, a well-sequenced workflow, and good validation steps including a test suite and migration checklist. Its main weakness is length — the skill packs a lot of inline code that could benefit from being split into bundle files, and some sections (like the version-check script) are more elaborate than necessary given Claude's capabilities. The error handling table and staged rollout guidance are strong additions.
Suggestions
Extract the migration wrapper (Step 3), test suite (Step 5), and version-check script (Step 1) into separate bundle files referenced from SKILL.md to improve progressive disclosure.
Trim the version-check script in Step 1 — Claude can read package.json and grep for patterns without a full script; a few shell commands would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably focused but includes some unnecessary verbosity — the version-check script in Step 1 is overly elaborate for what Claude could do with a few commands, and the migration wrapper class is quite long. The comments explaining breaking changes in Step 2 are useful but could be more compact. Some sections like the feature flag rollout add bulk that may not always be relevant. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code examples throughout — from version assessment scripts to migration wrappers, test suites, and rollout logic. The before/after migration patterns are concrete and copy-paste ready, and the error handling table maps specific errors to specific solutions. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced from assessment through staged rollout, with explicit validation checkpoints (Step 4 runs tests, Step 5 provides a dedicated migration test suite, Step 6 enables gradual rollout). The migration checklist provides a comprehensive verification list, and the error handling table covers common failure modes with solutions. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's quite long and monolithic for a single SKILL.md with no bundle files. The migration wrapper, test suite, and feature flag code could reasonably be split into separate referenced files. External references are limited to GitHub/npm links rather than structured bundle files. | 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
3a2d27d
- 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.