New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Brand Name Checker

by luongnv89 in luongnv89/skills

Check product and brand names for conflicts across trademarks, domains, social handles, and package registries.

MITAuto-check passedLegal & Compliance

Install Brand Name Checker

skills CLI
$ npx skills add luongnv89/skills --skill brand-name-checker -a claude-code

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

GitHub CLI
$ gh skill install luongnv89/skills brand-name-checker --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/luongnv89/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brand-name-checker .claude/skills/brand-name-checker && 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
brand-name-checker
GitHub stars
131
Token cost
~2.6k tokens
SKILL.md length
1,225 words
Files
15 (incl. references)
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Check product and brand names for conflicts across trademarks, domains, social handles, and package registries.

  • Works in 6 steps: Social Media Check (First Priority) → Package Registry Check (if Step 1 clear) → Domain Check (if Step 1 clear) → …
  • Name brainstorming
  • SKILL.md covers When to Use, Subagent Architecture, Environment Check and Repo Sync Before Edits…, plus 8 more sections
  • Runs Python scripts from its folder; calls apt

What it does

Brand Name Checker is an agent skill from luongnv89/skills. Check product and brand names for conflicts across trademarks, domains, social handles, and package registries. Returns a risk level and Proceed/Modify/Abandon verdict. Don't use for name brainstorming, logo design, or trademark filings.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files (for example `agents/domain-checker.md`, `agents/registry-checker.md` and `agents/social-checker.md`).

It sits in Legal & Compliance, covering Intellectual property, Brainstorming and Logo and visual identity. It works with Homebrew and npm. The repository describes itself as: Supercharge your AI agents/bots with reusable skills. The licence is MIT.

When your agent uses it

  • Name brainstorming
  • Trademark filings

Example prompts

  • “/brand-name-checker”

Requirements

  • Python 3

Workflow steps

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

  1. Social Media Check (First Priority)
  2. Package Registry Check (if Step 1 clear)
  3. Domain Check (if Step 1 clear)
  4. Trademark Check (if Step 1 clear)
  5. Risk Assessment
  6. Recommendation

What it can do on your machine

Read from SKILL.md and the folder at commit b5ef695. 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

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • apt

    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 Name Checker loads about 2.6k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 1,225 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.6k

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 luongnv89/skills at commit b5ef695, republished under its MIT licence (© luongnv89). 1,225 words, ~2,643 tokens.

Download SKILL.mdSave it as .claude/skills/brand-name-checker/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
brand-name-checker
description
Check product and brand names for conflicts across trademarks, domains, social handles, and package registries. Returns a risk level and Proceed/Modify/Abandon verdict. Don't use for name brainstorming, logo design, or trademark filings.
license
MIT
effort
max
metadata.version
1.5.0
metadata.author
Luong NGUYEN <luongnv89@gmail.com>

Brand Name Checker

Check product and brand names for conflicts across trademarks, domains, social media, and package registries (npm, PyPI, Homebrew, apt).

When to Use

Use before adopting a product or brand name. To save context budget, queries, edge cases, and templates live in references/*.md.

Subagent Architecture

Workers in agents/ each return JSON: social-checker (6 platforms), registry-checker (npm, PyPI, Homebrew, apt), domain-checker (TLDs), trademark-checker (WIPO, EUIPO, INPI). The synthesizer applies the Step 5 risk policy.

  • Flow: Social → (if no exact handle is taken) → parallel {Registry, Domain, Trademark} → Synthesizer.
  • Early-Exit Rule: if social-checker finds an exact handle taken on any of the 6 platforms, skip Steps 2-4 and go straight to the synthesizer with an "Abandon" verdict.
  • Without subagents: run Steps 1-4 inline from references/source-checks.md, in the same order.

Environment Check

  1. Before Step 1, confirm the WebSearch and WebFetch tools are available.
  2. Run one test query.
  3. If either check fails, stop and return the BLOCKED report from Output Format with the error.

Repo Sync Before Edits (mandatory)

This skill writes no files by default. Before creating, updating, or deleting files in a repository, run the stash-first sync in references/repo-sync.md.

Input

Read the name from $ARGUMENTS; if empty, ask the user. If prd.md exists, read it for industry, target registries, and target domains.

Analysis Protocol

Queries, check URLs, and status rules for Steps 1-4: references/source-checks.md. Record every result with its source.

Step 1: Social Media Check (First Priority)

Search X/Twitter, Instagram, GitHub, LinkedIn, TikTok, and Discord. If an exact handle is taken (Early-Exit Rule), return NEGATIVE: Exact social handle taken (@platform) and skip to Step 6.

Step 2: Package Registry Check (if Step 1 clear)

Check npm, PyPI, Homebrew, and apt as Available, Taken (owner, last publish date), Similar, or Unknown. If target registry intent is missing or unverifiable, record it as unknown rather than treating every registry as clear.

Step 3: Domain Check (if Step 1 clear)

Check .com first, then .io, .app, .co, .eu, .fr:

  • Available: an authoritative availability result confirms the domain is unregistered
  • Parked: Domain exists but is for-sale/parking
  • Active: In use (flag if same industry)
  • Unknown: the source is unavailable or only shows that no active site was found; do not infer availability
Step 4: Trademark Check (if Step 1 clear)

Search WIPO, EUIPO, and INPI in Nice Classes 9, 35, 42; record each mark as live or expired.

Step 5: Risk Assessment

This section is the single authority for qualitative risk policy. The synthesizer must read and follow this section rather than inventing a second matrix. Classify each source result as confirmed, clear, or unknown/unverifiable. Upstream worker labels and severity fields are evidence only; re-check their underlying facts and do not blindly trust numeric severity.

Qualitative risk matrix

Risk precedence is High > Moderate > Low. Select the highest matching trigger; never average findings. "Multiple handles" means two or more confirmed non-exact handle collisions on distinct platforms.

Risk levelHighest matching trigger
HighExact social handle collision on any of the 6 platforms (the Early-Exit Rule); two or more confirmed non-exact social handle collisions; a confirmed collision on any target registry; an active .com in the same industry; an active trademark conflict in Nice Classes 9, 35, 42; a well-known-brand/typosquat conflict; or the existing elevated trademark-collision risk for a very short name.
ModerateNo High trigger, but one confirmed non-exact social handle collision; a different-industry active .com; a similar trademark; a confirmed collision on a non-target registry; or any unknown/unverifiable check or target intent.
LowEvery required check and target intent is explicitly verified, with no High or Moderate trigger and no unknown result; .com is verified available or parked.

Unknown policy: if checks or target intent are missing or unverifiable and there is no known High finding, use provisional Moderate + Modify pending verification. Unknown is not a confirmed collision and never Low clearance. An existing High finding remains High. No averaging or mitigation reduces High. Checks skipped by the Early-Exit Rule remain skipped, not cleared.

The exact-handle Early-Exit Rule is unchanged: an exact handle collision on any of the 6 platforms immediately returns an Abandon recommendation and skips the remaining checks. Report those checks as skipped, not clear.

Recommendation semantics
  • Proceed: only for a fully verified Low result; state the evidence and limitations, and never represent unknown checks as clearance.
  • Modify: for Moderate, including provisional Moderate; suggest variants that address confirmed conflicts and identify pending verification.
  • Abandon: for High; mitigation or available alternatives cannot lower the High result.
  • Any alternative that was not checked through the applicable sources must be labeled unverified; never invent availability or a Low assessment.
Show full SKILL.md (460 more words)Show less
Step 6: Recommendation

Follow the recommendation semantics above and the registration order in Final Action.

Output Format

Return this compact text report, the only format: it fits on one screen, so it needs no HTML or interactive view. Replace bracketed fields with observed evidence only. Use Unknown when a check is unverifiable and Skipped (not cleared) for checks omitted by the Early-Exit Rule. The RISK line must state the highest matching trigger and its policy rationale, not only the level. Keep RISK and RECOMMEND as the last two lines; callers read them.

RESULT: [COMPLETE | PARTIAL | BLOCKED] - [N/M checks verified; unknown and skipped counts]
SOCIAL: [Clear | NEGATIVE: reason | Unknown: reason]
REGISTRY: npm ([status]) | PyPI ([status]) | Homebrew ([status]) | apt ([status])
DOMAIN: .com ([status]) | .io ([status]) | .app ([status])
TM: WIPO ([status]) | EUIPO ([status]) | INPI ([status])
EVIDENCE: [source queried for each status: URL or search query, and check time]
SKIPPED: [sources, if any; skipped is not cleared]
UNKNOWN: [checks not verified, why, and what would verify them | none]
RISK: [Low | Moderate | High] - [highest matching trigger, evidence, and policy rationale]
RECOMMEND: [Proceed | Modify | Abandon] - [reason and checked or unverified alternatives]; next: [the user's decision and remaining actions]

RESULT status: COMPLETE when every check is verified or skipped by the Early-Exit Rule; PARTIAL when any check is Unknown; BLOCKED when no name was given or the web tools are unavailable (return only the RESULT line with the reason and fix). Before writing the report, read references/output-contract.md for the field rules and the next: clause. If prd.md exists, append the blocks from references/prd-integration.md.

Step Completion Reports

After each major step, emit a status report. The general template and per-step examples (Social, Registry, Domain, Trademark, Risk, Recommendation) live in references/step-reports.md. Adapt check names to what the step validates; use √ for pass and × for fail.

Acceptance Criteria

  • Social media check completed across all 6 platforms with explicit available/taken/unknown status
  • Package registry status confirmed for npm, PyPI, Homebrew, and apt (unless the Early-Exit Rule fired)
  • Domain availability checked for .com and at least two alternative TLDs (unless the Early-Exit Rule fired)
  • Trademark search completed against WIPO, EUIPO, and INPI (unless the Early-Exit Rule fired)
  • Risk level assigned (Low / Moderate / High) with the highest matching trigger as rationale
  • Final recommendation delivered (Proceed / Modify / Abandon) with named alternatives if needed
  • Understanding: the first line states the RESULT status; verified statuses cite a source on EVIDENCE while unverified ones sit on UNKNOWN; RISK names its trigger; RECOMMEND ends with next:. Unanswered human review leaves understanding unconfirmed (references/output-contract.md)

Expected Output

Example of an Early-Exit run for nimbus; COMPLETE and PARTIAL runs: references/output-contract.md.

text
RESULT: COMPLETE - 6/16 checks verified; 0 unknown, 10 skipped by the Early-Exit Rule
SOCIAL: NEGATIVE: Exact social handle taken (@github)
REGISTRY: Skipped (not cleared)
DOMAIN: Skipped (not cleared)
TM: Skipped (not cleared)
EVIDENCE: github.com/nimbus resolves to an active organization; checked 2026-01-15T10:31Z
SKIPPED: registries, domains, trademarks; skipped is not cleared
UNKNOWN: none
RISK: High - exact social handle collision on GitHub (Early-Exit Rule)
RECOMMEND: Abandon - nimbus-dev, nimbusly (both unverified); next: pick a candidate and run this check on it

Edge Cases

Rate limits, source outages, special characters, very short names, and typosquats: references/edge-cases.md. A rate-limited registry gets one retry after 5 seconds, then is marked unknown — do not skip silently or infer availability.

Final Action

  • Proceed: Only for a fully verified Low result; state the evidence and limitations, then suggest registration order:
    1. Package registries first — claim names on npm/PyPI/Homebrew immediately, even with a placeholder package. These are first-come-first-served and the most vulnerable to namespace squatting.
    2. Domain — register the primary domain.
    3. Social handles — secure handles on key platforms.
  • Modify: Recommend a variant addressing confirmed conflicts and list any pending verification. Alternatives not checked are unverified, never available by assertion.
  • Abandon: Recommend the best alternative from suggestions; mark unchecked alternatives unverified and do not claim that any option is clear.

© luongnv89, 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 14 other files (references) in skills/brand-name-checker of luongnv89/skills.

  • SKILL.md
  • agents/domain-checker.md
  • agents/registry-checker.md
  • agents/social-checker.md
  • agents/synthesizer.md
  • agents/trademark-checker.md
  • docs/README.md
  • evals/evals.json
  • references/edge-cases.md
  • references/output-contract.md
  • references/prd-integration.md
  • references/repo-sync.md
  • references/source-checks.md
  • references/step-reports.md
  • tests/test_risk_policy.py

Open the folder on GitHubat commit b5ef695

Compare with similar skills

Brand Name Checker 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.

Brand Name Checker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brand Name Checker this skillluongnv89/skills131—~2.6kAutomated safety check: PassMIT
Domaincoreyhaines31/makerskills851—~5.8kAutomated safety check: PassMIT
Patent Brainstorm Path Trackerillusionaireal/oh-my-patent104—~1.6kAutomated safety check: PassMIT
Innovationtravisjneuman/.claude100—~2.7kAutomated safety check: PassMIT
Paper to Chinese Patent DrafterYuan1z0825/nature-skills47k1 repos~1.1kAutomated safety check: PassApache-2.0
Thesvgglincker/thesvg2.8k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Domain

    coreyhaines31/makerskills

    When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle…

    851 GitHub stars~5.8k tokensUpdated 2 days ago
    Legal & ComplianceAuto-check passed

  • Patent Brainstorm Path Tracker

    illusionaireal/oh-my-patent

    Records, branches and visualizes the rounds of a patent brainstorming session, scoring each candidate and letting you restore an abandoned idea.

    104 GitHub stars~1.6k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Innovation

    travisjneuman/.claude

    Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy.

    100 GitHub stars~2.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Paper to Chinese Patent Drafter

    Yuan1z0825/nature-skills

    Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    Legal & ComplianceAuto-check passed

  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Paper To Cn Patent

    snipp-zha/Paper-to-patent-Skill

    Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.

    107 GitHub starsUsed in 1 repo~959 tokens
    Legal & ComplianceAuto-check passed

More from luongnv89/skills

All 36 skills in this repo

  • Appstore Assets

    luongnv89/skills

    Generate App Store screenshots and header/search images for iPhone, iPad and Mac from a codebase or landing page, or re-render a set.

    131 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Dont Make Me Think

    luongnv89/skills

    Review UI usability using Steve Krug's principles and produce a scannable report.

    131 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Herdr Agent

    luongnv89/skills

    Manage AI agent fleets in Herdr: tile root + sub-agents in one tab, start/prompt/wait/read/monitor via the herdr agent CLI, steer any pane; help lists every operation.

    131 GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Ollama Optimizer

    luongnv89/skills

    Optimize Ollama configuration for the current machine's hardware.

    131 GitHub stars~4.1k tokensUpdated today
    Auto-check: notes

  • Security Setup

    luongnv89/skills

    Install local-first security hardening: pre-commit secret detection, offline dependency scans, static analysis, reports, and gated free CI.

    131 GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • SEO AI Optimizer

    luongnv89/skills

    Audit and optimize websites for technical SEO, content SEO, and AI bot accessibility.

    131 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Brand Name Checker

What does Brand Name Checker do?

Check product and brand names for conflicts across trademarks, domains, social handles, and package registries. Brand Name Checker is an agent skill from luongnv89/skills. Check product and brand names for conflicts across trademarks, domains, social handles, and package registries.

When should I use Brand Name Checker?

Brand Name Checker fits situations like: name brainstorming; trademark filings.

How do I install Brand Name Checker in Claude Code?

Run `npx skills add luongnv89/skills --skill brand-name-checker -a claude-code`. Or copy the skill folder (skills/brand-name-checker in luongnv89/skills) into .claude/skills/brand-name-checker in your project. Claude Code loads it when a task matches its description.

How do I install Brand Name Checker in Codex?

Run `npx skills add luongnv89/skills --skill brand-name-checker -a codex`. Or copy the skill folder (skills/brand-name-checker in luongnv89/skills) into .agents/skills/brand-name-checker in your project. Codex loads it when a task matches its description.

Can I use Brand Name Checker 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 luongnv89/skills --skill brand-name-checker -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-name-checker, .gemini/skills/brand-name-checker, .github/skills/brand-name-checker and .opencode/skills/brand-name-checker in your project.

What does Brand Name Checker need to run?

Going by SKILL.md and its folder, Brand Name Checker needs Python for the scripts in its folder and the command-line tools its instructions call (apt). Our summary lists: Python 3.

Does Brand Name Checker 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 Name Checker 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 Name Checker use?

Brand Name Checker is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brand Name Checker use?

About 2.6k 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. Its references folder adds about 4k tokens, read only when the agent opens those files.

What are the alternatives to Brand Name Checker?

Skills that share tags, products or a category with Brand Name Checker: Domain (coreyhaines31/makerskills, 851 stars), Patent Brainstorm Path Tracker (illusionaireal/oh-my-patent, 104 stars), Innovation (travisjneuman/.claude, 100 stars) and Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brand Name Checker?

luongnv89 (a GitHub user) maintains it in luongnv89/skills, which has 131 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

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