apollo-migration-deep-dive
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-migration-deep-diveComprehensive 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".
Validation
69%| 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 |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
77%This is a comprehensive, highly actionable migration guide with excellent workflow clarity and validation checkpoints. The main weaknesses are verbosity (could be more concise) and the monolithic structure that puts all implementation details in one file rather than using progressive disclosure to separate overview from detailed implementations.
Suggestions
Remove the 'Completion' section which is meta-commentary not relevant to the skill content
Consider extracting detailed field mappings (SALESFORCE_TO_APOLLO, HUBSPOT_TO_APOLLO) to a separate FIELD_MAPPINGS.md reference file
Condense interface definitions by removing obvious fields or combining related interfaces
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial code examples but is verbose at ~500 lines. Some sections like the interface definitions and helper functions could be condensed, and the 'Completion' section is unnecessary meta-commentary. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for migration assessment, field mapping, batch processing, validation, and rollback. Code is copy-paste ready with clear patterns. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with explicit validation checkpoints at each phase, clear rollback procedures, and feedback loops (validate -> fix -> retry). The phased migration strategy includes percentage-based progression and validation gates. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic file that could benefit from splitting detailed implementations (field mappings, batch workers) into separate reference files. External resources are linked but internal content is not progressively disclosed. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
80%The description excels at trigger terms and completeness with explicit 'Use when' and 'Trigger with' clauses, and is highly distinctive to Apollo.io migrations. 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 migration'
Add concrete deliverables or outputs the skill produces (e.g., 'generates migration plans, field mapping documents, data validation reports')
| 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 | Clearly answers both what (migration strategies, consolidating data sources, large-scale data migrations) and when (explicit 'Use when' clause and 'Trigger with phrases' section with specific triggers). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'apollo migration', 'migrate to apollo', 'apollo data import', 'crm to apollo', 'apollo migration strategy'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Apollo.io platform migrations. The explicit Apollo-related triggers and CRM migration context create a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
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.