agentleFS
design1onlinedesign1online/author-it/skills/storybuilder-improvement-plan/SKILL.md

storybuilder-improvement-plan

Skill2 starsChanged 4 months agoMITView on GitHub

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…

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Never change the original text.

    line 41

≈ “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.

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

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.

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.