tessl install https://github.com/softaworks/agent-toolkit --skill domain-name-brainstormergithub.com/softaworks/agent-toolkit
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.
Average Score
43%
Content
27%
Description
40%
Generated
Validations
Total score
12/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 213 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'domain-name-brainstormer' | |
description_field 'description' field is valid (178 chars) | |
description_voice 'description' should use third person voice; found second person: 'your ' | |
description_trigger_hint Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 4
Total score
6/12| Dimension | 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 |
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
Overall Assessment
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.
Description
Suggestions 3
Total score
8/12| Dimension | 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 |
Suggestions
Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user needs domain name ideas, wants to check domain availability, is starting a new project/website, or mentions registering a domain.'
Include additional natural trigger terms users would say: 'website name', 'register domain', 'buy domain', 'domain search', 'URL ideas'.
Remove the marketing fluff ('Saves hours of brainstorming and manual checking') and replace with actionable capability details or trigger conditions.
Overall Assessment
The description identifies a clear niche (domain name generation and availability checking) with good distinctiveness, but suffers from missing explicit trigger guidance and incomplete trigger term coverage. The marketing language ('Saves hours of brainstorming') adds no value for skill selection and the lack of a 'Use when...' clause significantly weakens its utility for Claude's skill selection process.