agentleFS
chianglianglinchianglianglin/novel-writer/.claude/skills/novel-wiki/SKILL.md

novel-wiki

Skill0 starsChanged 6 months agoMITView on GitHub

Browse and edit the story wiki (characters, plot, world, themes). View current state, add entries, or search for specific facts.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. 0msm0/novel-wiki-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if --wiki <path> was passed as an argument.

    line 12
  2. Distinctive:

    Read the following files using the Read tool:

    line 16
  3. Very specific:

    If a file does not exist, note it as [file not found].

    line 23
  4. Distinctive:

    Ask the user what they'd like to do:

    line 59
  5. Very specific:

    Ask which section and what the existing text looks like (partial match is fine).

    line 89
  6. Very specific:

    Read the file, find the matching line, ask the user what it should be changed to.

    line 90
  7. Very specific:

    Use the Edit tool to make the change.

    line 91
  8. Distinctive:

    Ask for a keyword. Search all wiki files for lines containing the keyword (case-insensitive).

    line 96
  9. Distinctive:

    Search all wiki files for lines containing the keyword (case-insensitive).

    line 97
  10. Very specific:

    Run /novel-setup first if the wiki directory does not exist.

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Novel Wiki

Browse, search, and edit the story wiki for your novel project.

Step 1: Determine wiki directory

Check if --wiki <path> was passed as an argument. If not, default to ./wiki/.

Step 2: Read all wiki files

Read the following files using the Read tool:

  • <wiki_dir>/project.md — title, genre, premise
  • <wiki_dir>/characters.md — character roster
  • <wiki_dir>/plot.md — plot events log
  • <wiki_dir>/world.md — world-building facts
  • <wiki_dir>/themes.md — themes and motifs

If a file does not exist, note it as [file not found].

Step 3: Display the wiki

Print the wiki contents in a clean, readable format:

═══════════════════════════════════════════
  STORY WIKI
═══════════════════════════════════════════

PROJECT
-------
[project.md content]

CHARACTERS
----------
[characters.md content]

PLOT EVENTS
-----------
[plot.md content]

WORLD FACTS
-----------
[world.md content]

THEMES
------
[themes.md content]

═══════════════════════════════════════════

Step 4: Offer actions

Ask the user what they'd like to do:

  1. Add an entry — add a new character, plot event, world fact, or theme
  2. Edit an entry — modify an existing entry
  3. Search — find entries matching a keyword
  4. Done — exit

If "Add an entry":

Ask:

  • Which section? (characters / plot / world / themes)
  • What is the entry text?

Append to the appropriate file. Format:

- **[entry text]**

Or if the user wants to add under a specific chapter heading, prompt for the chapter number and append:


## After Chapter [N]

- [entry text]

Confirm: Added to <section>. Updated <wiki_dir>/<file>.

If "Edit an entry":

Ask which section and what the existing text looks like (partial match is fine). Read the file, find the matching line, ask the user what it should be changed to. Use the Edit tool to make the change. Confirm: Updated entry in <section>.

If "Search":

Ask for a keyword. Search all wiki files for lines containing the keyword (case-insensitive). Display matching lines with their file source and line number.

If "Done":

Exit the skill.

Notes

  • Run /novel-setup first if the wiki directory does not exist.
  • The wiki is plain markdown — you can also edit the files directly in any text editor.
  • /novel-write automatically appends new facts to the wiki after each chapter.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.