full-crm
Use when the user wants to move already enriched contacts into a CRM and has a separate CRM MCP connected. Orchestrates that separately connected CRM MCP: confirms the connector, proposes field mapping, checks duplicates, requests explicit confirmation, then calls only the CRM MCP's tools. FullEnrich MCP itself only searches, enriches, and exports CSV/JSON; it does not write CRM records. Triggers on: "push to CRM", "sync contacts", "update my CRM", "add these to HubSpot", or similar requests.
Install
With your agent
Install OMGSkills skill "fullenrich/fullenrich-skills:skills/full-crm" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/FullEnrich/fullenrich-skills /tmp/fullenrich-skills && ln -s /tmp/fullenrich-skills/skills/full-crm ~/.claude/skills/full-crmFrom README
FULL CRM Level: Beginner Estimated cost: 0 credits (enrichment already done). CRM API calls depend on the CRM's own limits. Capability boundary FullEnrich MCP searches, enriches, and exports results as CSV or JSON. FullEnrich MCP does not write to CRMs. This skill calls only a separately connected CRM MCP, and only after explicit confirmation. Examples "Push these 20 enriched contacts to HubSpot" "Sync my enrichment results to Salesforce" "Add these leads to Attio with the company research as notes" "I just enriched 50 contacts, push them to my CRM" --- Persona You are a CRM data quality specialist. You've seen hundreds of CRMs wrecked by bad imports — duplicate records, missing fields, mangled mappings. You know that a bad CRM sync is worse than no sync at all. You are pedantic about duplicates. You check before you push. Every time. You never overwrite. Existing data in a CRM is trusted until proven wrong. New data fills gaps — it doesn't replace. You challenge bad mappings.
More from this repo
full-csv
Used when the user uploads a CSV file containing contacts (LinkedIn URLs, names + companies, or any combination) and...
full-lookalike
Used when the user has a LinkedIn profile and wants to find similar people — same type of role, seniority, industry,...
full-meeting
Used when the user has an upcoming meeting and wants a comprehensive brief on the person they're meeting.