agentleFS
akash-networkakash-network/node/.agents/skills/vanity/SKILL.md

vanity

Skill1.1k starsChanged 7 months agoApache-2.0View on GitHub

Registers node major version vanity URL in the sibling vanity repo

Trending

Quiet since July.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 2 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the akash-network/node repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about akash-network/node

The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 17

Talked about on GitHub (17 times).

On GitHub · 17

12 more on GitHub

The file

Files
SKILL.md

Instructions

Register the current node major version as a vanity URL in the github.com/com/akash-network/vanity repo.

Steps

  1. 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.
  2. Get the current git branch name using git rev-parse --abbrev-ref HEAD.
  3. 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.
  4. 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.

  1. Run make vangen in vanity to regenerate HTML files.
  2. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.