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 clear 'what' and 'when' clauses, explicit trigger terms, and a highly distinctive niche. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., specific version migrations, specific API changes handled). Overall it's a strong description that would enable accurate skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Updates import paths, replaces deprecated TrackAPI/RegionalAPI calls, migrates to new request/response patterns' to improve specificity.
| 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 import statements', 'replace deprecated API calls', or 'handle breaking changes in v3'. The actions remain somewhat high-level. | 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 separately. | 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'. Also includes natural keywords like 'customerio-node versions', 'legacy APIs', and 'SDK patterns' in the body text. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Customer.io SDK upgrades/migrations) with product-specific trigger terms. Unlikely to conflict with other skills unless there's another Customer.io-related skill. | 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 code examples, a well-sequenced workflow, and good validation steps including a test suite and migration checklist. Its main weakness is length — the migration wrapper, test suite, and feature flag rollout code could be split into referenced files to improve token efficiency. The dynamic shell commands at the top for current state detection are a nice touch.
Suggestions
Extract the migration wrapper (Step 3), test suite (Step 5), and staged rollout (Step 6) into separate referenced files to reduce the main skill's token footprint.
Remove the version-check TypeScript script (Step 1) — the shell commands in 'Current State' already accomplish this, and Claude can read package.json directly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably focused but includes some unnecessary verbosity — the version check script is overly elaborate for what `npm list` already does, comments explaining obvious things like 'Legacy-compatible identify' add bulk, and the staged rollout section with a custom hash-based feature flag is tangential to the core migration task. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for every step — version assessment, migration wrapper, test suite, and rollout. Commands are copy-paste ready (npm install, test commands), and the before/after migration patterns are concrete and specific. | 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 is a dedicated 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 a helpful error table, but it's quite long (~200 lines of substantive content) and could benefit from splitting the migration wrapper, test suite, and staged rollout into separate referenced files. The reference to 'customerio-ci-integration' at the end is good but the main body is 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.