brand-naming
Skill2 starsChanged 2 months agoMITView on GitHub
Develop and evaluate names for how they behave in the real world — in speech, in memory, in spelling, in search, in sales calls, across languages, and across future products. Use when naming or renaming a company, product, or feature, when a shortlist needs evaluation, or when a favored name needs stress-testing before legal spend. Produces a naming report with behavioral tests, a defended recommendation, and an explicit register of checks that still require professional clearance.
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
12
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
- Distinctive: line 10
Use when a name must be created, chosen, or defended.
- Distinctive: line 13
Do not use it as a substitute for trademark, linguistic, or regulatory clearance.
- Distinctive: line 24
Ask the user for the markets and the product roadmap explicitly.
- Distinctive: line 29
Create names that work in mouths, in messages, in interfaces, in conversation, in search boxes, in sales calls, and in a product …
- Distinctive: line 44
Cull for obvious collisions and structural weakness: before investing attention.
- Distinctive: line 53
Run these on every finalist.
- Distinctive: line 63
Product extension: Add three plausible future products.
- Distinctive: line 78
Test the name without its backstory.
- Distinctive: line 110
Run at least one blind spoken test and one written recall test with people outside the project.
- Distinctive: line 111
Search each finalist in the real markets and channels the brand will use, and record what a customer would actually find.
- Distinctive: line 113
Read the risk register back and confirm every unverified claim is labeled as unverified with a named owner for the check.
- Distinctive: line 117
Fresh-eyes pass: Read the output as someone who must act on it and was not in the process.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
Brand Naming
When to use this
Use when a name must be created, chosen, or defended. Use before committing to trademark spend, so that legal effort goes toward candidates that survive behavioral testing.
Do not use it as a substitute for trademark, linguistic, or regulatory clearance. This skill produces creative screening and behavioral evidence. It does not produce clearance, and saying otherwise exposes the client to real cost.
Inputs
The chosen territory and the position it expresses. Also: the markets and languages the name must work in, the product architecture it must extend across, the audiences who will say it aloud, existing names in the portfolio it must sit beside, and any constraints already known — established marks, rejected directions, regulatory limits.
Ask the user for the markets and the product roadmap explicitly. A name evaluated for one market and one product is not evaluated.
Mission
Create names that work in mouths, in messages, in interfaces, in conversation, in search boxes, in sales calls, and in a product architecture that does not exist yet.
The best name is not the one with the best origin story. It is the one whose real-world behavior supports the strategy when nobody is there to explain it.
Method
- Write the naming brief. Strategic role, audience, markets, tone, expansion needs, constraints. Establish what the name has to do before generating anything.
- Define naming territories by mechanism, not by word list: descriptive, suggestive, metaphorical, invented, compound, symbolic, vernacular, technical, or culturally grounded. Different mechanisms carry different risks and different ceilings.
- Generate broadly within each territory. Volume here is legitimate; it is cheap and the yield rate is genuinely low.
- Cull for obvious collisions and structural weakness before investing attention.
- Say them aloud. In sentences. On a phone call. Left on a voicemail. Names fail in speech far more often than on a page, and speech is where most of them first travel.
- Run the behavioral tests in the section below.
- Shortlist with reasoning, and record what each finalist risks.
- Register the required professional checks and route them to the right authority.
Behavioral tests
Run these on every finalist. They are the evidence; everything else is opinion.
- First-hearing recall. Say it once in a sentence. Ask for it back an hour later.
- Spelling from sound. Say it. Ask someone to type it. Count the variants you get.
- Search from memory. Would someone who heard it once find the company? Search it and see what they would land on instead.
- Descriptor pairing. Does it survive next to the category word without becoming a sentence?
- Sentence usage. Can a customer use it as a verb, a subject, an object? Does it sound natural in a complaint as well as in a compliment?
- Social introduction. Would someone say it in a meeting without flinching or explaining it?
- Product extension. Add three plausible future products. Does the architecture hold?
- Language and cultural screen. In every target market, by someone who speaks the language. Your own reading of a language you do not speak is not a screen.
Strong versus merely clever
| Merely clever | Strong |
| Delights the naming team | Survives being said by a stranger on a bad phone line |
| Needs its origin story | Works before anyone hears the story, and better after |
| Distinctive on a slide | Distinctive in a search result page full of competitors |
| One perfect fit for today's product | Holds when the company adds two products and a market |
| "Available domain" treated as clearance | Legal, linguistic, and market checks named and routed |
| Rejected for feeling unfamiliar | Unfamiliarity separated from weakness; most strong names felt odd first |
Test the name without its backstory. If it collapses, you have a story, not a name.
Failure modes
- Presenting availability, clearance, or safety as established when nothing was checked.
- Rejecting a name because it feels unfamiliar. Unfamiliar is what a new name is.
- Falling for the name that reads beautifully but cannot be spelled from hearing.
- Ignoring the second and third products the company will ship.
- Scoring candidates numerically and choosing the highest total, which reliably selects the inoffensive middle.
- Screening a language you do not speak.
- Letting the founder's favorite skip the behavioral tests.
Never claim without evidence
Never state that a name is trademark-available, legally clear, culturally safe, linguistically inert, or unregistered in any market. You have not checked, and these are the claims with direct financial and legal consequence.
Where a check has been run — a domain lookup, a search of a public trademark register, a native speaker's read — record exactly what was checked, in which jurisdiction or language, on what date, and by whom. A public register search is a screen, not an opinion on registrability.
Route trademark clearance to counsel, linguistic screening to native speakers in-market, and regulatory naming constraints to whoever governs the category.
Output
Produce naming-report.md using the structure in references/naming-report.md.
Verification
- Run at least one blind spoken test and one written recall test with people outside the project.
- Search each finalist in the real markets and channels the brand will use, and record what a customer would actually find.
- Read the risk register back and confirm every unverified claim is labeled as unverified with a named owner for the check.
- Counterfactual pass. For each recommendation: if it were removed, what meaningful outcome becomes less likely? No credible answer means cut it, downgrade it, or reframe it.
- Fresh-eyes pass. Read the output as someone who must act on it and was not in the process. Cut process debris, duplicated findings, unearned certainty, and any sentence that impresses without changing a decision.
Complete when
The shortlist contains genuinely different mechanisms, each finalist has behavioral evidence rather than advocacy, and every unresolved legal, linguistic, or market risk is visible with an owner attached.
Handoff
Verbal Identity inherits the name's rhythm, register, and the sentences it lives inside — a name that resists certain constructions constrains the voice, and that constraint should be recorded here. Identity System inherits its length, letterforms, and lockup demands. Brand Ship will check that the professional clearances registered here were actually completed before launch, and will block on the ones that were not.
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- aryankeluskar/skills★ 1same name
- mehtab78/skills★ 1same name
- productionx-in/Core-Skills★ 1same name
- rolandtolnay/llm-toolkit★ 1same name
- SkillMedev/brand-visual-identity★ 1same name
- sonwr/mcp-domain-radar★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- brand-architectSkill
- brand-criticSkill
- brand-governanceSkill
- brand-intelligenceSkill
- brand-reviewSkill
- brand-shipSkill
- brand-strategySkill
- brand-worldbuildingSkill
- identity-systemSkill
- positioning-forgeSkill
- verbal-identitySkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

