domain-name-brainstormer

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

Quality

56%

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

55%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 tidy catalogue stub that clearly routes users to an upstream bundle rather than duplicating it, with good structure and lean prose. Its weakness is that it provides almost no executable guidance or workflow for the skill's actual task, since all real content lives upstream.

Suggestions

Add at least one concrete, copy-paste example of the skill's output or invocation (e.g. a sample brainstormed domain list with checked TLDs) so the body is actionable on its own.

Include a minimal workflow for the domain-name task (generate candidates -> check availability across TLDs -> filter results) with a validation step, rather than only routing to the upstream repo.

Inline a short pointer to which upstream file holds the workflow (e.g. 'See upstream README.md for the generation script') so the one-level reference is more precisely signaled.

Dimension	Reasoning	Score
Conciseness	The body is short and largely free of concepts Claude already knows; the only mild padding is the explanatory 'Curated from...' line and the 'install the upstream bundle' preamble, so it sits at anchor 4 (efficient, minor trims possible) rather than the fully lean 5.	4 / 5
Actionability	The only concrete instruction is `open https://github.com/...` plus 'ask the agent to invoke this skill'; there is no executable guidance for the skill's actual task (domain generation or TLD checks), so it is incomplete concrete guidance matching anchor 3 rather than the mostly-executable 4.	3 / 5
Workflow Clarity	A rough sequence is present ('inspect upstream README' then 'ask the agent to invoke the skill') but the real workflow steps are undefined and there is no validation checkpoint, fitting anchor 2's 'rough sequence present but many gaps' below the structured 3.	2 / 5
Progressive Disclosure	The body is well-organized with clear sections (What it does, Source, How to use) and points one level deep to the upstream repo for the actual assets, scripts, and references; no bundle files exist locally to score against, so this is minor-organization-gaps anchor 4 rather than the fully split 5.	4 / 5
	Total	13 / 20 Passed

Description

58%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 specific and distinct, naming concrete actions and exact TLDs, but it omits any explicit 'when to use' trigger guidance and lacks the fuller set of natural trigger phrases a user would actually say. Adding a 'Use when...' clause and synonyms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete user scenarios (e.g. 'Use when brainstorming names for a startup, product, or project and you need to check which TLDs are free').

Broaden trigger terms to include natural phrases users say, such as 'is this domain available', 'check .com availability', 'website name ideas', and 'find a free domain'.

Reconsider whether listing only four TLDs in the description signals the full capability; either generalize ('common TLDs') or note that more can be checked.

Dimension	Reasoning	Score
Specificity	"Generate creative domain name ideas and check availability across multiple TLDs including .com, .io, .dev, and .ai" names the domain plus two concrete actions (generate ideas, check availability) with specific TLDs, matching anchor 4's 'several specific actions; minor gaps' rather than 3's limited coverage.	4 / 5
Completeness	The description clearly answers 'what' (generate ideas, check availability across TLDs) but contains no 'Use when...' or equivalent explicit trigger guidance; per the judging guideline a missing when-clause caps completeness at 3 even though the what is clear.	3 / 5
Trigger Term Quality	Contains relevant keywords like "domain name" and "TLD" plus extension names, but is missing common natural variations a user would actually say (e.g. "domain check", "website name", "is this domain available"), placing it at anchor 3 rather than the comprehensive coverage of 4 or 5.	3 / 5
Distinctiveness Conflict Risk	The domain-name brainstorming plus TLD-availability niche with named extensions is mostly distinct with only minor overlap risk against closely related naming skills, fitting anchor 4 better than the broad overlap of 3 or the minimal-risk precision of 5.	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: 1a7a23d

Reviewed: about 5 hours 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.