novel-setup
Skill0 starsChanged 6 months agoMITView on GitHub
Initialize a new novel project by creating the wiki directory structure (characters, plot, world, themes). Run this once before using /novel-write.
In this repository5 other files it gives its agents.
- novel-readerSkill
- novel-researchSkill
- novel-reviewSkill
- novel-wikiSkill
- novel-writeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask the user (one message, all at once):
- Distinctive: line 22
Use Bash to create the directory:
- Very specific: line 29
Write a file at <wiki_dir>/project.md with:
- Distinctive: line 40
Create each with a template header.
- Distinctive: line 90
If any wiki file already exists, do NOT overwrite it — skip it and tell the user.
≈ “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.
Files
Novel Setup
Set up the story wiki folder for a new novel project.
Steps
1. Gather project details
Ask the user (one message, all at once):
- Novel title — working title for this project
- Genre — e.g. "epic fantasy", "noir thriller", "literary fiction", "science fiction"
- Premise — one or two sentences describing the core story idea
- Wiki directory — where to store story context (default:
./wiki/)
2. Create the wiki directory
Use Bash to create the directory:
New-Item -ItemType Directory -Force -Path "<wiki_dir>"3. Create project.md
Write a file at <wiki_dir>/project.md with:
# [NOVEL_TITLE]
**Genre:** [GENRE]
**Premise:** [PREMISE]4. Create the four wiki files
Create each with a template header. Only create files that do not already exist.
<wiki_dir>/characters.md:
# Characters
<!-- Add character entries below. -->
<!-- Format: **Name** — description, key traits, role in story --><wiki_dir>/plot.md:
# Plot Events
<!-- Add plot events in chronological order. -->
<!-- Format: **Ch. N / Scene** — what happened, consequences --><wiki_dir>/world.md:
# World Facts
<!-- Add world-building facts: geography, history, magic/tech rules, factions, customs --><wiki_dir>/themes.md:
# Themes
<!-- Add recurring themes, motifs, and symbolic elements -->5. Confirm to user
Print:
Novel project initialized.
Wiki: <wiki_dir>/
├── project.md ← title, genre, premise
├── characters.md ← character roster
├── plot.md ← plot events log
├── world.md ← world-building facts
└── themes.md ← themes & motifs
Next: use /novel-write to generate a chapter.Notes
- If any wiki file already exists, do NOT overwrite it — skip it and tell the user.
- The wiki directory is used by
/novel-writeand/novel-wiki. Keep it in the project root or pass--wiki <path>to those skills.
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
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.

