open-knowledge-pack-worldbuilding

Name: open-knowledge-pack-worldbuilding
Author: inkeep/open-knowledge

$npx mdskill add inkeep/open-knowledge/open-knowledge-pack-worldbuilding

Manages a fiction encyclopedia with auto-stubbing and consistency checks.

Auto-stubs new entities when mentioned in project files.
Depends on OpenKnowledge MCP server and platform skill.
Flags contradictions in characters, settings, themes, and lore.
Delivers guidance through SKILL.md without cluttering templates.

SKILL.md

.github/skills/open-knowledge-pack-worldbuildingView on GitHub ↗

---
name: open-knowledge-pack-worldbuilding
version: "0.18.0"
description: "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. 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."
compatibility: "Claude Code, Claude Desktop, Claude Cowork, Claude.ai web. Requires OpenKnowledge MCP server. Installed project-local by `ok seed --pack worldbuilding`."
metadata:
  pack: "worldbuilding"
  author: "Inkeep"
  repository: "https://github.com/inkeep/open-knowledge"
---
# 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.

> Pack guidance. The platform `open-knowledge` skill still governs every markdown operation.

## 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.

More from inkeep/open-knowledge

Skill	Description
open-knowledge	Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
open-knowledge-bug-report	Use when the user reports a problem with OpenKnowledge, asks for help debugging OK, or wants to file a bug report. This skill guides the agent to capture diagnostic information via the ok bug-report CLI command.
open-knowledge-discovery	Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to share an OpenKnowledge project with collaborators, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill at `.claude/skills/open-knowledge/` whenever `ok init` runs. If the user appears to be editing markdown inside a `.ok/` project and this is the only OK skill loaded, advise them to re-run `ok init` to install the project-local skill.
open-knowledge-pack-codebase-wiki	How to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and points to the `workflow({ kind: 'wiki' })` guide for the full generate/refresh procedure. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-entity-vault	How to work in a Personal CRM project (the `entity-vault` starter pack, GBrain-compatible): a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline. Read when the project has these folders. Carries the dossier convention and entity-extraction behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-knowledge-base	How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — wired to the `workflow` MCP tool's ingest / research / consolidate kinds. Carries the pack's workflow, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-okf	How to work in an OKF starter project (the `okf` starter pack): a knowledge base that is conformant with Google's Open Knowledge Format (OKF) from commit one — `concepts/`, `references/`, `notes/`, a reserved `index.md` navigation hub, and a reserved `log.md` change history. Read when the project has these folders + reserved files. Carries the OKF conventions (non-empty `type` on every non-reserved doc; reserved files carry no frontmatter) as guidance, not enforcement. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-plain-notes	How to work in a Plain Notes project (the `plain-notes` starter pack): a flat notes/ folder plus a daily/ journal. The 'I just want to write' layout. Read when the project has these folders. Carries the linking habit and daily-entry behavior so templates and folder descriptions stay minimal. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-software-lifecycle	How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.
open-knowledge-pack-writing-pipeline	How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.