storybuilder-bible-audit
Skill2 starsChanged 4 months agoMITView on GitHub
Load the Story Bible You will be auditing an early-stage [story_bible] for logical consistency and plot plausibility. The story bible contains a premise, pitch, character list, and worldbuilding elements for a story concept. Prompt the user to provide a [story_bible] or use the /storybuilder-bible skill to generate one. Your Task Identify logical inconsistencies, implausible plot elements, character-world mismatches, and worldbuilding conflicts that would undermine the story's internal coherence. Perform the following six audit checks: Does the core premise hold together…
In this repository23 other files it gives its agents.
- book-market-researchSkill
- chapter-scene-workshopSkill
- create-sceneSkill
- create-story-bibleSkill
- deep-pov-workshopSkill
- dev-editor-recommendationsSkill
- dialogue-workshopSkill
- line-editing-workshopSkill
- one-line-elevator-pitchSkill
- query-letter-workshopSkill
- sentence-workshopSkill
- show-dont-tell-workshopSkill
- story-architectSkill
- storybuilder-bibleSkill
- storybuilder-brainstormSkill
- storybuilder-character-sheetSkill
- storybuilder-dev-editorSkill
- storybuilder-improvement-planSkill
- storybuilder-prohibited-wordsSkill
- storybuilder-sceneSkill
- storybuilderSkill
- strong-writing-checklistSkill
- writing-coachSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Do the characters' roles, goals, and capabilities make sense given the worldbuilding?
- Distinctive: line 20
Do character relationships and motivations align with the premise and pitch?
- Distinctive: line 25
Do the world elements support and enable the premise?
- Distinctive: line 27
Do geography, technology level, social structure, and magic/tech rules work together logically?
- Distinctive: line 57
Before writing your final audit, use a [scratchpad] to systematically work through each section of the [story_bible] using the following …
- Distinctive: line 62
Check each audit category systematically Note any contradictions, implausibilities, or logic gaps For each issue, think through what …
- Distinctive: line 75
If a section has no issues, state "No significant issues identified in this category." In Section 6 (Specific Fixes), provide 3-6 concrete, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Load the Story Bible You will be auditing an early-stage [story_bible] for logical consistency and plot plausibility. The story bible contains a premise, pitch, character list, and worldbuilding elements for a story concept. Prompt the user to provide a [story_bible] or use the /storybuilder-bible skill to generate one.
Your Task Identify logical inconsistencies, implausible plot elements, character-world mismatches, and worldbuilding conflicts that would undermine the story's internal coherence.
Perform the following six audit checks:
- Premise Logic Check:
Does the core premise hold together internally? Are the central conflict and stakes consistent with the stated world rules? Does the basic "what if" or setup make logical sense?
- Character-World Fit:
Do the characters' roles, goals, and capabilities make sense given the worldbuilding? Does any character's existence contradict stated world rules? Do character relationships and motivations align with the premise and pitch? Are character power levels, social positions, or abilities plausible in this world?
- Worldbuilding Coherence:
Do the world elements support and enable the premise? Are there conflicting world rules stated in different sections? Do geography, technology level, social structure, and magic/tech rules work together logically? Are there internal contradictions in how the world operates?
- Plot Setup Plausibility: Given the pitch, are there obvious logistical impossibilities? Are there character motivation gaps that would prevent the story from starting? Does the antagonist's power/position make sense relative to the protagonist's starting point? Is the inciting incident plausible given the world and characters?
- Early-Stage Convenience Flags: Does the premise rely on unlikely coincidences without justification? Are there characters who exist purely to solve plot problems with no other narrative purpose? Does the protagonist have suspiciously perfect allies or resources that feel contrived? Are there "because the plot needs it" elements with no in-world logic?
- Specific Fixes: For each major issue identified, provide concrete suggestions to resolve the problem while preserving the core pitch and appeal of the story. For each issue you identify, use this format: [Category] Issue: [Brief description of the problem] LOGIC BREAK: [Explain exactly what breaks the internal logic] References: [Specific premise/pitch elements, characters, or worldbuilding details involved] FIX: [Concrete suggestion to resolve the issue]
Here is an example of a well-formatted issue: Premise Issue: Protagonist is a street thief who "must save the kingdom." LOGIC BREAK: No clear path from thief skills to kingdom-saving capability. Why would kingdom authorities trust or empower a criminal? How does pickpocketing translate to stopping existential threats? References: Protagonist background, main plot premise FIX: Give them a specific rare skill (lockpicking ancient magical vaults that only respond to "pure intent," which their poverty-driven theft qualifies as) that makes them uniquely qualified, OR change their backstory to ex-royal guard framed as a thief, giving them both skills and motivation.
Scratchpad Before writing your final audit, use a [scratchpad] to systematically work through each section of the [story_bible] using the following template:
First, identify the core premise and main pitch List all characters and their stated roles/capabilities List all worldbuilding rules and elements Check each audit category systematically Note any contradictions, implausibilities, or logic gaps For each issue, think through what specifically breaks and how it could be fixed
Report Structure Structure your final audit report with these six sections: Section 1: Premise Logic Assessment Section 2: Character-World Mismatches Section 3: Worldbuilding Conflicts Section 4: Setup Plausibility Issues Section 5: Early Convenience Flags Section 6: Specific Fixes
If a section has no issues, state "No significant issues identified in this category." In Section 6 (Specific Fixes), provide 3-6 concrete, actionable suggestions that address the most critical problems while preserving the story's core appeal.
Final Output Your final output should contain only the six-section audit report, not the [scratchpad]. Each issue should be clearly formatted with the structure shown in the example above.
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.

