domain-hunter
Search domains, compare prices, find promo codes, get purchase recommendations. Use when user wants to buy a domain, check domain prices, find domain deals, compare registrars, or search for .ai/.com domains.
86
81%
Does it follow best practices?
Impact
94%
1.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that follows best practices closely. It provides specific capabilities, includes natural trigger terms users would actually say, has an explicit 'Use when...' clause, and occupies a clear niche that is unlikely to conflict with other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search domains, compare prices, find promo codes, get purchase recommendations.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (search domains, compare prices, find promo codes, get purchase recommendations) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'buy a domain', 'check domain prices', 'find domain deals', 'compare registrars', '.ai/.com domains'. Good coverage of common user phrasings and specific TLD extensions. | 3 / 3 |
Distinctiveness Conflict Risk | Domain purchasing/searching is a clear niche. The mention of registrars, promo codes, .ai/.com domains, and price comparison makes this highly distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured workflow for domain hunting with clear sequencing and validation checkpoints (especially the availability check and user confirmation gates). However, actionability is weakened by placeholder paths for external skills and template-style commands rather than fully executable examples. Conciseness could be improved by trimming domain naming advice Claude already knows and moving reference data (registrar handles, comparison sites) to bundle files.
Suggestions
Replace placeholder paths like `<twitter_skill_directory>` and `<reddit_skill_directory>` with concrete instructions on how to locate or invoke these skills, or note them as optional dependencies with fallback approaches.
Move static reference data (registrar Twitter handles, price comparison sites, naming pattern tips) into the referenced `references/registrars.md` file to keep the main skill leaner and more actionable.
Provide the referenced bundle files (`references/registrars.md`, `references/spaceship-api.md`) so the progressive disclosure structure is actually functional.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., listing common suffixes, explaining naming patterns like `{action}{noun}` that Claude already knows). The promo code section with placeholder paths adds bulk without being directly executable. | 2 / 3 |
Actionability | Provides concrete commands for WHOIS checks and web searches, but several key elements are pseudocode or placeholders (e.g., `<twitter_skill_directory>`, `<reddit_skill_directory>`, `{domain}`, `{tld}`, `{registrar}`). The WebSearch syntax is illustrative rather than executable, and the Twitter/Reddit skill integrations assume external skills without confirming their availability. | 2 / 3 |
Workflow Clarity | Clear 4-step sequential workflow with explicit validation checkpoints: Step 1 requires confirming availability before presenting domains, explicitly instructs to wait for user confirmation before proceeding, and Step 4 provides a structured output format. The flow from ideation → verification → pricing → recommendation is well-sequenced. | 3 / 3 |
Progressive Disclosure | References to `references/registrars.md` and `references/spaceship-api.md` are well-signaled and one level deep, but no bundle files were provided to verify they exist. The main content is reasonably structured but the price comparison sites and registrar handles could be moved to a reference file to keep the skill leaner. | 2 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- resciencelab/opc-skills
- Commit
74fa178
- 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.