Enriches a list of leads using the Trigify CLI (profile data + recent posts). Spawns parallel agents that each handle 10 leads at a time for speed. Used across outreach-check, outreach-launch-campaign, and outreach-intent-campaign. Use this skill when the user says "enrich leads", "enrich this list", "get lead details". Also trigger as step #2 of outreach-launch-campaign (Sub-routine B) and step #4 of outreach-intent-campaign (Sub-routine C).
Takes a lead list and enriches each lead using the Trigify CLI. Runs in parallel — 5 agents × 10 leads each — so 50 leads enrich simultaneously instead of one at a time.
Automation level: AUTONOMOUS — runs without interruption, merges results, passes to ICP qualify.
Routine positions: Outreach-check #3 | Outreach-launch #2 | Outreach-intent #4
Reads from the most recent relevant input file based on which sub-routine is running:
inbox/outputs/json/YYYY-MM-DD-apollo-raw.jsoninbox/outputs/json/YYYY-MM-DD-post-leads-filtered.jsonNote on URN-format profile URLs (Sub-routine C): Leads from trigify post engagements have URN-format URLs: linkedin.com/in/ACoAA.... These work fine with trigify profile enrich. Expect ~50% NOT_FOUND rate — skip failed leads silently and continue. The enriched result includes a clean linkedin_url (e.g. linkedin.com/in/username) that should replace the URN URL in downstream data.
inbox/outputs/json/YYYY-MM-DD-replies-raw.jsonMinimum required field per lead: linkedinUrl (or linkedin_url). Carry forward all other fields
from the input file — do not drop intent-specific fields (track, postTopic, sourcePostUrl, sabPostUrl).
Take all leads from the raw list. Split into batches of 10. For 50 leads → 5 batches.
Name the batch output files:
inbox/outputs/json/YYYY-MM-DD-enriched-batch-1.jsoninbox/outputs/json/YYYY-MM-DD-enriched-batch-2.jsonSpawn all batches simultaneously using the trigify-enrichment-agent (.claude/agents/trigify-enrichment-agent.md).
Each agent receives:
leads: their batch of 10 lead objectsoutput_file: their assigned batch output pathbatch_number: 1–5All 5 agents run at the same time. Do not wait for one before starting the next.
Once all 5 batch files exist and are written, proceed. If a batch file is missing after the agent completes, log a warning and continue — never block the whole run for one failed batch.
Combine all batch files into one enriched list:
YYYY-MM-DD-enriched-batch-*.json filesenriched: falseSave merged output to: inbox/outputs/json/YYYY-MM-DD-enriched-leads.json
Print to screen:
Enrichment complete — YYYY-MM-DD
─────────────────────────────────
Input leads: 50
Successfully enriched: X
Skipped (unenrichable): Y
Post data retrieved: Z (via Trigify: A | none: C)
Passing X enriched leads to acquisition-icp-qualify.
"trigify CLI not found — check PATH (expected: ~/.npm-global/bin/trigify)". Stop and surface to user.