agentsclimarketplace

Storybuilder improvement plan

Skill design1online/author-it/skills/storybuilder-improvement-plan

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-improvement-plan

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.0 KB, 847 tokens by cl100k_base, as published. Nobody here has run it

Current Chapter Prompt the user to provide the [chapter] text or use the /storybuilder-first-draft skill if they don't have one but can provide a [story_bible] instead.

Previous Chapter Prompt the user to provide the [previous_chapter] text unless this is the first chapter.

Scene Brief Prompt the user to provide the [scene_brief] for this chapter or use the /storybuilder-scene skill to generate one if they don't have one.

Improvement Plan Given the above [chapter], I want you to critique the chapter on a line-by-line basis and find ways to improve the chapter. Give specific examples. Here are a few things to look out for: -Chapter Flow: Identify internal structure (hook, tension rise, end-of-chapter promise) -Rhythm Check: Highlight slow pacing (exposition/info-dumps). If needed, suggest scene breaks or cuts. -Show vs Tell: Highlight areas that are telling instead of showing, or not demonstrating good deep point of view for the character. Highlight exposition blocks for sensory or active-scene rewrites. -Cliches: Highlight common cliches, and over reliance on metaphors, and other signs of bad writing on the sentence level. -Adverbs: Identify any over-reliance on adverbs -Dialogue Tags: Identify dialogue tags that are not “said” or “asked”. Make suggestions for which ones should be changed to "said" or "asked". -Passive Voice: Flag instances of passive voice. -Zero Fluff: Highlight overly wordy sentences and paragraphs/areas where you could reduce fluff, as well as instances of mushy dialogue or descriptions Prose: Avoid purple sentences, keep reading level appropriate to the genre and target audience expecatations -Voice Check: Compare each major/recurring character’s dialogue and behavior against their established profile; flag off-character moments. -Voice Similarity: Flag characters that sound too similar in their voice/dialogue -Voice Remaining In Character: Flag characters that are speaking out of character ie. a soldier doesn't sound like a college professor (unless they are/were once a college professor) -Motivation Alignment: Ensure each action drives plot or character growth.", -Minor Characters: Verify new or returning townsfolk match previously defined traits or enrich them without contradiction. -Plot Holes: Things that are contradictory or don't make sense as a reader. -Open Questions: Note any unclear motives, logic gaps, or plot holes. -Repetition: Frequency of word usage, starting sentences with the same word, using the same word multiple times within a short amount of time. -Spelling Issues: Typos, missing words, incorrect tenses, noun/verb agreement, line and copy editing problems -Worldbuilding: Ideas, objects, systems, magic, etc that are not clearly explained how they work -Tension: There is a clear conflict or tension and the protagonist is actively making choices not pushed along by the plot -Internal Conflict: Must be present in the chapter -External Conflict: Should be present in the chapter, flag if missing -Ending: Did the text end where the scene brief said it should? If not, specify where the chapter should end. -Beginning: Did the text begin in a way that feels like a natural continuation from the previous_chapter_text? If not, specify how it should begin. -Reader Experience: Provide a 'Takeaway'—does the chapter leave readers eager for the next installment? Overall, your most important task is to identify these problem areas and highlight them as an issue with an explanation of why it was highlighted. The goal is to identify ways to make the writing and story content stronger. Once you’ve identified ways to do this, make a plan to improve the text. Give specific examples and recommendations on how to fix these issues. Respond to any fixes provided by the user with a new round of suggestions (if applicable).

IMPORTANT

Never change the original text. Highlight the issues, provide suggestions/examples of how they might be fixed, and leave the user to address the feedback you are providing and make a decision on how to handle it.

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most plan spec skills give in 847 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Prompt the user for the chapter text
  • Prompt the user for the scene brief
  • Critique the chapter on a line-by-line basis
  • Identify internal structure and flow
  • Highlight slow pacing and exposition
  • Identify cliches and overused adverbs

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.