vanity

Registers node major version vanity URL in the sibling vanity repo

Quality

61%

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 ./.agents/skills/vanity/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, actionable runbook with concrete commands and a verification step. The only gap is the absence of an explicit validate-and-retry loop for the batch HTML regeneration step.

Suggestions

Add an explicit feedback loop to step 6: if verification fails (missing tags or existing files changed), diagnose and re-run `make vangen` rather than leaving the failure unhandled.

Specify how to detect the version suffix programmatically (e.g. the `go.mod` module-path parsing rule) so the extraction is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: concrete commands and a JSON template with no padded explanation of concepts Claude already knows.	3 / 3
Actionability	It gives executable commands (`git rev-parse --abbrev-ref HEAD`, `make vangen`) and a complete, copy-paste-ready JSON entry with explicit placeholder substitution.	3 / 3
Workflow Clarity	Steps are clearly numbered with abort conditions and a final verification step, but for a batch operation (regenerating HTML, editing a repo) there is no explicit error-recovery feedback loop if verification fails.	2 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, and well-organized into Instructions and numbered Steps with no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

35%Weight 40%Scale 1-3

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 a concrete, niche action, but it relies on technical jargon and omits any explicit trigger guidance for when to use it. Adding a natural-language "Use when..." clause would lift both completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause with natural user phrasing, e.g. "Use when releasing a new node major version that needs a vanity import URL."

Replace jargon ("sibling vanity repo") with terms users actually say, such as "vanity import path" or "Go module vanity URL".

Mention the key triggers explicitly (new node major version, go.mod version suffix) so the skill is distinguishable from generic repo-management skills.

Dimension	Reasoning	Score
Specificity	"Registers node major version vanity URL" names a concrete action and domain, but it is a single action rather than multiple specific capabilities, so it does not reach the level-3 anchor.	2 / 3
Completeness	It states what the skill does but provides no "Use when..." trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like "vanity URL" and "sibling vanity repo" are internal/technical jargon; there are no natural keywords a user would actually say when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The niche (node major version vanity registration) is fairly specific, but the phrasing is generic enough that it could overlap with other repo/vanity-related skills.	2 / 3
	Total	7 / 12 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: akash-network/node
Path: .agents/skills/vanity/SKILL.md
Commit: 096bff5

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