instantly-upgrade-migration
Migrate Instantly.ai integrations from API v1 to v2. Use when upgrading from deprecated v1 endpoints, updating authentication, or migrating endpoint paths and request formats. Trigger with phrases like "instantly v1 to v2", "instantly api migration", "instantly upgrade", "instantly deprecated", "migrate instantly api".
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 niche (Instantly.ai API v1→v2 migration) and provides explicit trigger terms and use-when guidance. The main weakness is that the specific capabilities could be more detailed — listing concrete migration actions beyond the general 'updating authentication' and 'migrating endpoint paths'.
Suggestions
Add more specific concrete actions such as 'convert API key auth to OAuth2', 'update campaign endpoint paths', or 'transform v1 request payloads to v2 format' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai API migration v1 to v2) and mentions some actions like 'updating authentication' and 'migrating endpoint paths and request formats', but doesn't list comprehensive concrete actions (e.g., specific endpoint mappings, payload transformations, error handling changes). | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate Instantly.ai integrations from API v1 to v2) and 'when' (upgrading from deprecated v1 endpoints, updating authentication, migrating endpoint paths). Includes explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'instantly v1 to v2', 'instantly api migration', 'instantly upgrade', 'instantly deprecated', 'migrate instantly api' — these are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific product (Instantly.ai) and a specific migration path (v1 to v2). Extremely unlikely to conflict with other skills due to the narrow, product-specific 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 migration skill with excellent concrete code examples, a comprehensive endpoint mapping table, and a clear multi-step workflow with validation checklist. Its main weakness is length — the skill tries to be both an overview and a complete reference, which makes it longer than ideal for a SKILL.md. Some content like the full adapter class and v2 feature examples could be split into referenced files.
Suggestions
Move the full InstantlyV1ToV2Adapter class and v2 feature adoption examples into separate referenced files (e.g., ADAPTER.md, V2_FEATURES.md) to keep SKILL.md as a concise overview
Remove the Prerequisites section — Claude doesn't need to be told it needs 'Understanding of Bearer token authentication'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code examples, but includes some unnecessary sections like 'Prerequisites' (listing 'Understanding of Bearer token authentication' is patronizing to Claude), and the 'Next Steps' and some commentary could be trimmed. The v1 code comments explaining what's deprecated are slightly verbose but still useful for migration context. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples, a complete migration adapter class, concrete bash commands for auditing, specific endpoint mappings in a table, and real request/response body structures. The code is copy-paste ready and covers the full migration lifecycle. | 3 / 3 |
Workflow Clarity | Clear 4-step sequential workflow (Audit → Create Adapter → Migrate Pagination → Adopt New Features) with a comprehensive migration checklist that serves as validation checkpoints. The error handling table provides a feedback loop for common migration failures, and the checklist ensures nothing is missed. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's quite long (~200 lines of substantive content) and could benefit from splitting the migration adapter code and v2 feature examples into separate referenced files. The endpoint migration table, request body changes, and adapter code could each be their own referenced documents to keep the SKILL.md as a concise overview. | 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.