domain-name-brainstormer
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
51
26%
Does it follow best practices?
Impact
99%
1.05xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/domain-name-brainstormer/SKILL.mdQuality
Discovery
40%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 communicates a clear and distinctive capability around domain name brainstorming and availability checking, which gives it a strong niche. However, it lacks an explicit 'Use when...' clause, uses second person ('your project'), and includes filler marketing language ('Saves hours of brainstorming') that doesn't aid skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for domain name ideas, wants to check domain availability, or mentions registering or buying a domain.'
Replace second person 'your project' with third person phrasing like 'for a given project' and remove the marketing fluff 'Saves hours of brainstorming and manual checking' in favor of additional trigger terms like 'domain search', 'website name', 'register a domain'.
Include more natural user trigger terms such as 'find a domain', 'domain search', 'website name', 'buy a domain', or 'domain registration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (domain names) and some actions (generates ideas, checks availability), but doesn't list comprehensive specific actions like suggesting alternatives, ranking by relevance, or exporting results. | 2 / 3 |
Completeness | Describes what it does (generates domain names, checks availability) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per rubric rules, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'domain name', 'TLDs', '.com', '.io', '.dev', '.ai', and 'availability', but misses common user phrases like 'register a domain', 'buy a domain', 'domain search', or 'website name'. | 2 / 3 |
Distinctiveness Conflict Risk | Domain name generation and TLD availability checking is a very specific niche that is unlikely to conflict with other skills. The mention of specific TLDs (.com, .io, .dev, .ai) makes it clearly distinguishable. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a marketing description of what a domain brainstorming assistant would do, rather than an actionable skill teaching Claude how to do it. It lacks any concrete mechanism (API, tool, script) for checking domain availability, making the core promise undeliverable. The content is extremely verbose, explaining many concepts Claude already knows (what TLDs are, what makes a good domain name) while failing to provide the one thing that would make it useful: executable code or tool usage for actual availability checking.
Suggestions
Add concrete, executable code or tool calls for checking domain availability (e.g., using whois commands, DNS lookups, or a specific API like domainr or namecheap)
Remove sections Claude already knows: TLD descriptions, general branding tips, 'What Makes a Good Domain', and 'When to Use This Skill'
Reduce the example output to a compact template showing the expected format, rather than a lengthy mock conversation
Split reference material (TLD guide, pricing context, naming tips) into separate files if they must be retained, and keep SKILL.md focused on the core workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive content Claude already knows (what makes a good domain, TLD descriptions, general branding tips). The 'When to Use This Skill' and 'What This Skill Does' sections are unnecessary padding. The pricing context, tips for success, and related tools sections add little actionable value. This skill could be reduced to ~25% of its current length. | 1 / 3 |
Actionability | Despite its length, the skill provides no concrete mechanism for actually checking domain availability—no API calls, no CLI tools, no executable code. The example output fabricates availability data with no explanation of how to actually verify it. The skill describes what it would do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | The 'Example Workflows' section provides numbered steps for different scenarios (startup launch, personal brand, product naming), giving some sequential structure. However, there are no validation checkpoints, no error handling, and no concrete tools or commands to execute at each step—they read more like wishlists than actionable workflows. | 2 / 3 |
Progressive Disclosure | All content is dumped into a single monolithic file with no references to external files. The TLD guide, naming tips, pricing context, and multiple workflow examples could easily be split into separate reference files. The document is a wall of text with no layered structure. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- Reviewed
Table of Contents
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.