Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →akash-network/vanity
Registers node major version vanity URL in the sibling vanity repo
Passed 15 of 19 test cases with the skill, and 10 of 19 without it.
and 4 more in the full report
7 fixed10 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are on branch `main` and `go.mod` has `pkg.akt.dev/node/v2`. Checking `vanity/vangen.json`, there is already an entry with `"prefix": "node/v2"`. Should you overwrite the entry or append a second `node/v2` block?
| Checked | Without skill | With skill |
|---|---|---|
| Aborts registration without modifying vanity/vangen.json when the prefix already exists. | Missed | Passed |
The instructions your model reads when the skill loads.
Register the current node major version as a vanity URL in the github.com/com/akash-network/vanity repo.
Read the major version from go.mod in this repo. Extract the version suffix from the module path (e.g. pkg.akt.dev/node/v2 → v2). If the module path has no version suffix (v0/v1), abort — no vanity entry is needed.
Get the current git branch name using git rev-parse --abbrev-ref HEAD.
Open vanity/vangen.json and check if a repository entry with "prefix": "node/vN" already exists (where vN is the version from step 1). If it exists, inform the user and abort.
Add a new entry to the repositories array in vanity/vangen.json:
{
"prefix": "node/vN",
"type": "git",
"main": true,
"url": "https://github.com/akash-network/node",
"source": {
"home": "https://github.com/akash-network/node",
"dir": "https://github.com/akash-network/node/tree/BRANCH{/dir}",
"file": "https://github.com/akash-network/node/blob/BRANCH{/dir}/{file}#L{line}"
},
"website": {
"url": "https://github.com/akash-network/node"
}
}
Replace vN with the detected version and BRANCH with the detected branch name. Place the entry after the last existing node entry.
Run make vangen in vanity to regenerate HTML files.
Verify that vanity/node/vN/index.html was created and contains the correct go-import and go-source meta tags pointing to the detected branch. Also verify that existing vanity/node/index.html and any vanity/node/vN/index.html is unchanged.
test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.