메뉴
One-shot migration between CRM backends. Markdown → Airtable, markdown → Attio, Airtable → markdown, Attio → markdown, or Airtable ↔ Attio. Use when first adopting an external CRM, when leaving one, or when swapping providers. Snapshot-style, not incremental.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Sweep all (or a filtered subset of) email addresses in the workspace CRM and re-verify them via Hunter Email-Verifier. Use periodically — people change jobs, addresses go stale, accept-all status changes. Updates the `verified` and `last-verified` columns in `crm/contacts.md` and prints a summary of what flipped.
Scan the user's existing Claude Code plugins and MCP servers to detect capabilities the career plugin needs (email send, transcription, calendar/tasks, semantic store, CRM). For each capability, decide whether to reuse an already-installed plugin/MCP, install a recommended companion plugin, or add an MCP server. Writes the resolution map to ${CAREER_DATA_DIR}/config.json under a `capabilities` block. Invoked from /career:onboard before install-companion-plugins so we don't double up on capabilities the user already has.
Enrich an existing CRM contact with Hunter Combined-Enrichment — pulls role, seniority, department, social handles, and the contact's company facts in one call. Use to flesh out a thinly-populated CRM row before drafting outreach or prepping for a meeting. Operates on an email address from the CRM; updates the row in place.
Given a person's name and their company (name or domain), return Hunter's best guess at their email address with a confidence score. Use when the user already knows who they want to reach and just needs the address. Differs from find-contact (which lists candidates at a company) — this is targeted at a single named person.
Validate a single email address via Hunter Email-Verifier. Use when the user has an address (handed to them, scraped, guessed) and wants a deliverability + confidence read before sending outreach. Returns Hunter's verdict (deliverable / risky / undeliverable / unknown), score, and the disposable / role / accept-all flags. Does not write to the CRM unless asked.
For CONTEXT_STORE=pinecone — verify the index against the local workspace. Flags vectors whose source file was deleted, renamed, or content-changed (hash mismatch), and surfaces vectors whose content contradicts current ground-truth (stale claims, closed engagements, outdated targets). Proposes deletes/re-embeds; never silently mutates the index.
| name | crm-migrate |
| description | One-shot migration between CRM backends. Markdown → Airtable, markdown → Attio, Airtable → markdown, Attio → markdown, or Airtable ↔ Attio. Use when first adopting an external CRM, when leaving one, or when swapping providers. Snapshot-style, not incremental. |
| disable-model-invocation | false |
| allowed-tools | Read, Write, Bash(mkdir *), Bash(cp *), Bash(date *) |
The migration tool. The adapter skills (crm-adapter-airtable, crm-adapter-attio) are for ongoing two-way sync — this skill is the one-time copy. Always snapshots the source and writes a migration log.
$ARGUMENTS:
--from=<markdown|airtable|attio> and --to=<markdown|airtable|attio>.--dry-run.--object=<companies|opportunities|outreach|all> — default all./career:crm-migrate --from=markdown --to=airtable
/career:crm-migrate --from=attio --to=markdown # leaving Attio
/career:crm-migrate --from=airtable --to=attio # swap providers
Always copy the source state first.
crm/ → ${WORKING_FOLDER}/cache/crm-snapshot-<date>.tar.${WORKING_FOLDER}/cache/<source>-snapshot-<date>.json.Use the field mappings from the relevant adapter SKILL.md. For unmappable fields (e.g. moving from Attio's free-form Notes to markdown row notes column), concatenate with \n---\n and put in a single column.
Show:
--dry-run stops here.
Write to destination. For external CRMs, prefer the adapter's create-by-slug path so re-running is idempotent.
For markdown destinations: write tables in the canonical layout. Preserve any existing rows the migration didn't touch (don't clobber a markdown CRM the user was already curating).
Write ${WORKING_FOLDER}/crm/.migration-<date>.md:
# CRM migration — {{date}}
- from: {{source}}
- to: {{dest}}
- objects: {{which}}
- snapshot: cache/<...>
- migrated: {{counts}}
- skipped: {{counts + reasons}}
- lossy fields: {{list}}
migrated: companies=<n> opportunities=<n> outreach=<n>
skipped: <n> (see log)
snapshot: cache/<source>-snapshot-<date>.<ext>
log: crm/.migration-<date>.md