instantly-migration-deep-dive
Execute complex Instantly.ai migration strategies for platform changes. Use when migrating between cold email platforms, consolidating workspaces, or re-architecting outreach infrastructure around Instantly. Trigger with phrases like "migrate to instantly", "instantly migration", "switch to instantly", "instantly platform migration", "outreach migration".
74
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-migration-deep-dive/SKILL.mdQuality
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 solid skill description with strong trigger terms and clear completeness, explicitly covering both what the skill does and when to use it. Its main weakness is that the capability description is somewhat high-level ('execute complex migration strategies') rather than listing specific concrete actions involved in the migration process. The distinctiveness is excellent due to the narrow focus on Instantly.ai migrations.
Suggestions
Add more specific concrete actions such as 'transfer campaigns, migrate contact lists, configure DNS/sending domains, map warmup settings' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai migration) and some actions (migrating between platforms, consolidating workspaces, re-architecting outreach infrastructure), but doesn't list specific concrete actions like data mapping, account setup, DNS configuration, campaign transfer, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute complex Instantly.ai migration strategies for platform changes) and 'when' (migrating between cold email platforms, consolidating workspaces, re-architecting outreach infrastructure) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes a well-defined set of natural trigger phrases users would actually say: 'migrate to instantly', 'instantly migration', 'switch to instantly', 'outreach migration'. These cover common variations of how users would express this need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Instantly.ai platform migrations specifically. The combination of 'Instantly.ai' + 'migration' creates a clear, distinct trigger that is unlikely to conflict with general email skills or other platform-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured migration guide with concrete TypeScript code and a clear multi-week timeline. Its main weaknesses are incomplete code (placeholder values, unfinished OAuth flow), lack of programmatic validation steps between migration phases, and excessive inline code that could be split into referenced files. The error handling table and migration timeline are strong additions.
Suggestions
Add programmatic validation between steps (e.g., verify account count after import, verify lead counts match source, check warmup status before proceeding to parallel run) rather than relying on console.log checklists.
Complete the OAuth flow code or remove it — the current version polls once and stops, which is misleading. Either show a complete polling loop or just reference the OAuth docs.
Split the detailed TypeScript implementations into separate referenced files (e.g., `migration-scripts/import-accounts.ts`) and keep SKILL.md as a concise overview with the timeline, checklist, and error table.
Remove placeholder return values (sourceLeadCount: 0) from the audit function — either make it actually compute values from a source platform export or simplify to just the checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with some verbose code blocks that could be tightened. The migration plan interface returning placeholder zeros, the OAuth polling example that doesn't complete, and extensive console.log checklists add bulk. However, most content is functional rather than explanatory, and it avoids explaining basic concepts. | 2 / 3 |
Actionability | The code is mostly executable TypeScript with concrete API calls and field mappings, which is good. However, it relies on an undefined `InstantlyClient` import, several functions return placeholder data (sourceLeadCount: 0), the OAuth flow is incomplete (polls once then stops), and the parallel run monitor is more of a reporting script than actionable migration logic. | 2 / 3 |
Workflow Clarity | The 5-step sequence is logical and the migration timeline provides a clear week-by-week plan. However, validation checkpoints are mostly checklists printed to console rather than programmatic checks. There's no explicit feedback loop for verifying lead import accuracy, no validation that accounts were successfully added before enabling warmup, and the parallel run lacks concrete go/no-go criteria. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, a summary table, timeline, and error handling table. However, it's quite long (~200+ lines of code) and could benefit from splitting detailed code into separate files (e.g., account-migration.ts, lead-import.ts) with the SKILL.md serving as an overview. The references at the end are good but the inline content is heavy. | 2 / 3 |
Total | 8 / 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.