World of ClaudeCraft is a browser-based classic-style multiplayer online game with a persistent shared world that can also run locally or be controlled through a Python reinforcement-learning interface. Players can quest and raid in the online world, while developers can host it themselves and train AI agents to play. The catalogue skills, agents, instructions, hooks, and setting support workflows for interacting with and developing the game.
Borrowing it
Nothing to install: this file belongs to levy-street/world-of-claudecraft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levy-street/world-of-claudecraft/main/.claude/skills/write-game-tooltips/SKILL.mdgit clone --depth 1 https://github.com/levy-street/world-of-claudecraftWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/levy-street/world-of-claudecraft/write-game-tooltips)<a href="https://agentmods.dev/skills/levy-street/world-of-claudecraft/write-game-tooltips"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/write-game-tooltips/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/levy-street/world-of-claudecraft/write-game-tooltips"><img src="https://agentmods.dev/badge/skills/levy-street/world-of-claudecraft/write-game-tooltips.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00074 | $0.00339 |
| Opus 5 | $0.00037 | $0.00169 |
| Sonnet 5 | $0.00015 | $0.00068 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
write-game-tooltips scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Write game tooltips
Make every tooltip clear enough to understand in one read and exact enough to test.
Required workflow
- Read
docs/design/tooltip-writing.mdin full. - Read the live content definition and every runtime handler for the effect.
- List the action, target, values, timing, scaling stat, triggers, caps, and consumption rules.
- Write the English source in the order the player experiences it.
- Use resolved values for anything changed by rank, gear, talents, or specialization.
- Add or update a focused test that compares the tooltip with the combat result.
- Run the relevant tooltip, mechanic, i18n, and type checks.
Hard rules
- Never infer mechanics from the old description.
- Never claim an effect scales until the live combat path proves it.
- Never hide a trigger, cap, target limit, stack rule, cooldown reset, or resource change.
- Never repeat metadata already shown above the description unless the repetition prevents a real misunderstanding.
- Never hand-edit non-English locale overlays or generated i18n files.
- Never use flavor text in place of an exact rule.
Write the English pass first. Locale work follows the repository release workflow.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 32 lines · 74 tokens per session scan A 640517041815
write-game-tooltips is a skill published in the GitHub repository levy-street/world-of-claudecraft (2,251 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 339 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.