CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

check-domain-availability-dns

Check domain availability, compare first-year registration and annual renewal estimates, and diagnose DNS records for a domain the owner wants to connect. Use for explicit requests about a domain name, renewal price, CNAME/TXT records, www versus apex, or pending domain verification. General website design belongs to the existing website workflow.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A highly actionable, well-sequenced operational guide with concrete endpoints, commands, response fields, and strong validation/error-recovery guidance. It is slightly over-long for a single file, with some repeated safety assurances and host-specific detail that could be trimmed or split into references.

Suggestions

Consolidate the three repeated never-pays/never-writes-DNS assurances into a single statement (e.g., once in the intro and once in the closing section) to save tokens.

Move host-specific DNS quirks (Namecheap Host fields, Cloudflare proxy rules) into a one-level-deep reference file, keeping SKILL.md as a lean overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense and operational, but the no-payment/no-DNS-write assurance is repeated three times ("It never pays, registers or writes DNS", "Do not enter payment details…", "It does not take payment, register domains or write DNS") and a few lines re-explain DNS basics Claude already knows ("www and @ are distinct hosts"). Efficient overall with minor trimmable redundancy, matching anchor 4 rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Fully executable throughout: exact endpoints with parameters ("GET https://www.adddomain.net/api/check?name=example.com"), copy-ready commands ("npx github:vitaliiphangan-code/adddomain-cli find <name>"), and named response fields ("price.first_year", "owner_summary") that cover the common availability, buy-link, and DNS-verification cases. Matches the top anchor.

5 / 5

Workflow Clarity

Clear sequence (check → interpret per result → registrar link → symptom-matched DNS diagnosis → final report) with explicit validation: per-outcome interpretation rules (available/registered/unknown), verification endpoints ("verify", "dns-verify"), a symptom-to-check error-recovery map, and a completion checklist in "Report what is established". The skill is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Sections are well-organized and easy to navigate, but at roughly 70 lines it exceeds the under-50-line simple-skill exception, and host-specific quirks (Namecheap Host fields, Cloudflare proxy rules) are inlined where they could live in one-level-deep reference files. Good structure with minor organization gaps matches anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: concrete capabilities, an explicit trigger clause with natural keywords, and clear boundary guidance. Its only weakness is slightly incomplete synonym coverage of common user phrasings such as buying or registering a domain.

DimensionReasoningScore

Specificity

Lists three concrete, comprehensive actions — "Check domain availability", "compare first-year registration and annual renewal estimates", and "diagnose DNS records" — fully covering the skill's niche. No meaningful capability gaps, so it matches the top anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers both: the "what" is the three named actions, and the "when" is a concrete "Use for explicit requests about…" clause listing five trigger phrases. It also adds boundary guidance ("General website design belongs to the existing website workflow"), matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "domain name", "renewal price", "CNAME/TXT records", "www versus apex", "pending domain verification" — with synonyms for DNS record types. Common phrasings like "buy a domain" or "register a domain" are absent, so it falls just below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (domain availability, pricing, DNS connection) with distinct technical triggers (CNAME/TXT, www versus apex, domain verification) and explicitly de-scopes general website design to another workflow. Minimal conflict risk with neighboring skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vitaliiphangan-code/add-domain-website-skills

Path

skills/check-domain-availability-dns/SKILL.md

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.