agentleFS
johnisanerdjohnisanerd/alphaosint-prospector/skills/prospect/SKILL.md

prospect

Skill0 starsChanged 11 days agoMITView on GitHub

Run the full Alpha OSINT Prospector pipeline from an Ideal Customer Profile to a ranked leads file. Finds companies hiring for roles that signal a need, enriches them with LinkedIn and Crunchbase data, scores each 0-100 with reasons, finds decision-makers and verified work emails, and exports CSV. Use when the user says find me leads, build a prospect list, who should I sell to, find companies hiring SDRs (or any role), or prospect for my ICP. For one stage only use define-icp, source-accounts, enrich-and-score, find-decision-makers or export-leads.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    Read references/conventions.md first.

    line 10
  2. Very specific:

    Call get_icp. If nothing is saved, run the define-icp skill.

    line 13
  3. Very specific:

    Call estimate_cost with the limits below and state the worst case.

    line 16
  4. Distinctive:

    No funding data does not mean no money.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Prospect: ICP in, ranked leads out

Most lead lists start from a static database. This one starts from a live buying signal: a company that posted a job this week for the role your product serves. The pipeline then checks whether that company fits, whether it has money, and who to talk to.

Read references/conventions.md first. The spend and fail-closed rules there apply to every step.

Step 1. ICP

Call get_icp. If nothing is saved, run the define-icp skill. Do not invent an ICP from the user's company name.

Step 2. Estimate, then source

Call estimate_cost with the limits below and state the worst case. Then:

source_companies(max_companies=25, max_jobs_per_keyword=40)

Job boards match loosely: a search for "sales development representative" also returns "Inside Sales Representative - Flooring". The server ignores postings whose title does not contain every word of one of the ICP's hiring keywords and reports them as off_title_jobs_ignored. Expect to keep a third or less, so ask for about 4 jobs per company you want. If almost everything was ignored, the keyword is phrased differently on job boards; go back to define-icp and add the variant as its own keyword. Read the dropped list (agencies, exclusions) to the user in one line.

Sourced accounts usually have no industry, size or website yet. Scores mean little until Step 3.

Step 3. Enrich the top accounts

enrich_companies(top=10)

This runs three lookups in order: the Indeed employer page (cheap, and usually supplies the website that the other two are joined on), LinkedIn, then Crunchbase by domain. Report matched and mismatches_dropped. A mismatch is a namesake with a different website. It is expected for common names and is not an error.

Step 4. People and emails

Emails first, because the email step also returns named people for the ICP's departments:

find_emails(top=5, leads_per_domain=3, verify=true)
find_contacts(top=5)

find_contacts takes names from the enrichment data for free, then searches LinkedIn for the ICP's titles. Companies with no website are skipped by find_emails and listed in skipped_no_website.

Step 5. Show and export

list_leads(limit=10), then for the top 3 call get_lead and give, per account: score, the two strongest reasons, open roles, best contact, email and its verification status. Then export_leads() and give the file path and get_spend.

Judgment calls

  • Score under 40 after enrichment: say it is a weak fit and why. Do not pad the list.
  • No funding data does not mean no money. Bootstrapped and public companies score zero on funding. Say "no round on record".
  • The user asks you to email the leads: refuse that part. This tool researches and sends nothing.

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.