agentleFS
Sign inStart free
automatewithudayautomatewithuday/gtm-prospecting-system/skills/follower-scrape/SKILL.md

follower-scrape

Skill1 starsChanged 56 days agoMITView on GitHub

Use when stage 5 of the prospecting system needs the people behind the selected audiences collected — LinkedIn page followers via GetLeads, post engagers, community members, or event attendees — with the source of every person preserved. Also use when the ask is \"get me the followers of this company page\".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every output row gets source_type and source_detail added:

    line 21
  2. Very specific:

    Add the cost to spent_usd in state.json.

    line 38
  3. Distinctive:

    Never edit or trim a raw file.

    line 58
  4. Distinctive:

    No purchase without the human saying yes to that specific page and count.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Follower Scrape

Collects the raw audience. It does not judge fit — that is stage 6 — and it never drops the label saying where a person came from.

Pipeline contract

Stage 5 of 20. Reads 04-audiences.csv (rows with selected=true). Writes one file per audience to 05-audience-raw/<audience_type>-<name-slug>.csv.

Files live in runs/<run>/. Column definitions: /prospecting-system.

Every output row gets source_type and source_detail added:

Collected howsource_type
follows a LinkedIn pagefollower
reacted to or commented on a postengager
member of a communitymember
registered for or attended an eventattendee

A follower is a weaker signal than an engager. Keep them distinct; stage 11 ranks on it.

Route A — LinkedIn page followers (GetLeads)

Works the same for competitor, tool, and event pages: each is a LinkedIn company page.

  1. lookup_company_linkedin_followers with the page URL and the ICP filters (company_sizes, seniorities, countries from 02-client-profile.yaml). Free. Billing is on the requested count; non-matching leads are refunded after delivery.
  2. Show the human: follower count, price, and the run's remaining spend cap. Ask how many followers to buy and which email receives the CSV. Minimum order is 2,500 leads ($8.75); smaller pages are billed the minimum.
  3. Add the cost to spent_usd in state.json. If it would pass the cap, stop and ask. Also call get_wallet_balance: if the purchase would drop the wallet below an enabled auto top-up threshold, tell the human the card will be charged the top-up amount as well. That charge is outside the run's cap.
  4. prepare_company_followers_checkout returns a payment link. The human pays in the GetLeads app — do not attempt checkout yourself.
  5. The CSV arrives by email. The human saves it to 05-audience-raw/. Mark the stage blocked with note waiting for follower CSV: <page> until it lands, and carry on with the account lane (stages 3 and 7) meanwhile.

One page first. Run its CSV through stage 6 on a sample before buying the next page — if the judge rejects most of it, the page was wrong, and buying its siblings repeats the mistake.

Route B — Post engagers

People who commented on or reacted to a competitor's posts. Two options:

  • GetLeads MCP scrape_linkedin_post_once for a specific post (estimate_scrape_cost first; wallet cash).
  • The full harvester with scoring: linkedin-competitor-icp-scorer (Apify). Drop its ranked_engagers.csv into 05-audience-raw/ and keep comment_excerpt — stage 13 uses it.

Route C — CSV import (communities, events, anything else)

Member exports, attendee lists, sponsor-provided lists, a Reddit author pull. Save the file to 05-audience-raw/ as-is and add source_type + source_detail. Only import lists you are permitted to use for outreach; note where each came from in source_detail.

Rules

  • Never edit or trim a raw file. Normalizing and deduping happen in stage 6.
  • No purchase without the human saying yes to that specific page and count.
  • A paid stage whose output file exists is never re-run.

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.

Check your setup, free