Agent skill

Playbook Name To Other Prospects

by growthenginenowoslawski in growthenginenowoslawski/coldoutboundskills

Names 2 other right-fit people at the prospect's own company so an email can ask "is this you or them?" without ever naming the person being emailed.

MITAuto-check passed

Install Playbook Name To Other Prospects

skills CLI
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .claude/skills/playbook-name-to-other-prospects && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
playbook-name-to-other-prospects
GitHub stars
753
Token cost
~2.7k tokens
SKILL.md length
994 words
Files
3
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

Names 2 other right-fit people at the prospect's own company so an email can ask "is this you or them?" without ever naming the person being emailed.

  • Works in 7 steps: Trigger and scope → Output contract → Source chain (cost-tagged) → …
  • Name two other people at the company
  • SKILL.md covers 1. Trigger and scope, 2. Output contract, 3. Source chain (cost-tagged) and 4. Verification, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Playbook Name To Other Prospects is an agent skill from growthenginenowoslawski/coldoutboundskills. Names 2 other right-fit people at the prospect's own company so an email can ask "is this you or them?" without ever naming the person being emailed. Triggers on "name two other people at the company", "who else works there", "should I be talking to someone else", "colleague name variable", "other prospects line", "wrong person CTA". Outputs otherprospects, a ready-to-drop phrase like "Jeff Barg or Rob Cook".

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `clay-table.md` and `clay-workflow.md`).

The repository describes itself as: Open-source Claude Code skills for cold email and outbound sales. Grade campaigns, export Prospeo searches, scrape Google Maps — all from Claude Code. The licence is MIT.

When your agent uses it

  • Name two other people at the company
  • Who else works there
  • Should I be talking to someone else
  • Colleague name variable

Example prompts

  • “s own company so an email can ask”
  • “without ever naming the person being emailed. Triggers on”
  • “who else works there”
  • “/playbook-name-to-other-prospects”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Trigger and scope
  2. Output contract
  3. Source chain (cost-tagged)
  4. Verification
  5. Clay implementation
  6. Locked prompt
  7. Edge cases and failure modes

What it can do on your machine

Read from SKILL.md and the folder at commit 25c5d85. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Playbook Name To Other Prospects loads about 2.7k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 994 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthenginenowoslawski/coldoutboundskills at commit 25c5d85, republished under its MIT licence (© growthenginenowoslawski). 994 words, ~2,730 tokens.

Download SKILL.mdSave it as .claude/skills/playbook-name-to-other-prospects/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
playbook-name-to-other-prospects
description
Names 2 other right-fit people at the prospect's own company so an email can ask "is this you or them?" without ever naming the person being emailed. Triggers on "name two other people at the company", "who else works there", "should I be talking to someone else", "colleague name variable", "other prospects line", "wrong person CTA". Outputs other_prospects, a ready-to-drop phrase like "Jeff Barg or Rob Cook".

Playbook: Name 2 Other Prospects

All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.

Use when: the email needs a "not sure if this is you" or "who owns this" angle, or any CTA that offers the reader an easy referral instead of a yes or no.

Do not use when: you want the buying committee itself as separate leads. You never email the people named in this variable unless they are separately in the list on their own merits.

One-line output: other_prospects = "Jeff Barg or Rob Cook"

1. Trigger and scope

This produces one variable: the names of up to 2 other people at the same company as the person receiving the email. It exists so a first email can say "if this sits with Jeff Barg or Rob Cook instead, happy to talk to them" — without the reader feeling surveilled and without guessing wrong about who owns the problem.

⛔ The one absolute rule: never name the recipient to themselves

Hey John, should I reach out to John? is the worst possible outcome, and it is the thing this playbook is built to prevent.

No campaign, brief, or operator preference makes it acceptable. It is enforced from the recipient's full name and their profile URL, in a formula, on every row, always.

⚠️ A row without recipient_full_name is not runnable. The script should throw, and the build must not start. Treating a missing name as "nothing to exclude" is how this fails.

A second, softer exclusion

Optionally exclude everyone else from the same company who is also in this campaign — otherwise two colleagues receive emails naming each other. Default it off, turn it on when a campaign has real multi-contact density at one domain, and decide it at setup rather than mid-run.

2. Output contract

Inputs required per row
FieldTypeRequired?
domain (bare, lowercase)stringyes
company_namestringno, improves the web verifier
recipient_linkedin_urlstringyes when known
recipient_full_namestringyes, always. This is the hard exclusion
all_campaign_recipients_at_this_domainstring[]only when same-campaign exclusion is on
persona_titlesstring[]yes — this is the title cascade
Output fields
FieldTypeExampleNull?
other_prospectsstringJeff Barg or Rob Cookyes, ""
other_prospects_countint2no, 0
other_prospect_1_title, _2_titlestringChief Operating Officeryes

Abstain value: "". Never a single name padded to look like two, never a job title standing in for a name.

Copy-fit rules
  • Slots into a sentence like If this sits with {{other_prospects}} instead, happy to talk to them.
  • Two names joined by " or ". One name is fine and reads naturally; the sentence must still work.
  • Real names, correctly capitalized, full last names.
  • Never a title instead of a name. "your VP of Ops" is not this variable.
Downstream gate

If empty, the whole sentence must disappear — not just the variable. Put the referral CTA in its own sentence and use a pre-rendered whole-sentence field, or split the list at upload. Spintax cannot branch on an empty variable.

3. Source chain (cost-tagged)

#SourceCostWhat it does
1A colleagues-by-domain lookupplan creditsreturns people at the domain. Cheapest first pass
2A title-cascade people search on the same domaincredits per companyordered include_title / exclude_title cascade from the campaign's persona list
3The model judgeCHEAPscreens candidates, cleans names, drops bad data
4A still-there web checkFREEconfirms the named people are still at the company

Step 4 is not optional. Provider job titles go stale, and this variable puts a named human being into a stranger's inbox. A wrong name is not a soft miss.

Show full SKILL.md (389 more words)Show less

4. Verification

VERDICT: PASS 7/8.

5. Clay implementation

  • clay-table.md — the column build, including the two exclusion tiers as formulas.
  • clay-workflow.md — the CLI-buildable version.

6. Locked prompt

Params: max_completion_tokens=3000 (never max_tokens on a reasoning model), reasoning_effort="low", never temperature, JSON response format, flex tier for batch.

text
You screen colleague candidates for a cold email variable.

You get a target company and a list of people a data provider says work there. Pick up to 3
who are credible senior colleagues at THAT company, best first, and return their cleaned real names.

Return JSON only, exactly this shape:
{"keep":[{"name":"First Last","title":"..."}],"dropped":[{"name":"...","why":"..."}]}

Keep a person only if ALL of these are true:
- Their job title is at the target company, not a different employer.
- Their headline does not contradict the job title. A headline naming another company or a
  different line of work means the data is wrong. Drop them.
- The title is a real decision maker or senior function owner: owner, founder, chief, vice
  president, head of, director, general manager, partner, principal.
- The title is not support staff: assistant, executive assistant, administrator, office
  manager, coordinator, receptionist, intern, apprentice, student, product owner, scrum.
- The name is a real person name with a first name and a last name.

Freshness rule. Provider job titles go stale. When a candidate has no headline and no other
text tying them to the target company, prefer a candidate whose headline names the target
company. Only fall back to a no-headline candidate when there are fewer than 3 candidates
whose text names the company.

Clean the name before returning it:
- Remove credentials, emoji, pronouns, hashtags, hiring banners, quoted nicknames, and any
  text after a comma, pipe, or bracket.
- Fix ALL CAPS and all lowercase to normal capitalization. Keep accents and hyphens as they are.
- Keep the full last name. Never shorten a two word surname. Drop middle names.
- If only one name token exists, drop the person.

A headline that names a different profession from the job title is a hard drop, even when
the job title looks senior. Self reported founder titles are the most common bad data.

Order the kept people most senior first. Keep at most 3. Never invent a person. If nobody
qualifies, return an empty keep list. No em dashes anywhere in your output.

Example input:
Company: Harbor Freight Robotics (harborfreightrobotics.com)
Candidates:
1. Devon Marsh | title at company: Co-founder | headline: Wedding Photographer and Videographer
2. priya RAMANATHAN, MBA | title at company: Chief Operating Officer | headline: COO at Harbor Freight Robotics
3. Sam Whitfield | title at company: Executive Assistant to the CEO | headline: EA to the CEO
Example output:
{"keep":[{"name":"Priya Ramanathan","title":"Chief Operating Officer"}],"dropped":[{"name":"Devon Marsh","why":"headline is wedding photography, the founder title at this company is not credible"},{"name":"Sam Whitfield","why":"executive assistant is support staff, not a decision maker"}]}

Example input:
Company: Delacroix Dental Group (delacroixdental.com)
Candidates:
1. Ana Lucia Perez Ortiz | title at company: Practice Owner | headline: Owner at Delacroix Dental Group
2. T. | title at company: Director of Operations | headline:
3. Marcus Feld 🚀 | Hiring! | title at company: Head of Patient Experience | headline: Head of Patient Experience at Delacroix Dental Group
4. Robin Vale | title at company: Vice President Supply | headline:
Example output:
{"keep":[{"name":"Ana Lucia Perez Ortiz","title":"Practice Owner"},{"name":"Marcus Feld","title":"Head of Patient Experience"}],"dropped":[{"name":"T.","why":"no usable first and last name"},{"name":"Robin Vale","why":"no headline ties this person to the company and two better candidates exist"}]}

PER-ROW DATA (appended last)
Company: <company name> (<domain>)
Candidates:
<numbered candidate list>

Two things in this prompt are doing more work than they look:

  • The headline-contradiction rule. Self-reported founder titles are the most common bad data in contact databases. A "Co-founder" whose headline says "Wedding Photographer" is a data error, and without this rule it ships as a named human in a stranger's inbox.
  • The dropped array. The model must say why it dropped someone. That costs a handful of tokens and gives you the only cheap way to audit a variable that names real people.

Truncation guard: finish_reason=length means retry, never abstain.

7. Edge cases and failure modes

SymptomCauseFix
The email names its own recipientThe exclusion ran on a name that did not match exactly — a nickname, a middle initial, a maiden nameMatch on normalized name AND profile URL, and normalize hard: lowercase, strip accents and punctuation, compare first+last only. When in doubt, drop the candidate
Two colleagues each receive an email naming the otherSame-campaign exclusion is offTurn it on for campaigns with multi-contact density at one domain
The variable names someone who left last yearProvider titles go staleThe still-there check. Not optional
A "Co-founder" is really a photographerSelf-reported titlesThe headline-contradiction rule
An executive assistant gets namedSenior-sounding proximity to the CEOThe support-staff exclusion list
The name renders as PRIYA RAMANATHAN, MBA 🚀Raw provider strings are not copyThe cleaning rules. See also playbook-first-name-cleaning
Only one candidate qualifiesCommon at small companiesOne name is a fine answer. Make sure the sentence reads with one
The sentence renders with a dangling "or"The copy assumed two namesBuild the joined phrase in code, not in the template
Empty variable leaves a broken sentenceSpintax cannot branch on emptinessPre-render the whole sentence, or split the list at upload
Hard rules
  • Never name the recipient to themselves. Enforced on every row, always.
  • Never email the people named in this variable unless they are in the list on their own merits.
  • Never substitute a title for a name.
  • A row with no recipient name is not runnable.

© growthenginenowoslawski, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/playbooks/playbook-name-to-other-prospects of growthenginenowoslawski/coldoutboundskills.

  • SKILL.md
  • clay-table.md
  • clay-workflow.md

Open the folder on GitHubat commit 25c5d85

Compare with similar skills

Playbook Name To Other Prospects next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Playbook Name To Other Prospects compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Playbook Name To Other Prospects this skillgrowthenginenowoslawski/coldoutboundskills753—~2.7kAutomated safety check: PassMIT
Business Name Fitalirezarezvani/claude-skills28k—~2.8kAutomated safety check: PassMIT
Prospectingcoreyhaines31/marketingskills54k—~5kAutomated safety check: PassMIT
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Naming Conventionsthedaviddias/Front-End-Checklist74k—~481Automated safety check: PassMIT
Button Namethedaviddias/Front-End-Checklist74k—~488Automated safety check: PassMIT

Similar skills

  • Business Name Fit

    alirezarezvani/claude-skills

    Suggest, pick, or vet a business, startup, or product name that stays true to the founder's cultural origin while working professionally in the markets they want to sell into.

    28k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Prospecting

    coreyhaines31/marketingskills

    When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.

    54k GitHub stars~5k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Naming Conventions

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use consistent CSS naming conventions.

    74k GitHub stars~481 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Button Name

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for buttons.

    74k GitHub stars~488 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Select Name

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for select elements.

    74k GitHub stars~451 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed

More from growthenginenowoslawski/coldoutboundskills

All 49 skills in this repo
  • Email Deliverability Audit

    growthenginenowoslawski/coldoutboundskills

    Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.

    753 GitHub stars~3.4k tokensUpdated 5 days ago
    Auto-check passed
  • Icp Onboarding

    growthenginenowoslawski/coldoutboundskills

    Conversational intake for cold email campaigns. An agent skill from growthenginenowoslawski/coldoutboundskills.

    753 GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed
  • List Builder

    growthenginenowoslawski/coldoutboundskills

    META skill — build the largest possible qualified lead list for any request, end to end.

    753 GitHub stars~4.7k tokensUpdated 5 days ago
    Auto-check: notes
  • Auto Research Public

    growthenginenowoslawski/coldoutboundskills

    Autonomous cold email campaign launcher. An agent skill from growthenginenowoslawski/coldoutboundskills.

    753 GitHub stars~2.9k tokensUpdated 5 days ago
    Auto-check passed
  • Blitz List Builder

    growthenginenowoslawski/coldoutboundskills

    Use the Blitz API to find decision-makers at specific companies when you already have a list of company domains.

    753 GitHub stars~2k tokensUpdated 5 days ago
    Auto-check passed
  • Deliverability Test Public

    growthenginenowoslawski/coldoutboundskills

    Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.

    753 GitHub stars~1k tokensUpdated 5 days ago
    Auto-check passed

Questions about Playbook Name To Other Prospects

What does Playbook Name To Other Prospects do?

Names 2 other right-fit people at the prospect's own company so an email can ask "is this you or them?" without ever naming the person being emailed. Playbook Name To Other Prospects is an agent skill from growthenginenowoslawski/coldoutboundskills." without ever naming the person being emailed.

When should I use Playbook Name To Other Prospects?

Playbook Name To Other Prospects fits situations like: name two other people at the company; who else works there; should I be talking to someone else; colleague name variable.

How do I install Playbook Name To Other Prospects in Claude Code?

Run `npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a claude-code`. Or copy the skill folder (skills/playbooks/playbook-name-to-other-prospects in growthenginenowoslawski/coldoutboundskills) into .claude/skills/playbook-name-to-other-prospects in your project. Claude Code loads it when a task matches its description.

How do I install Playbook Name To Other Prospects in Codex?

Run `npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a codex`. Or copy the skill folder (skills/playbooks/playbook-name-to-other-prospects in growthenginenowoslawski/coldoutboundskills) into .agents/skills/playbook-name-to-other-prospects in your project. Codex loads it when a task matches its description.

Can I use Playbook Name To Other Prospects in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/playbook-name-to-other-prospects, .gemini/skills/playbook-name-to-other-prospects, .github/skills/playbook-name-to-other-prospects and .opencode/skills/playbook-name-to-other-prospects in your project.

What does Playbook Name To Other Prospects need to run?

SKILL.md names no scripts, command-line tools or credentials: Playbook Name To Other Prospects is instructions for the agent only.

Does Playbook Name To Other Prospects access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Playbook Name To Other Prospects safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Playbook Name To Other Prospects use?

Playbook Name To Other Prospects is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Playbook Name To Other Prospects use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Playbook Name To Other Prospects?

Skills that share tags, products or a category with Playbook Name To Other Prospects: Business Name Fit (alirezarezvani/claude-skills, 28k stars), Prospecting (coreyhaines31/marketingskills, 54k stars), Git Branch Naming (makeplane/plane, 61k stars) and Naming Conventions (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Playbook Name To Other Prospects?

growthenginenowoslawski (a GitHub user) maintains it in growthenginenowoslawski/coldoutboundskills, which has 753 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.

Source: growthenginenowoslawski/coldoutboundskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.