cloudflare-registrar

Cloudflare Registrar: domain availability, prices, registration via mcporter.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudflare-registrar/SKILL.md

Quality

Content

93%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 lean, fully actionable, and well-structured for a simple skill, with appropriate guardrails and a validation checkpoint for the billable registration step; the only gap is the absence of an explicit error-recovery feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; defaults, guardrails, and three commands each earn their place.	5 / 5
Actionability	Three copy-paste-ready `npx mcporter call` snippets with real paths and request bodies cover the common cases (check, register, list); fully executable.	5 / 5
Workflow Clarity	Validation is present for the billable registration step ('Always run domain-check immediately before registration' plus a confirmation gate), avoiding the destructive-cap, but no explicit error-recovery feedback loop is documented, keeping it below 5.	4 / 5
Progressive Disclosure	A single-purpose skill under 50 lines with no external references, organized into clear Defaults/Guardrails/Commands sections; the simple-skill exception allows a 5.	5 / 5
	Total	19 / 20 Passed

Description

58%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 names concrete actions in a distinct niche, but it lacks an explicit 'Use when...' trigger clause and omits common natural trigger terms, capping completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when checking domain availability, comparing prices, or registering domains through Cloudflare.'

Include more natural trigger terms and synonyms users would actually say, such as 'buy a domain', 'domains', or 'renew a domain'.

Broaden capability coverage slightly (e.g., listing/renewing registrations, DNS) to move specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ("domain availability, prices, registration") with only minor gaps in coverage, matching the 'lists several specific actions' anchor; not a 5 because coverage is not comprehensive.	4 / 5
Completeness	The 'what' is clear (Registrar availability/pricing/registration) but there is no explicit 'Use when...' clause, so the 'when' is only weakly implied; per the guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"domain availability, prices, registration" are relevant but omit common natural variations users would say (e.g., "buy a domain", "domains", "DNS"), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Cloudflare Registrar ... via mcporter" is a clear niche with distinct triggers and low overlap risk; not a 5 only because the absence of an explicit trigger clause leaves the boundary slightly less locked down.	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/cloudflare-registrar/SKILL.md
Commit: 92442a1

Reviewed: 3 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.