domain-name-brainstormer
tessl i github:softaworks/agent-toolkit --skill domain-name-brainstormerGenerates 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.
Activation
40%The description identifies a clear, distinct capability around domain name generation and availability checking, with good TLD examples. However, it lacks explicit 'Use when...' guidance and relies on marketing language ('Saves hours') instead of actionable triggers. The second-person 'your project' should be avoided per guidelines.
Suggestions
Add a 'Use when...' clause with trigger terms like 'need a domain name', 'check if domain is available', 'website name ideas', 'register domain'
Remove marketing fluff ('Saves hours of brainstorming and manual checking') and replace with explicit trigger scenarios
Rewrite to third person voice - change 'your project' to 'a project' or remove the possessive entirely
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (domain names) and two actions (generates ideas, checks availability), but lacks comprehensive detail about specific capabilities like bulk checking, alternative suggestions, or pricing information. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or explicit trigger guidance. The phrase 'Saves hours of brainstorming' is marketing fluff rather than actionable trigger information. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'domain name', 'TLDs', '.com', '.io', '.dev', '.ai', and 'availability', but misses common user phrases like 'website name', 'register domain', 'buy domain', or 'domain search'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on domain name generation and availability checking with explicit TLD examples; unlikely to conflict with other skills due to the specific domain focus. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
27%This skill is heavily padded with explanatory content that Claude already knows (domain naming best practices, TLD descriptions, pricing ranges). While it shows good example output format, it lacks actual implementation details for checking domain availability - the core technical capability. The content would benefit from dramatic reduction and addition of concrete tools/APIs.
Suggestions
Remove 'When to Use This Skill', 'Domain Naming Tips', 'TLD Guide', and 'Pricing Context' sections - Claude knows these concepts
Add concrete implementation: specify which APIs or tools to use for availability checking (e.g., WHOIS lookup commands, DNS queries, or specific availability APIs)
Move reference content (TLD guide, tips) to a separate REFERENCE.md file and link to it
Reduce the example output to show the format without extensive explanations of why each name works
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations Claude doesn't need (what makes a good domain, TLD guide, pricing context). The 'What This Skill Does' and 'When to Use This Skill' sections explain obvious concepts. Could be reduced by 70%+ while preserving all actionable content. | 1 / 3 |
Actionability | Provides example prompts and shows expected output format, but lacks any executable code or actual implementation for checking domain availability. The skill describes what Claude should do but doesn't provide concrete tools, APIs, or commands to actually verify availability. | 2 / 3 |
Workflow Clarity | Lists workflows (Startup Launch, Personal Brand, Product Naming) with numbered steps, but these are high-level descriptions without validation checkpoints. No feedback loops for when domains are taken or how to iterate on suggestions systematically. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including TLD guides, pricing context, and tips that could be separate reference documents. No clear navigation structure for a skill of this length. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
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.