Agent skill

Vanity

by akash-network in akash-network/node

Registers node major version vanity URL in the sibling vanity repo

Apache-2.0Auto-check passedDevelopment

Install Vanity

skills CLI
$ npx skills add akash-network/node --skill vanity -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install akash-network/node vanity --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vanity .claude/skills/vanity && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vanity
GitHub stars
1.1k
Token cost
~423 tokens
SKILL.md length
167 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Registers node major version vanity URL in the sibling vanity repo

  • Works in 4 steps: Read the major version from go.mod in… → Get the current git branch name using… → Open vanity/vangen.json and check if a… → …
  • Development work in your project
  • Calls git and make

What it does

Vanity is an agent skill from akash-network/node. Registers node major version vanity URL in the sibling vanity repo

Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Go. The repository describes itself as: Source code for Akash node, a secure, transparent, and peer-to-peer cloud computing network. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “Use the vanity skill to register node major version vanity URL in the sibling vanity repo”
  • “/vanity”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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…
  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…
  4. Add a new entry to the repositories array in vanity/vangen.json

What it can do on your machine

Read from SKILL.md and the folder at commit 5193e54. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vanity loads about 423 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 167 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~423

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from akash-network/node at commit 5193e54, republished under its Apache-2.0 licence (© akash-network). 167 words, ~423 tokens.

Download SKILL.mdSave it as .claude/skills/vanity/SKILL.md (or your agent's skills folder).
name
vanity
description
Registers node major version vanity URL in the sibling vanity repo

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:

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.

© akash-network, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/vanity of akash-network/node.

Open the folder on GitHubat commit 5193e54

Compare with similar skills

Vanity next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vanity compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vanity this skillakash-network/node1.1k—~423Automated safety check: PassApache-2.0
Add Redis Command to go-redisredis/go-redis22k—~1.4kAutomated safety check: PassBSD-2-Clause
Go Pedantrychromedp/chromedp13k—~3.7kAutomated safety check: PassMIT
AO Desktop App LauncherOrchestratorInc/agent-orchestrator13k—~2.4kAutomated safety check: PassApache-2.0
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Run Dozzle Dev Instanceamir20/dozzle15k—~747Automated safety check: PassMIT

Similar skills

  • Official

    Walks through adding a new Redis or Redis module command to the go-redis client, from fetching the spec and docs to the type, interface wiring, parsing and tests.

    22k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • AO Desktop App Launcher

    OrchestratorInc/agent-orchestrator

    Launches, restarts and troubleshoots the real AO Electron desktop app from a checkout, with isolated or real local data and checks for stale processes.

    13k GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Starts a Dozzle dev server on a port derived from the current worktree so you can test by hand in a browser, without disturbing instances started elsewhere.

    15k GitHub stars~747 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Code Review

    yaklang/yakit

    对 Yakit 仓库的代码改动做规范化 code review:按代码逻辑、TS 定义、UI 引用与 Props、CSS 样式、依赖版本、配置项六个维度审查,检查测试用例缺失,强制执行 tsc 类型检查与 vitest 测试验证,输出「结果汇总 / 明细解释 / 合并结论」三块报告,经用户确认后写入文件。当用户要求 review、审查、评审代码改动,或在提交、合并、提 PR…

    7.8k GitHub stars~1.4k tokensUpdated 7 days ago
    DevelopmentAuto-check: notes

More from akash-network/node

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    Auto-check passed
  • Upgrade Changelog

    akash-network/node

    Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go

    1.1k GitHub stars~923 tokensUpdated yesterday
    Auto-check passed
  • Setup Env

    akash-network/node

    Set up development environment by loading direnv. An agent skill from akash-network/node.

    1.1k GitHub stars~304 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Vanity

What does Vanity do?

Registers node major version vanity URL in the sibling vanity repo. Vanity is an agent skill from akash-network/node.

When should I use Vanity?

Vanity fits situations like: development work in your project.

How do I install Vanity in Claude Code?

Run `npx skills add akash-network/node --skill vanity -a claude-code`. Or copy the skill folder (.agents/skills/vanity in akash-network/node) into .claude/skills/vanity in your project. Claude Code loads it when a task matches its description.

How do I install Vanity in Codex?

Run `npx skills add akash-network/node --skill vanity -a codex`. Or copy the skill folder (.agents/skills/vanity in akash-network/node) into .agents/skills/vanity in your project. Codex loads it when a task matches its description.

Can I use Vanity in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akash-network/node --skill vanity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vanity, .gemini/skills/vanity, .github/skills/vanity and .opencode/skills/vanity in your project.

What does Vanity need to run?

Going by SKILL.md and its folder, Vanity needs the command-line tools its instructions call (git and make).

Does Vanity access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vanity safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vanity use?

Vanity is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vanity use?

About 423 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vanity?

Skills that share tags, products or a category with Vanity: Add Redis Command to go-redis (redis/go-redis, 22k stars), Go Pedantry (chromedp/chromedp, 13k stars), AO Desktop App Launcher (OrchestratorInc/agent-orchestrator, 13k stars) and Go-Redis Release Preparation (redis/go-redis, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vanity?

akash-network (a GitHub organization) maintains it in akash-network/node, which has 1,116 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: akash-network/node on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.