godot-mechanic-revival — Claude Code skill
godot-mechanic-revival — a skill for Claude Code and five other platforms covering the full player mortality loop: progress-index checkpoints, soul graves, ghost mode, I-frames, and death analytics.
LGPL-3.0 321 installs ★ 983 updated 2026-10-16
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a claude-codeWhat godot-mechanic-revival does
The skill defines a mandatory script execution order for Godot's death cycle, starting with revival_global_manager.gd as an Autoload singleton that owns the player_died and player_respawned signals, through to revival_checkpoint_persistence.gd, which writes the world-progress bitmask to user:// the moment a shrine is activated.
The script set covers each stage: revival_state_reset_guard.gd zeroes velocity and angular_velocity before teleport, revival_health_restitution.gd grants I-frames on revive, and optional layers handle soul graves, collision-layer swapping for ghost mode, and JSON death telemetry. revival_checkpoint_validator.gd uses a progress_index export to block checkpoint downgrades when a player backtracks to an earlier area.
Skipping the 1–2s respawn delay or hardcoding checkpoint coordinates are treated as explicit errors — the skill documents what breaks and which script fixes it. Death coordinates and cause are logged per-session so you can export them to a heatmap tool for difficulty balancing.
What it helps with
- Add a fade-out death delay so the player isn't snap-teleported to the last shrine
- Persist the active checkpoint to
user://so a crash doesn't roll back progress - Spawn a soul grave at the death location for a corpse-run retrieval mechanic
- Grant I-frames on revive to prevent instant-death loops near hazards
- Log per-death telemetry — position, cause, timestamp — for level balancing
Example prompts for the agent
- Implement the full Godot death loop with shrine checkpoints, screen fade, and I-frames on respawn
- Add a soul grave that spawns at the player's death coordinates and can be retrieved
- Wire up
revival_death_analytics.gdto record death cause and position to a JSON file
How to install godot-mechanic-revival
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a claude-code2Manually: put the files in place
~/.claude/skills/godot-mechanic-revival/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/godot-mechanic-revival/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a codex2Manually: put the files in place
.agents/skills/godot-mechanic-revival/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a cursor2Manually: put the files in place
.cursor/skills/godot-mechanic-revival/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thedivergentai/Game-Dev-Agentic-Skills skills/godot-mechanic-revival2Manually: put the files in place
.github/skills/godot-mechanic-revival/SKILL.md1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a gemini-cli2Platform CLI
gemini skills install https://github.com/thedivergentai/Game-Dev-Agentic-Skills --path skills/godot-mechanic-revivalManually: put the files in place
.devin/skills/godot-mechanic-revival/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about godot-mechanic-revival
How do I install godot-mechanic-revival in Claude Code?
Run npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-mechanic-revival -a claude-code. The skill file lands at ~/.claude/skills/godot-mechanic-revival/SKILL.md.
What does the godot-mechanic-revival skill do?
It provides a structured set of Godot scripts and rules for a complete player death cycle: progress-index shrine checkpoints, world-state persistence to user://, I-frames after respawn, and optional soul grave and ghost-mode layers.
Why does the skill forbid queue_free() on the player node at death?
Freeing the node breaks UI references and any enemy scripts pointing at the player. The correct approach is to disable processing and hide the mesh, then revive the existing instance in place.