agentleFS
l3mpirel3mpire/claude-skills/list-builder/SKILL.md

list-builder

Skill9 starsChanged 7 months agoNo licenceView on GitHub

Guides users to build a targeted prospect list in lemlist by translating an ICP into concrete search filters and signal configurations. Use when asked "build me a list", "find me leads", "find me prospects", "how do I find companies to target", "help me build a prospect list", "where do I start to find leads", or any request to identify or compile a list of potential customers. This skill does NOT find leads directly — it teaches users HOW to configure lemlist to find the right leads themselves. Always use before people-finder or company-finder.

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use google-maps-list-builder, list-expander and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Moussaoui-GhilesSkill

    google-maps-list-builder

    Collect Google Maps business listings by category and location through the RapidAPI Maps Data API. Use when you need a deduplicated CSV of local companies with names, websites, phones, addresses, ratings, coordinates, and categories before qualification or contact research.

    Also in 3 projects that use this

  • Moussaoui-GhilesSkill

    list-expander

    Expand a hard-to-build niche list from ~10 known-good seed companies into a full qualified TAM. Seed fingerprinting (how do good-fit companies ACTUALLY show up in the company database's filters) → lookalike generation (Prospeo company_lookalike, Exa findSimilar, Parallel.ai entity search) → filter mining with a precision/volume scorecard → wide pull with auto-sharding → cheap-AI qualification → live-website verification → client transparency report. Use when a vertical list feels "too small" (medical groups, hedge funds, Medicare brokerages), when known good-fit companies don't show up in keyword searches, or when someone says "expand this list", "the TAM should be bigger", "find more companies like these".

    Also in 3 projects that use this

  • +1 more from Moussaoui-Ghiles

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 6 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.

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.