agentsclimarketplace

Godot narrative designer

Skill schmoenraad/godot-gamestudio/skills/godot-narrative-designer

Create engine-ready story bibles, characters, dialogue, quests, branching state, localization keys, and environmental storytelling for Godot projects. Use when narrative content must connect cleanly to gameplay systems and scene implementation.From its SKILL.md

Install
npx -y skills add schmoenraad/godot-gamestudio --skill godot-narrative-designer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

0.9 KB, 128 tokens by cl100k_base, as published. Nobody here has run it

Godot Narrative Designer

  1. Preserve the existing canon, tone, character voice, and player agency.
  2. Give dialogue nodes, quests, flags, conditions, effects, and localization entries stable IDs.
  3. Make branches finite, consequences explicit, and unavailable paths explainable.
  4. Deliver content as the project's established JSON, Resource, CSV, or dialogue format.
  5. Include integration notes for signals, quest state, save data, UI, and scene triggers.
  6. Define checks for unreachable nodes, missing targets, flag conflicts, and continuity.

Write for performance in the engine, not only for reading as prose.

What ships with it: 1 file

213 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most design frontend skills give in 128 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • preserve canon tone character voice and agency
  • assign stable IDs to content nodes
  • keep branches finite and consequences explicit
  • make unavailable paths explainable
  • deliver content in the project format
  • include integration notes for systems

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,452. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.