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.
Agent skill
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.
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .claude/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospectsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .agents/skills/playbook-name-to-other-prospects && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .agents/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .cursor/skills/playbook-name-to-other-prospects && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .cursor/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/growthenginenowoslawski/coldoutboundskills.git --path skills/playbooks/playbook-name-to-other-prospects--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .gemini/skills/playbook-name-to-other-prospects && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .gemini/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospectsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .github/skills/playbook-name-to-other-prospects && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .github/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospects -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install growthenginenowoslawski/coldoutboundskills playbook-name-to-other-prospects --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/playbooks/playbook-name-to-other-prospects .opencode/skills/playbook-name-to-other-prospects && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "playbook-name-to-other-prospects" agent skill from https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-name-to-other-prospects into .opencode/skills/playbook-name-to-other-prospects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playbook-name-to-other-prospects", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
playbook-name-to-other-prospectsNames 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. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 25c5d85. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from growthenginenowoslawski/coldoutboundskills at commit 25c5d85, republished under its MIT licence (© growthenginenowoslawski). 994 words, ~2,730 tokens.
.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.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"
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.
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.
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.
| Field | Type | Required? |
|---|---|---|
domain (bare, lowercase) | string | yes |
company_name | string | no, improves the web verifier |
recipient_linkedin_url | string | yes when known |
recipient_full_name | string | yes, always. This is the hard exclusion |
all_campaign_recipients_at_this_domain | string[] | only when same-campaign exclusion is on |
persona_titles | string[] | yes — this is the title cascade |
| Field | Type | Example | Null? |
|---|---|---|---|
other_prospects | string | Jeff Barg or Rob Cook | yes, "" |
other_prospects_count | int | 2 | no, 0 |
other_prospect_1_title, _2_title | string | Chief Operating Officer | yes |
Abstain value: "". Never a single name padded to look like two, never a job title standing in
for a name.
If this sits with {{other_prospects}} instead, happy to talk to them.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.
| # | Source | Cost | What it does |
|---|---|---|---|
| 1 | A colleagues-by-domain lookup | plan credits | returns people at the domain. Cheapest first pass |
| 2 | A title-cascade people search on the same domain | credits per company | ordered include_title / exclude_title cascade from the campaign's persona list |
| 3 | The model judge | CHEAP | screens candidates, cleans names, drops bad data |
| 4 | A still-there web check | FREE | confirms 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.
VERDICT: PASS 7/8.
clay-table.md — the column build, including the two exclusion tiers as formulas.clay-workflow.md — the CLI-buildable version.Params: max_completion_tokens=3000 (never max_tokens on a reasoning model),
reasoning_effort="low", never temperature, JSON response format, flex tier for batch.
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:
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.
| Symptom | Cause | Fix |
|---|---|---|
| The email names its own recipient | The exclusion ran on a name that did not match exactly — a nickname, a middle initial, a maiden name | Match 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 other | Same-campaign exclusion is off | Turn it on for campaigns with multi-contact density at one domain |
| The variable names someone who left last year | Provider titles go stale | The still-there check. Not optional |
| A "Co-founder" is really a photographer | Self-reported titles | The headline-contradiction rule |
| An executive assistant gets named | Senior-sounding proximity to the CEO | The support-staff exclusion list |
The name renders as PRIYA RAMANATHAN, MBA 🚀 | Raw provider strings are not copy | The cleaning rules. See also playbook-first-name-cleaning |
| Only one candidate qualifies | Common at small companies | One name is a fine answer. Make sure the sentence reads with one |
| The sentence renders with a dangling "or" | The copy assumed two names | Build the joined phrase in code, not in the template |
| Empty variable leaves a broken sentence | Spintax cannot branch on emptiness | Pre-render the whole sentence, or split the list at upload |
© growthenginenowoslawski, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in skills/playbooks/playbook-name-to-other-prospects of growthenginenowoslawski/coldoutboundskills.
Open the folder on GitHubat commit 25c5d85
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Playbook Name To Other Prospects this skillgrowthenginenowoslawski/coldoutboundskills | 753 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Business Name Fitalirezarezvani/claude-skills | 28k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~5k | Automated safety check: Pass | MIT | |
| Git Branch Namingmakeplane/plane | 61k | — | ~594 | Automated safety check: Pass | AGPL-3.0 | |
| Naming Conventionsthedaviddias/Front-End-Checklist | 74k | — | ~481 | Automated safety check: Pass | MIT | |
| Button Namethedaviddias/Front-End-Checklist | 74k | — | ~488 | Automated safety check: Pass | MIT |
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.
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.
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.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use consistent CSS naming conventions.
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.
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.
growthenginenowoslawski/coldoutboundskills
Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.
growthenginenowoslawski/coldoutboundskills
Conversational intake for cold email campaigns. An agent skill from growthenginenowoslawski/coldoutboundskills.
growthenginenowoslawski/coldoutboundskills
META skill — build the largest possible qualified lead list for any request, end to end.
growthenginenowoslawski/coldoutboundskills
Autonomous cold email campaign launcher. An agent skill from growthenginenowoslawski/coldoutboundskills.
growthenginenowoslawski/coldoutboundskills
Use the Blitz API to find decision-makers at specific companies when you already have a list of company domains.
growthenginenowoslawski/coldoutboundskills
Compare reply rates, bounce rates, and positive reply rates broken down by inbox type (SMTP / Gmail / Outlook) for a Smartlead account.
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Playbook Name To Other Prospects is instructions for the agent only.
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.
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.
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.
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.
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.
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.