CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-migration-deep-dive

Comprehensive Apollo.io migration strategies. Use when migrating from other CRMs to Apollo, consolidating data sources, or executing large-scale data migrations. Trigger with phrases like "apollo migration", "migrate to apollo", "apollo data import", "crm to apollo", "apollo migration strategy".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with a clear, validated multi-step migration workflow, but it is held back by an orphaned bundle reference (implementation-guide.md is never linked) and notable content overlap between the body and that reference.

Suggestions

Add a clearly signaled pointer to references/implementation-guide.md (e.g., an 'Advanced / full implementation' section linking to it) so the bundle file is discoverable from SKILL.md.

Reduce overlap by trimming the inlined full code blocks that the implementation guide already covers, keeping SKILL.md as a lean overview and delegating detail to the reference.

Remove the unexplained `## Current State` (`npm list`) artifact, and note in the reconciliation step that only a 100-record sample is verified (or expand it) so the validation scope is explicit.

DimensionReasoningScore

Conciseness

Mostly efficient TypeScript with little explanatory padding, but the body duplicates much of references/implementation-guide.md (field mapping, batch worker, validation, rollback) and includes an unexplained `## Current State` (`npm list`) artifact, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript against real endpoints (e.g. `POST /contacts/bulk_create`, `/contacts/search`) with concrete field mappings and rate-limit handling, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced (mappings → assessment → batch migration → reconciliation → rollback) with explicit validation checkpoints (pre-migration assessment, a >10%-invalid gate, reconciliation, and a rollback path), so batch/destructive validation is present rather than missing.

3 / 3

Progressive Disclosure

Sections are well-organized, but references/implementation-guide.md is never linked or signaled from the body, and detailed code that could live in the reference is inlined — matching 'references present but not clearly signaled; content that should be separate is inline'.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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: concrete actions, explicit 'Use when' trigger guidance, natural trigger phrases, and a distinct Apollo-migration niche. Voice is appropriately third person / imperative with no first- or second-person phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "migrating from other CRMs to Apollo, consolidating data sources, or executing large-scale data migrations" — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers both 'what' (Apollo.io migration / consolidating data sources / large-scale migrations) and 'when' with an explicit "Use when migrating from other CRMs to Apollo..." clause plus trigger phrases, so it is not capped at 2.

3 / 3

Trigger Term Quality

Provides natural phrases a user would say — "apollo migration", "migrate to apollo", "apollo data import", "crm to apollo", "apollo migration strategy" — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Apollo.io-migration niche with Apollo-specific trigger phrases is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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