Skip to main content
skill Claude Code

business-name-fit — Claude Code skill: what it does, how to install

Vets or suggests business names that reflect a founder's cultural origin and work well in target markets abroad. Useful before launching a brand.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add alirezarezvani/claude-skills
/plugin install marketing-skills@claude-code-skills
Open on GitHub

What business-name-fit does

The skill evaluates company, startup, or product names across target markets. A word that sounds standard at home can sound comical or awkward elsewhere. For instance, the Persian name Anali or the Swedish word framåt read quite differently to English speakers. The skill detects unintended slang, pronunciation traps, and spelling hurdles like stripped accents.

The workflow starts with a brief: the founder's background, target geographies, and industry tone. Next, it tests each name against the WIPO trademark scale to reject generic terms. It also checks phonetic weight and cultural fit. If certainty about foreign slang is lacking, the skill advises asking a native speaker before committing.

Install this if you want an authentic name that avoids cultural embarrassment in international sales.

What it helps with

  • vet candidate brand names for unintended meanings and slang abroad
  • assess trademark distinctiveness using the WIPO scale per market
  • generate name ideas rooted in the founder's language and cultural values
  • spot pronunciation or spelling hurdles caused by accents and unusual letter combos

Example prompts for the agent

  • /business-name-fit
  • Check if the name Anali works for an English-speaking market
  • Suggest names for a cybersecurity startup based on Swedish roots for the EU market

How to install business-name-fit

1Plugin marketplace

/plugin marketplace add alirezarezvani/claude-skills
/plugin install marketing-skills@claude-code-skills

This installs the whole marketing-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add alirezarezvani/claude-skills --skill business-name-fit -a claude-code

3Manually: put the files in place

~/.claude/skills/business-name-fit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/business-name-fit/

From the same set349

The whole set →
engineering-skills Alireza Rezvani An engineering skill index for Claude Code that helps you select one specialist SKILL.md for the task at hand. It covers architecture, testing, DevOps, and data work. Claude Code 2,387installs finance-skills Alireza Rezvani Routes ambiguous finance prompts to the right bundled skill: financial-analyst, saas-metrics-coach, or month-end-close. Claude Code 2,312installs marketing-skills Alireza Rezvani A directory and router for marketing skills in Claude Code. It picks the right specialist skill for SEO, content, CRO, channels, and related tasks. Claude Code 2,264installs business-growth-skills Alireza Rezvani Routes growth and revenue prompts to the right specialized skill across customer success, sales engineering, RevOps, and proposals in Claude Code. Claude Code 2,189installs engineering-advanced-skills Alireza Rezvani An index of 37 engineering skills for architecture, automation, reliability, and platform work. Use it when a project needs task-specific engineering workflows. Claude Code 2,019installs product-skills Alireza Rezvani Product work orchestrator for Claude Code. Routes queries across 16 domain lanes and validates discovery trees with deterministic scripts. Claude Code 1,994installs pm-skills Alireza Rezvani Routes project-delivery requests across 8 PM sub-skills for Jira, Confluence, sprints, reporting, and team communication. Useful for controlled delivery work. Claude Code 1,975installs senior-backend Alireza Rezvani Scaffolds backend APIs, detects database bottlenecks, and runs load tests. Useful when designing Express routes, optimizing PostgreSQL, or preparing for production. Claude Code 1,674installs

Similar

d365-solution-blueprint official github Conducts a structured architect interview to author a Dynamics 365 F&SCM Solution Blueprint from scratch. Useful when starting an enterprise ERP project and defining key design decisions. GitHub Copilot 13installs stripe-best-practices official Stripe Integration guide for Stripe in Codex: covers Checkout Sessions, Connect Accounts v2, tax setup, and restricted API keys. CX Codex GP ChatGPT 36installs stripe-best-practices official OpenAI This skill guides Stripe API choices for payments, subscriptions, marketplaces, and financial accounts. Use it when building or reviewing a Stripe integration. CX Codex GP ChatGPT 36installs upgrade-stripe official Stripe Step-by-step guidance for upgrading Stripe API versions, server-side libraries, Stripe.js, and mobile SDKs. CX Codex GP ChatGPT 13installs payments official Vercel Labs Guidance for adding Stripe checkout, subscriptions, and webhook handling to Vercel apps. Use it when building payment flows. CX Codex GP ChatGPT 5installs churn-prevention coreyhaines31 A Claude Code skill for subscription churn: an exit survey at cancellation, an offer matched to the stated reason, and recovery of failed payments. Claude Code CX Codex Cursor +1 120,600installs revops coreyhaines31 This skill helps design RevOps workflows for lead stages, scoring, routing, and marketing-to-sales handoffs. Use it when CRM processes need clear rules. Claude Code CX Codex Cursor +1 113,000installs community-marketing coreyhaines31 Builds and grows branded communities on Discord or Slack to drive product retention and turn users into advocates. Claude Code CX Codex Cursor +1 89,100installs

Questions about business-name-fit

How to install business-name-fit in Claude Code?

Run /plugin marketplace add alirezarezvani/claude-skills or use npx skills add alirezarezvani/claude-skills --skill business-name-fit -a claude-code.

What does business-name-fit do?

It tests whether a business name sounds natural, respectable, and easy to pronounce across target markets. It can also generate names based on the founder's home language.

Why does it classify names on the WIPO scale?

Generic and descriptive names are legally weak and difficult to protect. The skill tests distinctiveness separately for each market to prevent unregistrable picks.

Source text

SKILL.md · MIT
---
name: business-name-fit
description: 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. Use when someone is naming a company, brand, or product and cares about how it lands across languages and regions — for example a name that sounds right at home but might read oddly to English speakers, or an authentic name they want to check before committing. Trigger this for any request about choosing a business name, checking if a name "works" abroad, spotting bad meanings in other languages, or making a name sound trustworthy in a specific market — even if the person doesn't say the word "skill".
---

# Business Name Fit

## Overview

Help founders choose or check a business/brand/product name that is authentic to their origin **and** lands well in the market where they'll operate.

The core value is catching the mismatch between the two: a name can be perfectly good in its home language yet confusing, funny, or off-putting elsewhere. Examples:
- The Persian name "Anali" is fine in Iran but reads oddly to English speakers.
- The Swedish word "framåt" ("forward") can sound like "frame" to an English ear.

This skill both **suggests new names** and **checks names the person already has**.

## Step 1 — Gather the essentials

If the skill is invoked with nothing else to go on (e.g. just `/business-name-fit`, no name, no context), don't launch into the full list below. Ask one question first, and wait for the answer:

> Are you looking to **find a new name**, or **check one you already have**?

Once that's answered, ask only for what's still missing from the conversation. Keep it to a couple of short questions.

1. **Origin** — the founder's culture/language or the company's home base (e.g. Persian/Iran, Swedish/Sweden, Mandarin/China).
2. **Target market(s)** — where the business will operate (e.g. international/English-speaking, EU, China, Arabic-speaking countries). There can be more than one.
3. **Business area** — the industry or field, because tone matters (a law firm and a candy brand need different feels).
4. **Mode** — do they want new name ideas, a check of names they already have, or both? (Already answered above if the skill opened with the find-or-check question.)
5. **Existing names** — if they're checking, collect the candidates.
6. **Desired feel** (optional) — modern, traditional, playful, premium, etc.

## Step 2 — Run the fit checks (the heart of the skill)

Run every candidate name through these checks, once per target market:

- **Meaning** — Does it mean something unintended, negative, funny, or taboo in the market's language(s)? Include slang.
- **Look-alike** — Does it resemble an existing word that changes the impression (e.g. framåt → "frame")?
- **Pronunciation** — Can people in the target market say it easily, or does it get mangled?
- **Spelling** — After hearing it, can they spell it? Watch for tricky letter combos and origin-language diacritics (å, ø, ç, etc.) that won't survive in English.
- **Distinctiveness** — Where does it sit on the WIPO scale: generic, descriptive, deceptive, suggestive, arbitrary, or coined? Generic and descriptive names are weak and often cannot be registered at all — say so plainly, because a founder can build a business on such a name and still never own it. Reject deceptive names outright. Judge this **separately per market**: a word that is plainly descriptive at home may be arbitrary and strong abroad, and the reverse.
- **Sound** — Say it aloud. Does its sound-feel match the field? Front vowels (ee, i) read light and quick; back vowels (o, u) solid and heavy; hard plosives (p, t, k, b, d, g) sharp and firm; soft fricatives and nasals (s, f, m, l, n) smooth and gentle. Note honestly that these associations come mainly from English-language research and do not transfer automatically to other languages.
- **Tone fit** — Does it feel trustworthy and appropriate for that industry and that market?
- **Origin authenticity** — Does it still genuinely reflect the founder's origin, or has it been flattened into something generic?

Also weigh the classic evaluation criteria: relevance to the category, connotations, overall liking, ease of recognition, distinctiveness, and ease of recall.

`references/naming-research.md` holds the sources and reasoning behind these checks — read it when a founder asks *why*, or when a name category or sound effect needs explaining in depth. `references/worked-examples.md` shows three full cases end to end (a name fixed, a name approved, a name rejected) — read it when you need a model for how a finished analysis should read.

Be honest about confidence. If unsure whether a name carries an odd meaning or slang sense in a language, say so plainly and recommend a native-speaker check before the founder commits.

## Step 3 — If suggesting new names

Every suggestion must satisfy **three constraints at once**: rooted in the origin, professional for the industry, and clean in the target market. A name that meets only two of the three is not a valid suggestion — drop it and find another.

**3a. Write the naming brief first — before generating anything.**
Founders (and firms generally) tend to work out what they actually want from a name only *after* they have fallen for a candidate, which corrupts the judgement. So write it down first, in one or two lines: what the business promises its customers, what feeling that promise needs, and what the name must therefore do. Then pick origin words that carry that meaning. Examples of the logic:
- Childcare → warmth, safety, gentleness. Not power or speed.
- Consultancy, law, finance → competence, stability, discretion. Not cuteness.
- Art authentication, certification, security → authenticity, precision, trust.
- Health → care, cleanliness, calm.
- Technology → clarity, motion, forwardness.

**3b. Draw the raw material from the origin language.**
- Real words, roots, names, places, or concepts from the origin language.
- Meaningful cultural ideas (nature, values, mythology) shaped into short, sayable forms.
- Light blends or coined words that keep an origin flavor.

Prefer a word whose **literal meaning is itself the value proposition** — a Persian word meaning "authentic" for an authentication company beats a merely beautiful word. But stop short of plainly describing the product: aim for names that *hint* (suggestive), use an unrelated real word (arbitrary), or are invented (coined). These are both more memorable and far more likely to be registrable than a descriptive name.

**3c. Apply the professional-quality bar.** Reject a candidate if it:
- is hard to say or spell in the target market after one hearing;
- carries a tone that clashes with the field (playful for a law firm, clinical for a toy brand);
- needs an accent or non-Latin character to read correctly;
- is longer than about three syllables, or looks like a random invented string;
- sounds like a personal first name when the business needs institutional credibility.

**3d. Sanity-check against the market's naming conventions.** Names carry different weight by region — what reads as confident in the Gulf may read as overblown in the Nordics. Make sure the name would not look out of place next to established firms in that field and that market.

**3e. Run every surviving candidate through the Step 2 checks**, then hand off to Step 4 to present them.

Offer 3–5 strong candidates rather than a long weak list.

## Step 4 — Present the results

Default to a **compact table, every time** — checking existing names and presenting new suggestions both work this way. The whole answer should be readable at a glance: no scrolling through prose to find the verdict.

- **Checking names** — one row per name (one row per name × market if there's more than one market). Columns for whatever checks actually mattered for that name — not all eight every time. Cells hold a symbol plus 2–4 words (e.g. `❌ reads as slur (EN)`, `⚠️ crowded namespace`), never a sentence.
- **Suggesting names** — one row per candidate: origin meaning, target-market read, verdict. Same rule — phrases in cells, not paragraphs.

After the table, add at most one short line naming the 2–3 strongest options. Never present a single favourite as if it were the only option.

Stop there. Do **not** add check-by-check breakdowns, reasoning paragraphs, or a written verdict for each name unless the person asks for more — "why", "explain", "tell me more about X", "detailed report" — in which case expand only the part they asked about, still as briefly as clarity allows.

## Step 5 — Hand over the verification steps

Close every session with a short list of what still has to be checked — one line each, this skill cannot confirm any of it:

- **Trademark** — search the register in each target market before spending on the name (a formal step, not an afterthought).
- **Domain & handles** — availability where the founder will actually use them.
- **Business registry** — the company register in the home country.
- **Native-speaker gut check** — a real speaker in each target market, for the finalists.

Expand any of these only if asked.

## Anti-Patterns

- **Don't split the checks by feel alone.** A name can pass the sound check and fail the look-alike or spelling check (or the reverse) — always run every check, don't stop once one check feels conclusive. See Scenario A in `references/worked-examples.md`.
- **Don't call a name "safe" on meaning alone.** Distinctiveness (the WIPO scale) is a separate, legal question. A name can be linguistically clean and still be generic or descriptive — weak and hard to register — or the reverse.
- **Don't treat English/Western sound-symbolism findings as universal.** They come mainly from English-language research (Pogacar et al.) and do not automatically transfer to Persian, Arabic, Mandarin, or any other target market — say so when it matters.
- **Don't present one favourite.** Offer 3–5 candidates; a founder evaluating only one option isn't evaluating.
- **Don't skip the find-or-check question when the skill opens with no context.** Guessing origin, market, or industry produces suggestions that don't fit.
- **Don't let this skill's output stand in for verification.** It cannot check trademark, domain, or business-registry availability — always close with Step 5.
- **Don't write a check-by-check essay by default.** The default output is a compact table (Step 4); expand only when asked.

## Cross-References

- **brand-guidelines** (`marketing-skill/skills/brand-guidelines`) — use after a name is chosen, to build the visual and verbal identity system around it.
- **copywriting** (`marketing-skill/skills/copywriting`) — use once the name is locked, for tagline and messaging work that needs to match the name's tone.
- **marketing-context** (`marketing-skill/skills/marketing-context`) — load first if available; ICP and positioning context should inform which candidate names fit best.

© Alireza Rezvani · MIT · alirezarezvani/claude-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor