domain-dns-ops

DNS/domain ops: registrars, zones, redirects, DNS/HTTP verify, manager truth.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/domain-dns-ops/SKILL.md

Quality

Content

82%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 content is an exemplary thin-router skill: token-efficient, well-structured, and mostly executable, with a clearly sequenced golden path that ends in verification. Its main gaps are deferred execution detail for a few DNS/redirect steps, no explicit failure-recovery loop, and an orphaned bundle reference file that the body never links.

Suggestions

Link the bundled reference from the body (e.g. under 'Source of truth': 'See references/manager-repo.md for a file-by-file map of the manager repo') so progressive disclosure starts inside the skill.

Add a short failure-recovery step to the verify section (e.g. 'If dig does not return CF IPs, re-check registrar/nameservers before changing DNS records').

Inline the exact cli4 commands for the DNS placeholder A records (currently deferred to DNS.md) since they sit on the golden path and block HTTPS termination.

Dimension	Reasoning	Score
Conciseness	The body is a lean router: it explains no concepts Claude already knows (no 'what is DNS', no library comparisons) and every line is operational — commands, file pointers, guardrails. This matches the anchor 'lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Most steps carry concrete, executable commands ('cli4 --get name=example.com /zones', 'dig +short example.com @1.1.1.1', 'curl -I https://example.com', the full namecheap-set-ns invocation, git commands). It falls short of fully copy-paste-ready because key steps defer execution detail to external docs ('see ~/Projects/manager/DNS.md for exact cli4 calls' for the DNS placeholder step and the Page Rules template).	4 / 5
Workflow Clarity	The golden path is a clearly sequenced 6-step workflow ending in an explicit verify step with expected outcomes ('expect CF anycast', 'expect 301'), plus a guardrail to 'verify after each change (NS -> DNS -> redirect)'. It misses 5 because there is no explicit error-recovery or rollback loop when a verify step fails — failure handling is only hinted at in the guardrail about confirming the registrar.	4 / 5
Progressive Disclosure	The SKILL.md is a well-organized overview with a dedicated 'Source of truth' section pointing one level deep to clearly named external files, and content is appropriately split. The minor gap: the skill's own bundle file, references/manager-repo.md, is never referenced from the body, so a navigating agent discovers it only by listing the bundle.	4 / 5
	Total	17 / 20 Passed

Description

61%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 is concise and domain-distinct with several natural trigger terms, but it functions as a compressed topic list rather than a complete description. It lacks an explicit 'Use when...' trigger clause and leans on internal jargon ('manager truth'), leaving a user unsure exactly when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up a new domain, changing nameservers, debugging DNS/redirects, or verifying DNS/HTTP for vanity domains.'

Replace the jargon phrase 'manager truth' with a concrete capability such as 'routes through the ~/Projects/manager repo as the source of truth'.

Include common trigger synonyms like 'nameservers', 'Cloudflare', and 'DNS records' so the description matches the natural phrasing users are likely to use.

Dimension	Reasoning	Score
Specificity	The description names the domain ('DNS/domain ops') and lists concrete areas ('registrars, zones, redirects, DNS/HTTP verify'), but it is a noun-heavy topic list with only one action verb ('verify'); 'manager truth' is internal jargon rather than a concrete capability. It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' — below 4 because it doesn't articulate several specific actions.	3 / 5
Completeness	The 'what' is reasonably clear (DNS/domain operations covering registrars, zones, redirects, verification), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3. It is above 2 because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	'DNS', 'domain', 'redirects', and 'verify' are natural phrases a user would say when needing this skill, giving good keyword coverage. It falls short of 5 because common variations like 'nameservers', 'Cloudflare', or 'DNS records' are missing, and 'manager truth' is not a natural user term.	4 / 5
Distinctiveness Conflict Risk	DNS/domain operations with registrar and redirect specifics is a clear niche with minimal conflict risk against unrelated skills. Minor overlap risk remains with broader cloud/infrastructure or networking skills, so it does not reach 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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: steipete/agent-scripts
Path: skills/domain-dns-ops/SKILL.md
Commit: 3f8c6a3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.