AugmentClaude

Worldbuilding

Manage fictional characters, settings, factions, and lore with automatic consistency checks.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up β€” so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/worldbuilding-inkeep/ β€” the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates β€” they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description β€” no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the β€œWhat this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

What this skill does

Worldbuilding pack β€” how to work here

This project is a fiction encyclopedia. The graph is the product: characters, settings, themes, factions, and lore that link to each other. The agent's main jobs are auto-stubbing new entities as they're mentioned and flagging contradictions. This skill holds those behaviors so templates and folder descriptions stay clean.

This skill is pack guidance. The platform /open-knowledge skill (read/write/preview/linking/grounding rules) still governs every markdown operation β€” this layers the worldbuilding conventions on top.

Folders

  • characters/ β€” one file per character (PC + NPC); frontmatter carries type, status, faction, first appearance.
  • settings/ β€” locations, regions, world-rules; frontmatter carries region, controlling faction, danger level. The "where" of the story.
  • themes/ β€” recurring narrative concerns (love, betrayal, identity). The "why." Themes work via opposition; each entry captures the theme and its tension.
  • factions/ β€” political, social, criminal, magical, religious groups. Ships faction, political-faction, and religion templates.
  • lore/ β€” history, mythology, cosmology, magic systems. Ships lore, magic-system, and historical-event templates.

Agent behaviors (the core value)

  • Auto-stub on mention. When a chapter, session log, or existing entry references a name not yet captured, stub a file in the right folder with backlinks to where it was mentioned.
  • Flag contradictions. When a character's faction (or any field) contradicts their actions in narrative, or a setting is described two ways, surface the conflict β€” in fiction a contradiction is itself a story-shaping detail worth noting, not silently "fixing."
  • Thread the graph. Link characters ↔ factions ↔ settings ↔ lore so each entry becomes a hub for everywhere it appears.
  • Do NOT add TTRPG stat-block fields (xp_awarded, etc.) β€” those belong in a future TTRPG variant.

Templates

Create with write({ document: { path, template: "<name>" } }). Templates carry only structure; section meaning is described here, not inside the document body.

Related skills