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

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is lean and highly actionable with executable end-to-end migration code, but its multi-step batch/destructive workflow lacks explicit validation checkpoints and the provided implementation-guide reference is not surfaced from the body.

Suggestions

Add explicit validate→fix→retry checkpoints within the batch migration and rollback steps, not only the pre-migration assessment gate.

Link to references/implementation-guide.md from the body (e.g., a 'Full implementation' pointer) so the existing bundle is discoverable and the body can stay an overview.

Move the full pipeline example or detailed code into the implementation guide and keep the SKILL.md body as a concise overview pointing to it.

DimensionReasoningScore

Conciseness

The body is mostly executable code with minimal framing prose and assumes Claude's competence; it does not explain basic concepts, and every section earns its place.

3 / 3

Actionability

Provides complete, executable TypeScript with real Apollo endpoints (POST /contacts/bulk_create, /contacts/search, DELETE), concrete field mappings, and a copy-paste-ready full pipeline example.

3 / 3

Workflow Clarity

A clear 5-step sequence exists with a pre-migration validation gate, but the destructive batch migration and rollback steps lack explicit validate→fix→retry feedback loops, capping the score per the batch/destructive rule.

2 / 3

Progressive Disclosure

Sections are organized, but a references/implementation-guide.md bundle exists yet is never linked or signaled from the SKILL.md body, and substantial code that could live in the reference is inlined.

2 / 3

Total

10

/

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 concise, specific, and clearly signals both capability and trigger conditions with natural user phrasing. It distinguishes itself well via Apollo-specific terminology.

DimensionReasoningScore

Specificity

Names the Apollo.io domain and lists multiple concrete actions — "migrating from other CRMs to Apollo", "consolidating data sources", and "executing large-scale data migrations" — rather than abstract language.

3 / 3

Completeness

Explicitly answers both what (Apollo.io migration from CRMs/sources) and when via a clear "Use when migrating..." clause with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural trigger phrases users would actually say ("apollo migration", "migrate to apollo", "apollo data import", "crm to apollo", "apollo migration strategy"), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Targeted at a narrow niche (Apollo.io migration) with distinct, product-specific triggers 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.