Loading the registry…
Generate and vet brand names for a product that also have a free, registerable domain. Use this skill whenever someone wants to NAME a product, app, startup, company, SaaS, or feature and wants a name whose domain is actually gettable — "find a brand name", "name my product/app/startup", "what should I call my company/this product", "come up with product name ideas", "naming ideas with a free .com", "every name I like has the domain taken, find ones that are free", "I need a short memorable name with an available domain", "help me name my business", "rebrand and check the domain". It brainstorms many candidates across naming archetypes, screens them for global/linguistic safety and target-persona fit, scores and ranks them, then verifies domain availability (.com/.io/.ai/.co/.app via RDAP + DNS + WHOIS) plus social handles, and returns a ranked shortlist of names whose domains are free. It is specifically for inventing and choosing a NEW brand name; a one-off lookup of a single domain already chosen, registering a domain, DNS or registrar questions, a standalone trademark search, logo design, taglines or copy for a name that already exists, and naming a person, pet, or code identifier are separate tasks this skill does not handle.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
9 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'jannosiilbek/jann0z-claude-plugins (brand-namer)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'jannosiilbek/jann0z-claude-plugins (brand-namer)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
105 findings · 13.6s
v0.3.74
10 findings · 3.2s
v0.1.0
1 finding · 5.6s
v0.1.0
0 findings · 5.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 116 findings across every scanner that examined this package. None of the 9 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 66 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/plugins/napkin/skills/ddd-usecases/scripts/fixtures/spec/SKILL.md, /repo/plugins/napkin/skills/ddd-align/scripts/fixtures/golden/spec/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
42 MANIFEST_MISSING_LICENSE
Files: /repo/plugins/napkin/skills/ddd-usecases/SKILL.md, /repo/plugins/napkin/skills/erd-diagram/SKILL.md, /repo/plugins/napkin/skills/ddd-brief/SKILL.md and 39 more · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.worktreeinclude · reported by cisco-skill-scanner
1 MANIFEST_DESCRIPTION_TOO_LONG
Files: /repo/plugins/lunchbox/skills/brand-namer/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/plugins/lunchbox/skills/brand-namer/scripts/check-availability.mjs · reported by nerlo-behavioral
66 The model's answer could not be read.
Rules: COMMAND_INJECTION_JS_CHILD_PROCESS, AAK-MARKETPLACE-001, LOW_ANALYZABILITY and 5 more · Files: /repo/plugins/napkin/skills/ddd-usecases/scripts/selftest.mjs, /repo/plugins/napkin/skills/ddd-align/scripts/selftest.mjs, .claude-plugin/marketplace.json and 52 more · reported by cisco-skill-scanner, agent-audit-kit
Critical command injection vulnerabilities detected
The artifact contains critical command injection vulnerabilities in `selftest.mjs` files within the `ddd-align` and `ddd-usecases` skills, allowing for arbitrary shell execution. Additionally, there are multiple findings indicating potential network egress capabilities and file write violations. Several components also exhibit low analyzability, which can obscure further risks.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.