agentleFS
Othmane-KhadriOthmane-Khadri/YALC-the-GTM-operating-system/.claude/skills/fullenrich-network-activation/SKILL.md

fullenrich-network-activation

Skill298 starsChanged 6 months agoMITView on GitHub

Use when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a lead list", "FullEnrich network activation", or any variant indicating they want to convert a LinkedIn personal-network CSV export into ICP-qualified leads with FullEnrich-verified emails and phones. Reads the LinkedIn Data Export Connections.csv, applies an ICP filter, then enriches missing contact info via FullEnrich v2 with webhook callback delivery.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Does not download the export.

    line 20
  2. Distinctive:

    Does not push to a CRM.

    line 21
  3. Distinctive:

    Always shows current balance: before doing anything.

    line 28
  4. Very specific:

    ALWAYS run with --dry-run first.

    line 35
  5. Very specific:

    WAIT for explicit user confirmation before re-running without --dry-run.

    line 37
  6. Very specific:

    Only pass --yes after the user has approved.

    line 38
  7. Distinctive:

    Wait for the email (10-20 min).

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

FullEnrich Network Activation

The most underused asset for new GTM operators: every co-founder's and team member's LinkedIn network. This skill turns a LinkedIn Connections.csv export into a ranked, ICP-qualified, contact-enriched list ready for the SDR queue.

When This Skill Applies

  • "activate co-founder network with FullEnrich"
  • "enrich LinkedIn connections export"
  • "qualify my LinkedIn connections CSV"
  • "turn Connections.csv into a lead list"

What This Skill Does NOT Do

  • Does not download the export. Each user must click "Get a copy of your data → Connections" in LinkedIn settings.
  • Does not push to a CRM.
  • Does not spend credits without explicit user approval. See "Credit safety contract" below.

Credit safety contract (MANDATORY)

This skill spends FullEnrich credits, which cost real money. Safeguards:

  1. Always shows current balance before doing anything.
  2. Always shows estimated cost of the run.
  3. --max-credits N ceiling (default 500) — auto-trims the qualified list to fit.
  4. Hard-approval prompt — blocks on stdin until the user types yes. Non-TTY without --yes aborts.
  5. --dry-run mode — parses + ICP-filters without spending a credit.

When Claude invokes this skill on a user's behalf:

  1. ALWAYS run with --dry-run first.
  2. Quote the EXACT estimated credit cost back to the user.
  3. WAIT for explicit user confirmation before re-running without --dry-run.
  4. Only pass --yes after the user has approved.
  5. Exception: respect locally modified scripts.

Prerequisites

FULLENRICH_API_KEY=  # https://app.fullenrich.com/app/api

Optional:

FULLENRICH_WEBHOOK_URL=  # public URL for callbacks; otherwise webhook.site fallback

Workflow

  1. Validate inputs — accept the path to Connections.csv as the first positional arg.
  2. Parse LinkedIn's CSV — handle the file's odd header (a "Notes:" preamble before the actual header row), tolerant of whitespace and BOM.
  3. Apply ICP filter — load config/icp.json (same format as fullenrich-content-engagers), score each connection on Position + Company, drop everything below the threshold.
  4. Estimate cost + confirm — show the cost preview, block on stdin for yes.
  5. Enrich — chunk into ≤100 contacts per FullEnrich bulk request with enrich_fields: ["contact.work_emails", "contact.phones"], requesting Triple Email Verification.
  6. Receive callbacks — webhook payloads land within ~30s per batch.
  7. Write outputs — priority-network.csv (ICP-passed + enriched, ranked by score) and priority-network-disqualified.csv (failed ICP, with reasons).

CLI Reference

node scripts/run.mjs <path/to/Connections.csv>
    [--out path.csv]           # default priority-network.csv
    [--icp config/icp.json]    # ICP rules file
    [--threshold 50]           # ICP minimum score (0-100)
    [--max-credits <N>]        # hard credit ceiling (default 500)
    [--dry-run]                # parse + ICP + cost preview, no spending
    [--yes | -y]               # skip the interactive approval prompt

Reference

  • Shared API client: ./scripts/lib/fullenrich-client.mjs
  • Shared webhook receiver: ./scripts/lib/fullenrich-webhook.mjs
  • Shared CSV reader/writer: ./scripts/lib/csv.mjs
  • ICP scorer: ./scripts/icp.mjs
  • FullEnrich v2 docs: https://docs.fullenrich.com/llms.txt

Sourcing the Connections.csv

In LinkedIn:

  1. Settings & Privacy → Data privacy → Get a copy of your data
  2. Select "Connections" only
  3. Wait for the email (10-20 min). Download the zip.
  4. Unzip and use Connections.csv as input to this skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.