agentsclimarketplace

Storybuilder bible audit

Skill design1online/author-it/skills/storybuilder-bible-audit

AI skills for writers who don't want AI writing their novels for them...From the repository description

Install
npx -y skills add design1online/author-it --skill storybuilder-bible-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.3 KB, 872 tokens by cl100k_base, as published. Nobody here has run it

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:

  1. 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?

  1. 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?

  1. 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?

  1. 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?

  2. 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?

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most audit compliance skills give in 872 tokens

Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06

  • Read product marketing context before asking questionsin 29 of 960, across 11 files
  • Rank findings by severityin 29 of 960, across 22 files
  • Generate audit reportin 22 of 960
  • Run the audit scriptin 20 of 960, across 19 files
  • Generate a prioritized action plan reportin 19 of 960, across 11 files
  • Ensure one H1 per pagein 15 of 960, across 5 files
  • Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
  • Verify alt text on all imagesin 12 of 960, across 3 files
  • Determine the audit scope before startingin 12 of 960, across 4 files
  • Verify important pages allowed in robots.txtin 11 of 960, across 2 files
  • Detect business type from homepage signalsin 11 of 960, across 7 files
  • Delegate specialized tasks to subagentsin 11 of 960, across 7 files

Said here and by no other author read

  • Prompt the user to provide a story bible
  • Identify logical inconsistencies and plot implausibility
  • Perform the six audit checks
  • Use a scratchpad before writing the final audit
  • Structure the final audit report with six sections

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.