outreach-filter

Solid

Clean and segment a lead list before a single credit is spent on it. Deduplicates by email, by company domain and by LinkedIn profile, handling the awkward cases (subdomains, plus aliases, apostrophes and accents in names, Sales Navigator URLs that never string match a public profile), excludes existing customers, competitors and blacklisted addresses using find_contact and the Emelia blacklist endpoints, drops generic mailboxes such as contact@ and info@ and the junior roles that cannot buy, checks that geography and headcount match the ICP, and splits what survives into segments that each deserve a different message. Reads outreach/leads.csv and outreach/icp.json, writes a smaller leads.csv plus a report of every row removed and why. Triggers on: filter, clean the list, dedupe, deduplicate, duplicates, remove customers, exclusion list, blacklist, suppression list, generic emails, contact@, role address, segment the list, segmentation, list hygiene, data quality, before enrichment.

Data & Documents 12 stars 2 forks Updated 2 days ago MIT

Install

Quality Score: 82/100

Stars 20%

37

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

80

License 10%

100

Description 5%

100

Skill Content

# Filter and segment the list ## What this does Takes `outreach/leads.csv` and gives back a shorter one, plus a written account of every row that left and why. It deduplicates, removes customers, competitors and blacklisted addresses, drops shared mailboxes and roles that cannot buy, checks geography and size against the ICP, and splits the rest into segments. This step spends no Emelia credits, and it exists so that the next step does not spend them on rows you were going to delete. Filtering before enriching is the single change that most reduces the cost of a campaign. ## When to use it Always, between [outreach-leads](../outreach-leads/SKILL.md) and any enrichment. Also on its own, when a user arrives with an old list and asks what is still usable in it: this skill answers that question for free. Use a different skill when: - The list does not exist yet: `outreach-leads`. - The list is clean and needs addresses: `outreach-enrich`, which runs after this. - The problem is who you are targeting, not the rows: go back to [outreach-icp](../outreach-icp/SKILL.md). ## Inputs | Input | Required | If missing | |---|---|---| | `outreach/leads.csv` | yes | Ask for a path, or run `outreach-leads` first. | | `outreach/icp.json` | strongly recommended | Without it you cannot check geography, size or segments. Ask for the country list and the headcount band as a minimum, and say which checks you skipped. | | Customer domains | strongly recommended | Ask for a CRM export with ...

Details

Author: emelia-io
Repository: emelia-io/claude-outreach
Created: 3 days ago
Last Updated: 2 days ago
Language: Python
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

outreach-leads

Build the lead list by actually querying the sources this repository supports: the Basile API for French B2B, where an ICP becomes a plan of several queries (adjacent job titles, size bands, zones, sources), each counted for free with countOnly before a single record is extracted, then merged, deduplicated and cut of what is obviously off target before any enrichment credit is spent; a LinkedIn Sales Navigator search collected through the Emelia LinkedIn scraper; or a CSV the user already has (encoding, separator and column mapping handled). Writes outreach/leads.csv with a fixed 26 column schema that every other skill in this repository reads, including a source and a source_url column on every row. Reads outreach/icp.json, a Sales Navigator URL or a file path. Triggers on: build a list, lead list, source leads, find companies, find prospects, Basile, api.basile.cc, docs.basile.cc, French companies, SIREN, NAF, activity filter, count before extracting, Sales Navigator, LinkedIn search, LinkedIn scraper, scra

12 Updated 2 days ago

Data & Documents Solid

outreach-enrich

The full enrichment waterfall on a lead list: filter first, find the missing emails, verify only the addresses that came from somewhere other than Emelia's finder, find mobile numbers only where they are worth 50 credits, then decide row by row who is sendable, who is on hold and who is dropped. Ends by routing the rows to separate destinations, one list per destination: addresses found go to the email campaign list, rows with no address but a valid LinkedIn profile URL are proposed as a separate LinkedIn campaign, and the rest is set aside and counted. Never pushes a whole enriched base into a single Emelia list. Runs under a credit budget fixed before the first call and stops when it is reached. Writes outreach/enrichment.json with every counter and updates outreach/leads.csv without losing a single original column, then fills the custom fields your sequence needs. Triggers on: enrich, enrichment, enrich my list, waterfall, find and verify, clean and enrich, contact data, credits budget, how much will this

12 Updated 2 days ago

Data & Documents Solid

outreach-icp

Turn a vague outbound brief such as 'sell our tool to SaaS companies' into a targeting spec that a data source can actually execute: job titles with their real per-country variants, industries with NAF, NAICS and SIC codes, headcount band, geography, technographics, buying signals, and the exclusions that keep customers, competitors and unpayable prospects out of the list. Estimates the addressable market with free count calls before a single credit is spent, and splits the brief into separate campaigns when it covers too many audiences. Reads a brief in plain language, writes outreach/icp.json. Triggers on: ICP, ideal customer profile, targeting, target audience, who should I target, define my market, segment, segmentation, persona, buyer persona, job titles, NAF code, NAICS, SIC, headcount, firmographics, technographics, buying signals, exclusion list, TAM, addressable market, market sizing.

12 Updated 2 days ago