convex-acquire-domain

Find and buy a domain for the current Convex app through Convex, then bind it (labs; spend action).

Quality

66%

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 ./.agents/skills/convex-acquire-domain/SKILL.md

Quality

Content

76%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 body is exceptionally concise and well-structured with a clear, gated workflow for a destructive spend action. Its main weakness is actionability: it describes steps at a conceptual level without the specific Convex commands, CLI invocations, or API calls needed to execute them.

Suggestions

Add the concrete commands/API calls for each step — e.g., the exact `convex` CLI or control-plane invocation to check availability, register via DNSimple, and attach the custom domain.

Include a short example of the rebind step (the specific RP_ID/ORIGIN fields and the re-publish command) so the auth-origin change is reproducible.

Show how to verify the bind succeeded (e.g., checking the custom-domain status) to add an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a short workflow, terse rules, no padding or explanation of concepts Claude already knows; every line carries instruction or constraint, such as 'the agent never holds the registrar credential' which earns its place as a safety boundary.	5 / 5
Actionability	Guidance is concrete in intent (brainstorm names, check availability/price, register through Convex via DNSimple, rebind RP_ID/ORIGIN, re-publish) but provides no executable commands, API calls, or code; it instructs at a high level rather than giving copy-paste-ready steps.	3 / 5
Workflow Clarity	A clear numbered sequence with an explicit validation checkpoint (wait for an explicit yes on a specific domain before the Tier-2 spend action) and a re-publish step after rebinding; minor gaps only — no error-recovery loop, but the destructive spend action is properly gated.	4 / 5
Progressive Disclosure	This is a short, single-purpose skill under 50 lines with no external bundle files needed; it is well-organized into Workflow and Rules sections with no nested references, qualifying for the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

57%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 states concrete actions and a clear niche but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger-term coverage is adequate but lacks natural user phrasings and synonyms.

Suggestions

Add an explicit 'Use when...' clause stating the natural trigger (e.g., 'Use when the user wants to register or buy a custom domain for their Convex deployment').

Include natural synonyms users actually say — 'register a domain', 'custom domain', 'get a domain name' — alongside 'buy' and 'bind'.

Drop or relocate the parenthetical 'labs; spend action' jargon from the description to reduce technical noise.

Dimension	Reasoning	Score
Specificity	Names the domain (domain purchasing for a Convex app) and several concrete actions — find, buy, bind — but the actions are brief and omit details like availability/price checking found only in the body, leaving minor gaps in coverage.	4 / 5
Completeness	It clearly states the 'what' (find, buy, bind a domain) but provides no 'Use when...' clause or explicit trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It contains relevant terms ('domain', 'buy', 'bind') but lacks the natural phrases and synonyms a user would say ('register a domain', 'custom domain', 'get a domain name'), and includes technical jargon like 'RP_ID/ORIGIN'-adjacent framing via 'spend action'.	3 / 5
Distinctiveness Conflict Risk	It carves a fairly distinct niche — buying a domain specifically through Convex for the current Convex app — with only minor overlap risk against a generic 'domains' capability that it explicitly distinguishes from in the body.	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: openclaw/clawhub
Path: .agents/skills/convex-acquire-domain/SKILL.md
Commit: 694ff71

Reviewed: 1 day 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.