domain-name-brainstormer

Generate creative domain name ideas and check availability across multiple TLDs including .com, .io, .dev, and .ai.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/domain-name-brainstormer/SKILL.md

Quality

Content

47%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured catalogue stub, but it contains no actionable instructions for the skill's stated purpose — generating domain ideas and checking availability are entirely delegated to an external repository with only an `open` command as a pointer. Workflow and actionability are weak because every substantive step is undefined.

Suggestions

Inline a minimal actionable quick-start (e.g., a concrete availability-check command such as a whois/DNS lookup, or a naming heuristic) so the skill is usable without leaving the file.

Replace "install the upstream bundle" with the specific installation commands or file paths instead of deferring to "Inspect the upstream README for exact paths".

De-duplicate the description (repeated in "What it does") and the upstream URL (appears in both Source and the bash block) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is short, uses clean sections, and explains nothing Claude already knows; the only trims are minor duplication (the frontmatter description is repeated verbatim in "What it does" and the upstream URL appears twice), matching the efficient-with-minor-trims anchor.	4 / 5
Actionability	The only concrete command is `open <upstream URL>`; there is no executable guidance for the skill's actual task — no method for generating name ideas, no availability-check command or API. All real steps are delegated to an external README the user must inspect, matching the minimal-concrete-guidance anchor.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream → install bundle → invoke by name or trigger phrase), but the critical install step is undefined ("install the upstream bundle" with no command or path) and details are deferred to an external README, matching the rough-sequence-with-many-gaps anchor.	2 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the body is well-organized into clear sections with a single, clearly signaled upstream reference — good structure with the minor gap that the actual skill content lives entirely off-repo.	4 / 5
	Total	12 / 20 Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and specific about its two core actions, with concrete TLD extensions that aid discovery. Its main weakness is the missing "Use when..." clause, which caps completeness and limits natural trigger coverage. Adding explicit usage triggers and a couple of synonyms (brainstorm, naming) would raise it substantially.

Suggestions

Append a "Use when..." clause, e.g., "Use when the user asks for domain name ideas, wants to name a startup or product, or needs to check domain availability."

Include common user phrasings and synonyms such as "brainstorm names", "naming", or "is this domain taken" to broaden natural trigger coverage.

Optionally mention one more concrete capability (e.g., suggesting alternatives when a domain is taken) to lift specificity from two actions to several.

Dimension	Reasoning	Score
Specificity	"Generate creative domain name ideas" and "check availability across multiple TLDs" name the domain and two concrete actions with specific TLD extensions, matching the 1-2-concrete-actions anchor; it is not a 4 because no further capabilities (e.g., shortlisting, registrar lookups, alternatives) are listed.	3 / 5
Completeness	The "what" is clear (generate ideas, check TLD availability) but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms include "domain name", "check availability", "TLDs", and the concrete extensions ".com, .io, .dev, .ai", giving good keyword coverage; falls short of 5 because common user phrasings like "brainstorm", "naming", or "is this domain taken" are absent.	4 / 5
Distinctiveness Conflict Risk	Domain-name brainstorming plus TLD availability checking is a fairly distinct niche with specific trigger terms; minor overlap risk remains with generic naming or marketing-copy skills, so it sits mostly-distinct rather than minimal-conflict.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/domain-name-brainstormer/SKILL.md
Commit: 1b47e60

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.