CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

0.98x
Quality

55%

Does it follow best practices?

Impact

95%

0.98x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./domain-name-brainstormer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 skill is well-structured with a useful output template, but it is padded with generic domain-naming advice Claude already knows and never specifies how availability is actually checked, which weakens actionability and conciseness.

Suggestions

Trim general-knowledge sections ("What Makes a Good Domain", "TLD Guide", "Tips for Success", "Pricing Context") to the non-obvious essentials.

Specify the actual availability-checking mechanism (a tool, API endpoint, or CLI command) or explicitly state that availability is estimated and must be confirmed at a registrar.

Replace the full mock-conversation example with a concise output-template skeleton to save tokens.

DimensionReasoningScore

Conciseness

Several sections restate general knowledge Claude already has ("What Makes a Good Domain", "TLD Guide", "Tips for Success", "Pricing Context"), and the full mock-conversation example is padded, making it noticeably verbose.

2 / 5

Actionability

A concrete output template and example prompts are provided, but the core "checks availability" promise has no executable mechanism (no tool, API, or command), leaving a key detail missing.

3 / 5

Workflow Clarity

Example workflows list sequenced steps, but they read as user-facing advice rather than an operational Claude workflow, and the availability-checking step has no checkpoint or method.

3 / 5

Progressive Disclosure

The body is well organized with clear section headers and no nested references, though reference-style content (TLD guide, pricing) is inlined rather than split out.

4 / 5

Total

12

/

20

Passed

Description

65%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 clearly conveys a distinct, well-targeted capability with good natural trigger terms, but it omits any explicit "Use when..." guidance and only lists two concrete actions.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when launching a project, rebranding, or picking a domain name."

List a few more specific actions (e.g. suggest variations, compare TLDs, flag taken/premium domains) to raise specificity.

DimensionReasoningScore

Specificity

"Generates creative domain name ideas" and "checks availability across multiple TLDs" name the domain plus two concrete actions, but coverage stops there rather than listing several specific operations.

3 / 5

Completeness

The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural user phrasing is well covered ("domain name ideas", "brainstorming", "availability", plus concrete TLDs .com/.io/.dev/.ai), with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Domain-name brainstorming with TLD availability checking is a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ComposioHQ/awesome-claude-skills
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.