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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-migration-deep-dive83
Quality
78%
Does it follow best practices?
Impact
96%
1.77xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-migration-deep-dive/SKILL.mdDiscovery
79%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 has excellent trigger term coverage and completeness with explicit 'Use when' and 'Trigger with' clauses, making it easy for Claude to select appropriately. However, it lacks specificity about what concrete actions the skill performs - 'comprehensive migration strategies' is vague and doesn't tell Claude what capabilities are actually available.
Suggestions
Replace 'Comprehensive Apollo.io migration strategies' with specific actions like 'Maps CRM fields to Apollo schema, transforms contact/company data, validates data integrity, handles deduplication during Apollo.io migrations'
Add concrete capabilities such as 'Generates migration scripts, creates field mapping documentation, identifies data quality issues'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive migration strategies' without listing concrete actions. It doesn't specify what actions are performed (e.g., mapping fields, transforming data, validating records). | 1 / 3 |
Completeness | Explicitly answers both what ('migration strategies', 'migrating from other CRMs', 'consolidating data sources', 'large-scale data migrations') and when ('Use when...' clause with clear triggers). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'apollo migration', 'migrate to apollo', 'apollo data import', 'crm to apollo', 'apollo migration strategy' - these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io migrations specifically. The explicit Apollo-related trigger terms make it unlikely to conflict with generic CRM or data migration skills. | 3 / 3 |
Total | 10 / 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 comprehensive, highly actionable migration guide with excellent workflow clarity and validation checkpoints. However, it suffers from verbosity - the 500+ lines of inline code could be better organized with progressive disclosure, splitting detailed implementations into separate reference files while keeping the main skill as a concise overview with navigation.
Suggestions
Split detailed code implementations (field mappings, batch workers, validation) into separate reference files (e.g., FIELD_MAPPINGS.md, BATCH_WORKER.md) and keep SKILL.md as a concise overview with links
Condense interface definitions - Claude can infer TypeScript types from usage patterns without explicit interface blocks
Remove the 'Completion' section which is meta-commentary about the skill pack rather than actionable migration guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose for a migration guide. Many code blocks include boilerplate and interface definitions that could be condensed. The 500+ lines could be reduced significantly while preserving actionability. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with concrete implementations for assessment, field mapping, batch processing, validation, and rollback. Code is copy-paste ready with specific examples for Salesforce and HubSpot migrations. | 3 / 3 |
Workflow Clarity | Excellent multi-phase migration workflow with explicit validation checkpoints at each phase, clear rollback procedures, and error recovery patterns. The phased approach (Pilot → Early Adopters → Main → Cleanup) with validation gates is well-structured. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one massive file. The detailed code implementations for field mapping, batch workers, and validation could be split into separate reference files with the main skill providing an overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (568 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 11 Passed | |
Table of Contents
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.