update-metadata
Skill251 starsChanged 5 months agoApache-2.0View on GitHub
Refresh icons and metadata/stats for agents and cloud providers in manifest.json. Run this when: - An agent or cloud provider's logo changes - An icon URL breaks (404 or stale redirect) - A new agent or cloud is added without an icon - GitHub star counts need refreshing - Agent repo info changed (license, language) - You want a full metadata audit - You need to validate that all source URLs are still reachable Run the update script, passing through…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OpenRouterTeam/spawnword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- OpenRouterTeam/spawn★ 251100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository9 other files it gives its agents.
- skills/junie/AGENTS.mdAGENTS.md
- skills/opencode/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- pclSkill
- setup-spaSkill
- update-teamSkill
- spawnSkill
- spawnSkill
- spawnSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Run the update script, passing through any arguments:
- Very specific: line 37
If --validate reports broken URLs (marked with ✗), fix them by editing the relevant .sources.json file:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Update Agent & Cloud Metadata
Refresh icons and metadata/stats for agents and cloud providers in manifest.json.
When to use
Run this when:
- An agent or cloud provider's logo changes
- An icon URL breaks (404 or stale redirect)
- A new agent or cloud is added without an icon
- GitHub star counts need refreshing
- Agent repo info changed (license, language)
- You want a full metadata audit
- You need to validate that all source URLs are still reachable
Arguments
--agent <id>— Update only the specified agent (e.g.--agent openclaw).--cloud <id>— Update only the specified cloud (e.g.--cloud hetzner).--agents-only— Only process agents, skip clouds.--clouds-only— Only process clouds, skip agents.--icons-only— Only refresh icons, skip GitHub metadata.--stats-only— Only refresh GitHub stats, skip icon downloads.--validate— Check all source URLs are reachable without downloading. Exits with code 1 if any are broken.--dry-run— Print what would change without writing files.
Procedure
Run the update script, passing through any arguments:
bun run .claude/skills/update-metadata/update.ts [arguments]Fixing broken sources
If --validate reports broken URLs (marked with ✗), fix them by editing the relevant .sources.json file:
- Agent sources:
assets/agents/.sources.json - Cloud sources:
assets/clouds/.sources.json
Each entry maps an id to { "url": "...", "ext": "png" }. Update the url to a working icon source (apple-touch-icon, GitHub org avatar, or favicon), then re-run the script without --validate to download and update everything.
Review the output, then commit the changed files (manifest.json, .sources.json files, and any updated icon files).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

