upgrade-blockscout-api
Skill32 starsChanged 5 months agoMITView on GitHub
Refresh the bundled Blockscout API reference files inside one of this repo's end-user skills. Takes a target argument; each target has its own pipeline because the source artefacts differ (Swagger releases for `blockscout-analysis`, a build-time clone of the `pro-api` repo for `web3-dev`). Run when a target's upstream cuts a new release and the skill's bundled references need to catch up.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- blockscout-analysisSkill
- bump-skill-versionSkill
- web3-devSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Read the <target> argument from the user's invocation.
- Very specific: line 32
Read the matching reference file under references/ and follow it end-to-end.
- Distinctive: line 33
Do not mix instructions across targets.
≈ “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
Upgrade Blockscout API
Refresh the API reference files bundled inside one of this repo's end-user skills.
The two skills published from this repo each carry their own snapshot of the Blockscout API surface, but they're built from completely different upstream artefacts and on independent release cadences. Coupling their refreshes would force spurious diffs on whichever target's upstream hasn't moved, so this skill takes a target argument and runs only that target's pipeline.
Invocation
/upgrade-blockscout-api <target><target> must be one of:
| Target | Refreshes | Procedure |
blockscout-analysis | blockscout-analysis/references/blockscout-api/*.md and the master index, from latest Blockscout backend + Stats releases. | references/blockscout-analysis.md |
web3-dev | web3-dev/references/pro-api.json and web3-dev/references/pro-api-index.md, from a build-time clone of the pro-api repo. | references/web3-dev.md |
Routing rule
- Read the
<target>argument from the user's invocation. If it is missing or not in the table above, stop and ask which target to upgrade — listing the valid values. Do not guess and do not run both. - Read the matching reference file under
references/and follow it end-to-end. The reference is the canonical, authoritative procedure for that target. - Do not mix instructions across targets. The two procedures share no structural steps; lifting a step from one into the other will silently corrupt the bundled output.
Working directory
Both procedures assume the working directory is the repository root (the parent of blockscout-analysis/ and web3-dev/). Confirm this before running any script — the indexers and patch tools resolve paths relative to the repo root and will write to the wrong place otherwise.
Adding a new target
When a third skill in this repo starts bundling Blockscout API references, add it as a new row in the routing table above and drop a references/<new-target>.md file alongside the existing two. Keep this SKILL.md as routing only — every target's procedure lives in its own reference file so the agent loads only what the current run needs.
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.

