CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vanity

Registers node major version vanity URL in the sibling vanity repo

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/vanity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplar of a concise, fully actionable instruction skill: exact commands, a complete template, explicit abort conditions, and a verification step that guards the batch regen operation.

DimensionReasoningScore

Conciseness

Lean, well-organized body with no padding or explanation of concepts Claude already knows; every line carries an instruction or a concrete template.

5 / 5

Actionability

Provides concrete commands (git rev-parse, make vangen), exact file paths, and a complete copy-paste JSON template with clearly marked placeholders to substitute.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation/abort checkpoints (abort on no version suffix, abort on existing entry, verify generated HTML and unchanged siblings), including a feedback-style verify step for the regen operation.

5 / 5

Progressive Disclosure

A short single-purpose skill under 50 lines with no bundle files, organized into a clear Instructions/Steps structure, which per the simple-skill guidance merits a 5.

5 / 5

Total

20

/

20

Passed

Description

46%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 a clear, specific action but omits any 'when to use' trigger guidance and relies on internal jargon rather than natural user language. It is distinct but not self-activating.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when bumping the node major version and the vanity URL needs updating.'

Replace jargon like 'sibling vanity repo' with phrasing a user would naturally say, or include synonyms such as 'vanity import path' or 'go module redirect'.

Mention the abort conditions (no version suffix, or entry already exists) so the scope is explicit up front.

DimensionReasoningScore

Specificity

Names the domain ('node major version vanity URL', 'sibling vanity repo') and one concrete action ('Registers'), but lists only a single action rather than comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (registers the vanity URL) but lacks any 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'vanity URL', 'vanity repo', and 'node major version' are technical jargon a user would rarely say naturally; missing the common phrasings users would actually use to invoke this skill.

2 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (node version vanity URLs in a specific repo) with minimal overlap risk against other skills, though the phrasing is not maximally distinct.

4 / 5

Total

12

/

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

akash-network/node

Path

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