godot-dialogue-system — Claude Code skill for Godot dialogue
A skill for branching dialogue in Godot: Resource-based graphs, portraits, gated choices, typewriter reveal.
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a claude-codeWhat godot-dialogue-system does
This skill hands the agent working patterns for dialogue in Godot: a conversation tree stored as a Resource, separate nodes for lines and choices, character portraits, gates on flags and quests, translation keys, voice acting. Useful when you are building an RPG, a visual novel, or any game where the story forks.
Inside is a script catalog plus a decision tree. The golden path is Resource Autoload: dialogue_resource.gd, dialogue_manager_singleton.gd, dialogue_ui_controller.gd, typebox_effect.gd. A JSON graph engine (dialogue_engine.gd) covers external writers and spreadsheets, and there are supporting scripts for gameplay events, condition validation, portraits, and choice logging. Pick one runtime engine. Running the Resource manager next to the JSON engine is asking for trouble.
The typewriter effect tweens visible_ratio or visible_characters, and skip input must finish the line at once. The skill bans a Timer per character and bans hardcoded line text in GDScript, because that breaks localization. Dialogue cursor state lives in the manager, not the UI node, so a scene change does not drop the player's progress. The license is LGPL-3.0, which is worth checking against your own project's license.
What it helps with
- build a branching conversation with player choices
- hide lines the player has not unlocked yet
- add a typewriter reveal with click-to-skip
- move line text into translation keys
- tie a line to a quest flag or stat gate
Example prompts for the agent
- build a Resource dialogue graph for the merchant scene
- gate this reply so it only shows after the quest is turned in
- wire typebox_effect with click-to-skip on the RichTextLabel
How to install godot-dialogue-system
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a claude-code2Manually: put the files in place
~/.claude/skills/godot-dialogue-system/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/godot-dialogue-system/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a codex2Manually: put the files in place
.agents/skills/godot-dialogue-system/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a cursor2Manually: put the files in place
.cursor/skills/godot-dialogue-system/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thedivergentai/Game-Dev-Agentic-Skills godot-dialogue-system2Manually: put the files in place
.github/skills/godot-dialogue-system/SKILL.md1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a gemini-cli2Platform CLI
gemini skills install https://github.com/thedivergentai/Game-Dev-Agentic-Skills --path skills/godot-dialogue-systemManually: put the files in place
.devin/skills/godot-dialogue-system/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -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-dialogue-system
How do I install godot-dialogue-system in Claude?
Run npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-dialogue-system -a claude-code. The skill lands at ~/.claude/skills/godot-dialogue-system/SKILL.md.
What does godot-dialogue-system do?
It gives the agent patterns for Godot dialogue: Resource-based graphs, choices, portraits, flag conditions, localization, and voice acting.
Which dialogue engine should I use?
Use the Resource Autoload path for .tres graphs kept in the repo, and the JSON engine when writers work from spreadsheets. One runtime engine at a time.