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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with concrete code and clear sequencing, but loses points for relying on an unbundled client, missing validation feedback loops around destructive batch operations, and keeping everything in a single monolithic file.

Suggestions

Add explicit validate -> fix -> retry checkpoints before destructive/batch steps (e.g., verify a small test import and inbox rates before pausing the old platform in the cutover).

Provide or bundle the referenced ./src/instantly/client so the code examples are self-contained and copy-paste executable, or document the assumed API surface inline.

Move the detailed per-step code and 4-week timeline into reference files (e.g., STEPS.md, TIMELINE.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient (code, tables, checklists with little concept-explanation padding), but repetitive boilerplate such as the account-credential object spelled out twice and a partial OAuth polling stub could be tightened.	2 / 3
Actionability	Concrete TypeScript code and field mappings are provided for each step, but the code depends on an unbundled ./src/instantly/client and the OAuth function is an incomplete stub, so it is not fully copy-paste executable as-is.	2 / 3
Workflow Clarity	The 5-step sequence, 4-week timeline, and cutover checklists are clearly ordered, but batch/destructive operations (bulk lead import, block-list bulk-create, old-platform decommission) lack explicit validate-then-fix-then-retry feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	Content is well-sectioned but lives entirely in one ~330-line monolithic file with no references to separate detail files, so material that could be split out (full API usage, timeline) is inline rather than one level deep.	2 / 3
	Total	8 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: specific actions, natural trigger phrases, and explicit what/when guidance for a distinct niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete migration actions — "migrating between cold email platforms, consolidating workspaces, or re-architecting outreach infrastructure" — rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what ("Execute complex Instantly.ai migration strategies") and when ("Use when migrating between cold email platforms, consolidating workspaces, or re-architecting outreach infrastructure") with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say ("migrate to instantly", "instantly migration", "switch to instantly", "outreach migration") plus a Use-when clause, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Instantly.ai cold-email platform migration) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.