agentleFS
aiagentwithdhruvaiagentwithdhruv/skills/casualize-names/SKILL.md

casualize-names

Skill16 starsChanged 9 months agoMITView on GitHub

Convert formal names to casual versions for cold email personalization - first names, company names, and city names. Use when user asks to casualize names, make names friendly, or prepare lead data for emails.

  • Reads credentials

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 10

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Only processes rows with emails

    line 32
  2. Common:

    Use common nicknames: "William" → "Will", "Jennifer" → "Jen"

    line 39
  3. Common:

    Keep original if no common nickname exists

    line 40
  4. Common:

    Remove "The" at beginning

    line 44
  5. Common:

    Remove legal suffixes (LLC, Inc, Corp, Ltd)

    line 45
  6. Common:

    Remove generic words (Realty, Group, Solutions, Services)

    line 46
  7. Common:

    Keep core brand name

    line 47
  8. Common:

    Use "you guys" for overly generic names

    line 48
  9. Common:

    Use local nicknames: "San Francisco" → "SF", "Philadelphia" → "Philly"

    line 55
  10. Common:

    Keep original if no common nickname

    line 56

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

Casualize Names Workflow

Goal

Convert formal names (first names, company names, cities) to casual, friendly versions suitable for cold email copy.

Scripts

  • ./scripts/casualize_batch.py - Main script (all 3 fields at once)
  • ./scripts/casualize_company_names_batch.py - Company names only
  • ./scripts/casualize_first_names_batch.py - First names only
  • ./scripts/casualize_city_names_batch.py - City names only

Quick Start

# Process all three fields at once (recommended, 3x faster)
python3 -u ./scripts/casualize_batch.py "GOOGLE_SHEET_URL"

# Re-process existing (overwrite)
python3 -u ./scripts/casualize_batch.py "GOOGLE_SHEET_URL" --overwrite

How It Works

  1. Processes records in batches of 50
  2. Uses 5 parallel workers
  3. Claude converts all three fields in one API call
  4. Batch updates Google Sheet with results
  5. Only processes rows with emails

Performance: ~35 records/sec (3,000 records ≈ 90 seconds)

Casualization Rules

First Names

  • Use common nicknames: "William" → "Will", "Jennifer" → "Jen"
  • Keep original if no common nickname exists
  • Keep it professional

Company Names

  • Remove "The" at beginning
  • Remove legal suffixes (LLC, Inc, Corp, Ltd)
  • Remove generic words (Realty, Group, Solutions, Services)
  • Keep core brand name
  • Use "you guys" for overly generic names

Examples:

  • "Keller Williams Realty Inc" → "Keller Williams"
  • "The Teal Umbrella Family Dental Healthcare" → "Teal Umbrella"

City Names

  • Use local nicknames: "San Francisco" → "SF", "Philadelphia" → "Philly"
  • Keep original if no common nickname

Output

Creates three new columns:

  • casual_first_name
  • casual_company_name
  • casual_city_name

Environment

ANTHROPIC_API_KEY=your_key

Schema

Inputs

NameTypeRequiredDescription
sheet_urlstringYesGoogle Sheet URL with lead data
overwritebooleanNoRe-process existing casualized names

Outputs

NameTypeDescription
sheet_urlstringSame sheet with casual_first_name, casual_company_name, casual_city_name columns added

Credentials

NameSource
ANTHROPIC_API_KEY.env

Composable With

Skills that chain well with this one: scrape-leads, gmaps-leads, instantly-campaigns

Cost

~35 records/sec, minimal API cost

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.