bump-skill-version
Skill32 starsChanged 5 months agoMITView on GitHub
Bump a skill's version number across all files in this repo (the skill's own frontmatter, the marketplace plugin entry, and any skill-specific occurrences). Pass the skill name and new version as arguments (e.g., 'blockscout-analysis 0.5.0'). Use after content changes are complete and the skill is ready for a new release.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- genericService/claude-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- genericService/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- blockscout-analysisSkill
- upgrade-blockscout-apiSkill
- web3-devSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 70
Apply skill-specific edits: if references/<skill-name>.md exists, read it and apply each edit it lists.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bump Skill Version
Update a skill's version string in every file that references it. This skill works for any skill in the repo: it first applies a shared bump procedure (frontmatter version + marketplace plugin entry), then consults a per-skill reference file for any extra locations specific to that skill.
Usage
Pass <skill-name> <new-version> as $ARGUMENTS (e.g., blockscout-analysis 0.5.0). If either is missing, ask the user before proceeding.
<skill-name> must match a top-level skill directory in the repo root (e.g., blockscout-analysis/, web3-dev/). Verify the directory and its SKILL.md exist before making any edit.
Shared procedure (applies to every skill)
These three edits are required for every skill bump.
1. <skill-name>/SKILL.md — frontmatter metadata
The YAML frontmatter contains a single-line JSON metadata field with a "version" key:
metadata: {"author":"blockscout.com","version":"<OLD>","github":...}Replace "version":"<OLD>" with "version":"<NEW>". Use exact strings — do not use regex replacements.
2. .claude-plugin/marketplace.json — plugin entry version
The marketplace manifest has a plugins array; each entry has its own "name" and "version" fields. The bare string "version": "<OLD>" may appear in more than one plugin entry when versions happen to coincide, so the old_string passed to Edit must include the "name" line of the target plugin to disambiguate. Match a block like this:
"name": "<skill-name>",
"description": "...",
"source": "./<skill-name>/",
"strict": false,
"version": "<OLD>",Replace only the "version": "<OLD>" line within that block with "version": "<NEW>". Leave the top-level marketplace metadata.version untouched — it tracks the marketplace as a whole, not the individual skill.
3. .agents/plugins/<skill-name>/.codex-plugin/plugin.json — codex plugin descriptor
Each skill that ships as a Codex plugin has its own descriptor at .agents/plugins/<skill-name>/.codex-plugin/plugin.json. The descriptor is dedicated to one skill, so the version field is unambiguous — but include the "name" line in the old_string anyway as a sanity check that the right file is being edited:
{
"name": "<skill-name>",
"version": "<OLD>",Replace "version": "<OLD>" with "version": "<NEW>". If the file does not exist for a given skill (a skill might not ship as a Codex plugin), skip this edit.
Skill-specific procedure
After the shared edits, check for references/<skill-name>.md next to this SKILL.md. If it exists, follow every extra step it lists. If it does not exist, the skill has no additional version sites — skip this step. This is intentional: keeping per-skill quirks in their own file lets SKILL.md stay short and lets new skills be onboarded by dropping in a single reference file (or none at all).
Procedure
- Parse arguments: split
$ARGUMENTSinto<skill-name>and<new-version>. If either is missing, ask the user. - Validate target: confirm
<skill-name>/SKILL.mdexists. Abort if not — a typo in the skill name would otherwise bump the wrong file. - Discover current version:
Grepfor the pattern"version":"[0-9]+\.[0-9]+\.[0-9]+"in<skill-name>/SKILL.mdto read the current version from the frontmatter metadata. - Validate version: confirm
<new-version>differs from the current version. Abort if identical. - Apply shared edits: perform the three edits in "Shared procedure" above. Use exact old/new strings. Skip the codex descriptor edit only if the file does not exist for this skill.
- Apply skill-specific edits: if
references/<skill-name>.mdexists, read it and apply each edit it lists. Otherwise skip. - Verify:
Grepfor the old version string scoped to<skill-name>/,.claude-plugin/marketplace.json, and.agents/plugins/<skill-name>/and confirm zero remaining occurrences. Other skills' files and.memory_bank/may legitimately contain that string and must not be touched.
Notes
.memory_bank/contains spec documentation with example version strings that do not track live versions; never update them.- Other skills'
SKILL.mdfiles may currently sit at the same numeric version as the one being bumped. Do not update them — only the targeted skill changes. - This skill only updates version strings. It does not modify content — use the appropriate per-skill content-update workflow for that.
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
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.

