normalise-outreach-names
Skill1 starsChanged 49 days agoMITView on GitHub
Normalise first names and company names in an outreach list so template merge fields read naturally. Strips emoji, credentials, honorifics, and legal suffixes, shortens companies to the name a person would say aloud, and enforces a caps policy (no ALL CAPS unless it is a true acronym or the brand styles itself that way everywhere). Use before any CSV goes into an email tool or enrichment table, or when the user says "normalise names", "clean up the company names", "fix the first names", or "the merge fields look wrong".
In this repository12 other files it gives its agents.
- ad-description-makerSkill
- ad-headline-makerSkill
- b2b-ad-creativeSkill
- cold-outreachSkill
- deep-ad-researchSkill
- gtm-contextSkill
- icp-scoringSkill
- jtbd-researchSkill
- linkedin-connection-analysisSkill
- linkedin-post-distillSkill
- positioning-messagingSkill
- tech-stack-prospectsSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If the answers are obvious from the file, proceed and state your assumptions.
- Distinctive: line 27
Read the CSV and identify the name and company columns.
- Very specific: line 28
Add First name and Company clean columns.
- Distinctive: line 30
Verify any unfamiliar all-caps names (see the caps policy).
- Distinctive: line 39
If the first name is still unusable (a company name, a single letter, or empty), leave it blank and flag the row.
- Distinctive: line 47
Never use "your company" instead of a name.
- Distinctive: line 48
Never "correct" a brand that styles itself lowercase: If the source is lowercase and the brand writes itself that way, trust it.
- Distinctive: line 52
ALL CAPS is banned in merge fields unless one of these holds:
- Distinctive: line 59
If you can't verify it, use sentence case.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Normalise outreach names
A merge field is a promise that a human wrote this. "Hey NORTHWIND LTD" breaks it instantly. Every list gets these rules before it touches a template.
Before you start
This skill works on a list, so it rarely needs the shared context file. If .agents/product-marketing.md (or .claude/product-marketing.md) exists, check it for a "words to use" or brand list that should override the defaults below.
Confirm, in one message:
- Which file, and which columns hold the person's name and the company name.
- Whether to reuse a caps-OK list from earlier runs (look for
caps-ok.txtnext to the CSV).
If the answers are obvious from the file, proceed and state your assumptions.
Workflow
- Read the CSV and identify the name and company columns.
- Add
First nameandCompany cleancolumns. Never overwrite the originals. - Apply the first name rules, then the company rules, then the caps policy.
- Verify any unfamiliar all-caps names (see the caps policy).
- Print the diff and run the say-aloud test before writing the file.
First names
- Strip emoji and symbols, then anything after a comma (credentials: "Priya Shah, CPMM" becomes Priya).
- Drop honorifics (Dr, Mr, Mrs, Ms, Prof): "Dr Tom Hale" becomes Tom.
- Take the first token. If it is a bare initial, take the next token: "J Arun Mehta" becomes Arun.
- ALL-CAPS names get sentence case ("OKAFOR" becomes Okafor), but short initialism names stay ("MJ").
- If the first name is still unusable (a company name, a single letter, or empty), leave it blank and flag the row. Never guess.
Company names
- Strip emoji, ® and ™.
- Drop trailing parentheticals and taglines: "Brightloop (brightloop.io)" becomes Brightloop; "Fleetwise - Logistics Software" becomes Fleetwise; "Castly.io: Live Shopping Platform" becomes Castly.io. Exception: "(previously X)" – drop the bracket and keep the current name ("paydo (previously QuickPay)" becomes paydo).
- Strip legal suffixes, repeatedly if stacked: Inc, Inc., LLC, Ltd, Limited, PLC, LLP, GmbH, GmbH & Co. KG, Pte Ltd, Sdn Bhd, AG, Corp, Co. "Hartmann Tierfutter GmbH & Co. KG" becomes Hartmann Tierfutter.
- The say-aloud test decides length. The merge field holds the name a person would say across a table, not the registered name: Clearpath, not Clearpath Technologies; Easy Move, not Easy Move Removals & Storage. Drop generic trailing descriptors (Technologies, Software, Solutions, AI) when the remaining stem is distinctive. Keep them when the stem becomes ambiguous (a three-letter stem that matches a famous bank or brand) or when it is how people say the name (Ada Health, Street Soccer USA).
- Never use "your company" instead of a name. It is the biggest template tell. For a genuinely unsayable name, rephrase the template around "your team".
- Never "correct" a brand that styles itself lowercase. If the source is lowercase and the brand writes itself that way, trust it.
The caps policy
ALL CAPS is banned in merge fields unless one of these holds:
- True acronym (the letters stand for something), and always AI, UK, USA, and TM.
- Verified brand styling: the company writes itself in caps everywhere. Its website header, LinkedIn page name, and logo agree.
When an all-caps name is not on the caps-OK list and is not obviously an acronym, check before deciding. Fetch the company site or LinkedIn page and see how it writes its own name. One check per name. Add verified names to caps-ok.txt so the next run skips the check.
If you can't verify it, use sentence case. "Quick question about Northwind" reads fine. "NORTHWIND" mid-sentence reads like shouting.
Watch for casing traps
Python's str.capitalize() lowercases everything after the first character. It turns "AI" into "Ai", "TM" into "Tm", and "1VALET" into "1valet" (digit first). Title-case word by word, apply the caps-OK list afterwards, and read the diff before writing.
Output format
- The same CSV with two new columns:
First nameandCompany clean. - A short summary: rows changed, rows flagged for review (with the reason), and any names added to
caps-ok.txt.
Quality checklist
- Original columns untouched.
- No emoji, credentials, honorifics, or legal suffixes left.
- No ALL CAPS unless it is an acronym or verified brand styling.
- No "Ai", "Tm", or other casing-trap damage.
- Lowercase brands left lowercase.
- Three cleaned companies read aloud inside "quick question about {company}" sound like a person talking, not a legal filing or a shout.
- Blank or doubtful first names flagged, not guessed.
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
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.

