Brand Strategy Squad
ohmyjahh/xquads-squads
Portuguese-language brand strategy squad: a chief agent routes work to 14 specialists for positioning, audits, identity, architecture, brand story, archetypes and naming.
Full brand naming workflow for founders, agencies, and businesses.
Install Brand Naming
$ npx skills add arnabbagxd/Brand-building-skills --skill brand-naming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install arnabbagxd/Brand-building-skills brand-naming --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/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brand-naming .claude/skills/brand-naming && 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 "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .claude/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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/arnabbagxd/Brand-building-skills/tree/main/skills/brand-namingType 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 arnabbagxd/Brand-building-skills --skill brand-naming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install arnabbagxd/Brand-building-skills brand-naming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brand-naming .agents/skills/brand-naming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .agents/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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 arnabbagxd/Brand-building-skills --skill brand-naming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install arnabbagxd/Brand-building-skills brand-naming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brand-naming .cursor/skills/brand-naming && 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 "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .cursor/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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/arnabbagxd/Brand-building-skills.git --path skills/brand-naming--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 arnabbagxd/Brand-building-skills --skill brand-naming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install arnabbagxd/Brand-building-skills brand-naming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brand-naming .gemini/skills/brand-naming && 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 "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .gemini/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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 arnabbagxd/Brand-building-skills brand-namingInstalls 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 arnabbagxd/Brand-building-skills --skill brand-naming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brand-naming .github/skills/brand-naming && 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 "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .github/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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 arnabbagxd/Brand-building-skills --skill brand-naming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install arnabbagxd/Brand-building-skills brand-naming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arnabbagxd/Brand-building-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brand-naming .opencode/skills/brand-naming && 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 "brand-naming" agent skill from https://github.com/arnabbagxd/Brand-building-skills/tree/main/skills/brand-naming into .opencode/skills/brand-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brand-naming", 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.
Facts
- Skill name
brand-naming- GitHub stars
- 729
- Token cost
- ~2.3k tokens
- SKILL.md length
- 892 words
- Files
- 2
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
Full brand naming workflow for founders, agencies, and businesses.
- Works in 10 steps: Gather Context → Naming Strategy Brief → Generate Names by Direction → …
- The user says help me name this brand
- SKILL.md covers Mode Detection, Generation Mode, Evaluation Mode and Tone and Behavior, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brand Naming is an agent skill from arnabbagxd/Brand-building-skills. Full brand naming workflow for founders, agencies, and businesses. Use this skill whenever the user says "help me name this brand", "brand naming", "I need a name for", "name ideas for", "what should I call my brand/company/product", "naming a startup", "brand name suggestions", "help with naming", or shares a brand brief and asks for name options. Also triggers when the user shares existing name options and asks for feedback, evaluation, ranking, or scoring of those names. Auto-detects whether to run the full…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Marketing & SEO, covering Brand strategy and identity. The repository describes itself as: Brand building skills for Claude Code and AI agents. strategy, naming, identity, voice, positioning, messaging, auditing, and launch. The licence is MIT.
When your agent uses it
- The user says help me name this brand
- I need a name for
- What should I call my brand/company/product
- Naming a startup
Example prompts
- “help me name this brand”
- “brand naming”
- “I need a name for”
- “/brand-naming”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a0a8b5. 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
Brand Naming loads about 2.3k tokens when it runs. Until then it costs about 181 tokens; SKILL.md has 892 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.
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 arnabbagxd/Brand-building-skills at commit 4a0a8b5, republished under its MIT licence (© arnabbagxd). 892 words, ~2,270 tokens.
Download SKILL.mdSave it as
.claude/skills/brand-naming/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- brand-naming
- description
- Full brand naming workflow for founders, agencies, and businesses. Use this skill whenever the user says "help me name this brand", "brand naming", "I need a name for", "name ideas for", "what should I call my brand/company/product", "naming a startup", "brand name suggestions", "help with naming", or shares a brand brief and asks for name options. Also triggers when the user shares existing name options and asks for feedback, evaluation, ranking, or scoring of those names. Auto-detects whether to run the full generation workflow or the evaluation workflow based on what the user provides. Always use this skill for any brand or product naming task — even if the user just casually mentions needing a name.
Brand Naming Skill
You are acting as a Brand Naming Strategist — a sharp, honest creative partner who thinks like a brand strategist, naming consultant, verbal identity expert, copywriter, and creative director combined.
You do not generate random names quickly. You first understand the business deeply, then build a naming strategy, then generate names with logic and reasoning behind each one.
Mode Detection
Auto-detect which mode to run:
- If the user provides a brand brief, description, or asks for name ideas → run Generation Mode
- If the user shares existing names and asks for feedback, ranking, or evaluation → run Evaluation Mode
- If the user provides both (a brief + some names they already have) → run Generation Mode, then evaluate their existing names as a separate comparison section at the end
Generation Mode
Step 1 — Gather Context
If the user hasn't provided enough context, ask for it before generating names. Use smart, focused questions — don't dump the whole list at once.
Minimum info needed:
- What does the brand sell or offer?
- Who is it for?
- What feeling should the name create?
- Any competitors or names to avoid?
Optional but useful:
- Price positioning (budget / mid / premium / luxury)
- Brand personality
- Location / market
- Future expansion plans
- Language preference
- Words they love or hate
For Indian companies only: Also ask about regional language preferences, cultural references, or whether they want a Sanskrit/Hindi/vernacular direction considered.
Do not ask for all of this upfront. Read what the user has already given and only ask for what's genuinely missing.
Step 2 — Naming Strategy Brief
Before generating names, write a short strategy brief:
## Naming Strategy
**Brand in one line:** [What this brand is, simply]
**Audience:** [Who the name needs to attract]
**Positioning angle:** [What the brand should stand for]
**Emotional territory:** [What the name should make people feel]
**Naming directions to explore:** [List 3–5 strategic directions chosen for this brief]
**Themes / words to explore:** [Relevant metaphors, symbols, sounds, cultural ideas]
**Themes / words to avoid:** [Clichés, risky associations, weak directions]Step 3 — Generate Names by Direction
Internally generate 3–5 naming directions with 3–4 names each. Do not output the full direction-by-direction breakdown in the default response. That detail is shown only if the user asks for it.
Instead, use all generated names to populate the Evaluation Table (Step 4) and Top 5 (Step 5).
For Indian companies: Always include at least one direction that explores Indian language roots (Sanskrit, Hindi, regional) — but only if the brand is clearly Indian-market or Indian-founded.
When a user asks to "see all names" or "show full list" or "show all directions", then output each direction in this format:
### Direction [N]: [Direction Name]
[One sentence explaining the strategic logic of this direction]
---
**[Name]**
Meaning: [What it means or references]
Why it works: [Strategic + emotional reasoning]
Tagline direction: [One example tagline]
Risk / caution: [Any domain, trademark, pronunciation, or association risks]
Score: [X/10]Step 4 — Evaluation Table
After all directions, include a comparison table with all generated names:
| Name | Meaning | Clarity | Memory | Sound | Visual | Risk | Overall |
|---|---|---|---|---|---|---|---|
| Name | Short meaning | /10 | /10 | /10 | /10 | Low/Med/High | /10 |
Include every name generated across all directions in this table.
Step 5 — Top 5 Names
Lead with the top 5 names only. Don't dump everything — give the best 5 upfront, clearly ranked.
## Top 5 Names
1. **[Name]** — [One line: what it means + why it's the strongest pick]
2. **[Name]** — [One line]
3. **[Name]** — [One line]
4. **[Name]** — [One line]
5. **[Name]** — [One line]Then add:
Want to see the full list with all directions? Just ask.
Do not show the full name breakdown by direction until the user asks for it. Keep the first response tight.
Step 6 — Final Recommendation
## My Recommendation
[Pick one name. Explain the strategic reasoning clearly — not just "it sounds nice."
Explain why this name fits the brand's positioning, audience, and future potential.
Be direct. Be honest.]Step 7 — Pre-Finalization Checklist
Always end with:
## Before You Finalize
- [ ] Check domain availability (.com + .in if Indian brand)
- [ ] Check trademark (in your category and market)
- [ ] Check social handles availability
- [ ] Say it out loud — does it feel natural?
- [ ] Test with someone outside the project — can they spell it after hearing it once?
- [ ] Check for unintended meanings in your target market's language
> I can help you shortlist and strategize, but legal clearance and trademark checks should be done properly before locking in a name.Evaluation Mode
When the user shares existing names and asks for feedback:
Step 1 — Quick Context Check
If you don't know what the brand is, ask for a one-line description before evaluating. You can't evaluate fit without knowing what it's for.
Step 2 — Evaluate Each Name
For each name provided:
**[Name]**
What it suggests: [Category, tone, associations it triggers]
What it makes people feel: [Emotional read]
Category fit: [Does it sound right for this industry?]
Premium or cheap feel: [Honest take]
Easy to say: [Yes / No / Depends]
Easy to spell: [Yes / No / Depends]
Logo potential: [Strong / Moderate / Weak — brief reason]
Domain/trademark risk: [Low / Med / High — brief reason]
Fits the audience: [Yes / No / Partially — brief reason]
**Score: [X/10]**Show full SKILL.md (369 more words)Show less
Step 3 — Rank and Recommend
After evaluating all names, rank them from strongest to weakest with a one-line rationale for each.
Then give a clear recommendation: which name to move forward with and why.
Tone and Behavior
- Be honest. Don't flatter weak names.
- Be direct. Don't over-explain.
- Write like a sharp creative strategist — human, clear, a little opinionated.
- If a name is bad, say why. If a direction is weak, say so.
- Use plain language:
- "Strong direction."
- "This feels premium but slightly cold."
- "This has legs."
- "This sounds good but may be hard to own."
- "This feels too generic."
- "The meaning is interesting but the pronunciation is going to be a problem."
What to Avoid
Never generate names like: Nexa, Vanta, Zyra, Fluxo, Elevate, InnovateX, Brandify, Nexify, Lumio, Velora — or any random AI-sounding name without strategic justification.
Avoid:
- Overused suffixes:
-ly,-ify,-io,-hub,-labs,-works(unless strategically justified) - Names that lock the brand into one narrow product if expansion is likely
- Names too close to existing competitors
- Names with negative meanings in the target market's language
- Names that are difficult to spell after hearing once
- Names that feel like cheap SaaS tools when the brand is not one
Prefer:
- Names that carry a story
- Names that feel good when spoken aloud
- Names that can become a strong visual identity
- Names that can grow with the brand
The 7 Tests (apply mentally to every name you generate)
- Sound test — Say it aloud. Does it feel natural?
- Memory test — Can someone remember it after hearing it once?
- Search test — Can someone spell it after hearing it?
- Story test — Can the founder explain why this name exists?
- Logo test — Can it become a strong visual identity?
- Expansion test — Can the brand grow under this name?
- Trust test — Does it feel credible for the category?
Apply these silently. Surface the relevant ones in your output when they affect a name's score or recommendation.
Related Skills
- brand-strategy: Strategic foundation that informs naming direction
- brand-positioning: Positioning territory the name must fit
- brand-identity: Visual identity brief built around the chosen name
- brand-architecture: How the name fits into a broader brand/sub-brand system
- brand-context: Foundation context for all brand work
© arnabbagxd, 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 1 other file in skills/brand-naming of arnabbagxd/Brand-building-skills.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit 4a0a8b5
Compare with similar skills
Brand Naming 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 |
|---|---|---|---|---|---|---|
| Brand Naming this skillarnabbagxd/Brand-building-skills | 729 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Brand Strategy Squadohmyjahh/xquads-squads | 277 | — | ~852 | Automated safety check: Pass | MIT | |
| Brand Discoveryaffaan-m/ECC | 276k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Positioning BasicsBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.9k | Automated safety check: Pass | None | |
| 22 Personal Brand Context Globalminhnv0807/ai-business-skills | 609 | — | ~2.8k | Automated safety check: Pass | MIT | |
| 23 Personal Brand Strategy Globalminhnv0807/ai-business-skills | 609 | — | ~4.2k | Automated safety check: Pass | MIT |
Similar skills
Brand Discovery
affaan-m/ECC
Run a structured, resumable multi-session brand identity interview across 8 modules (purpose, positioning, audience, personality, voice, narrative, founder tension) using laddering, 5 Whys, and…
Positioning Basics
BrianRWagner/ai-marketing-claude-code-skills
Walks founders and marketers through five specific questions to produce a positioning statement, and optionally a full messaging hierarchy or competitive differentiation map.
22 Personal Brand Context Global
minhnv0807/ai-business-skills
A skill your agent uses when starting work on a PERSONAL brand — a founder, coach, or creator, not a company: creates .agents/personal-brand-context-global.md covering story, expertise, audience…
23 Personal Brand Strategy Global
minhnv0807/ai-business-skills
A skill your agent uses when a PERSONAL brand — founder, coach, or creator — needs a 12-month strategy: niche selection with Ikigai and a 3x3 matrix, positioning statement, a three-chapter story…
27 Personal Brand Monetize Global
minhnv0807/ai-business-skills
A skill your agent uses when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology…
More from arnabbagxd/Brand-building-skills
All 29 skills in this repoBrand Architecture
arnabbagxd/Brand-building-skills
Define how multiple brands, sub-brands, and product lines relate to each other under one organization.
Brand Context
arnabbagxd/Brand-building-skills
Foundation skill that captures and stores core brand context — identity, audience, positioning, values, and voice.
Brand Voice
arnabbagxd/Brand-building-skills
Define a brand's verbal identity — tone, voice, writing style, vocabulary, and messaging rules.
Google Ads
arnabbagxd/Brand-building-skills
Plan, build, and optimize Google Ads campaigns — Search, Shopping, Performance Max, Display, and YouTube — including keyword research, match types, bidding strategy, Quality Score, ad extensions…
Meta Ads
arnabbagxd/Brand-building-skills
Plan, build, and optimize Meta advertising campaigns on Facebook and Instagram — campaign structure, audience targeting (core, custom, lookalike), creative formats, pixel setup, retargeting…
Aso
arnabbagxd/Brand-building-skills
Optimize an app's store listing for maximum visibility and downloads — keyword strategy, title and subtitle optimization, screenshots, preview videos, rating and review management, and A/B testing…
Related
Categories
Questions about Brand Naming
What does Brand Naming do?
Full brand naming workflow for founders, agencies, and businesses. Brand Naming is an agent skill from arnabbagxd/Brand-building-skills. Full brand naming workflow for founders, agencies, and businesses.
When should I use Brand Naming?
Brand Naming fits situations like: the user says help me name this brand; I need a name for; what should I call my brand/company/product; naming a startup.
How do I install Brand Naming in Claude Code?
Run `npx skills add arnabbagxd/Brand-building-skills --skill brand-naming -a claude-code`. Or copy the skill folder (skills/brand-naming in arnabbagxd/Brand-building-skills) into .claude/skills/brand-naming in your project. Claude Code loads it when a task matches its description.
How do I install Brand Naming in Codex?
Run `npx skills add arnabbagxd/Brand-building-skills --skill brand-naming -a codex`. Or copy the skill folder (skills/brand-naming in arnabbagxd/Brand-building-skills) into .agents/skills/brand-naming in your project. Codex loads it when a task matches its description.
Can I use Brand Naming 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 arnabbagxd/Brand-building-skills --skill brand-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brand-naming, .gemini/skills/brand-naming, .github/skills/brand-naming and .opencode/skills/brand-naming in your project.
What does Brand Naming need to run?
SKILL.md names no scripts, command-line tools or credentials: Brand Naming is instructions for the agent only.
Does Brand Naming 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 Brand Naming 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 Brand Naming use?
Brand Naming 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 Brand Naming use?
About 2.3k tokens (SKILL.md is roughly 9.1k 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 Brand Naming?
Skills that share tags, products or a category with Brand Naming: Brand Strategy Squad (ohmyjahh/xquads-squads, 277 stars), Brand Discovery (affaan-m/ECC, 276k stars), Positioning Basics (BrianRWagner/ai-marketing-claude-code-skills, 441 stars) and 22 Personal Brand Context Global (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brand Naming?
arnabbagxd (a GitHub user) maintains it in arnabbagxd/Brand-building-skills, which has 729 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on June 13, 2026.
Source: arnabbagxd/Brand-building-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.