vanity
SkillDev toolsRegisters node major version vanity URL in the sibling vanity repo
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the vanity skill
What this skill tells your AI
The instructions your AI receives, as published by akash-network/node in .agents/skills/vanity/SKILL.md and read by ahel’s review.
Register the current node major version as a vanity URL in the github.com/com/akash-network/vanity repo.
Steps
-
Read the major version from
go.modin 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.jsonand check if a repository entry with"prefix": "node/vN"already exists (wherevNis the version from step 1). If it exists, inform the user and abort. -
Add a new entry to the
repositoriesarray invanity/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 vangeninvanityto regenerate HTML files. -
Verify that
vanity/node/vN/index.htmlwas created and contains the correctgo-importandgo-sourcemeta tags pointing to the detected branch. Also verify that existingvanity/node/index.htmland anyvanity/node/vN/index.htmlis unchanged.
Signals
- GitHub stars
- 1k
- Forks
- 275
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
vanity- Source
- github.com/akash-network/node