Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →danjdewhurst/plot-structure
This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "act structure", "story arc", "plot outline", or wants to plan and manage the narrative structure of a story.
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
and 12 more in the full report
11 fixed6 passed either way5 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to export a Mermaid timeline diagram using story diagram timeline. What directory rule must be followed regarding where to save generated diagrams relative to entity folders?
| Checked | Without skill | With skill |
|---|---|---|
| Requires generated diagrams to be saved outside entity folders. | Missed | Passed |
The instructions your model reads when the skill loads.
Plan and manage story arcs, plot points, setups and payoffs, and the narrative timeline. Each arc is a markdown file in plot/arcs/, and plot/timeline.md holds the planned events and backstory in story order. The plot index lists all arcs, their status, and theme coverage.
A story project must already exist (created via the story-init skill). Verify by checking for story.md in the project root.
story.md for genre, themes, and form (novel, novella, novelette, short-story, flash, serial, picture-book, chapter-book). For short-story and flash, use references/short-story-form.md instead of a multi-act beat sheetreferences/structure-models.md for available structuresreferences/snowflake.md on top of the chosen structureplot/_index.md frontmatter structure fieldbeat (see Recording Beats on Chapters)story reindex ., story wordcount . --write, and story check .A chapter's optional beat frontmatter field names the beat-sheet beat it delivers, so story grid, story context, and the codex can show the structure chapter by chapter.
plot/_index.md, as references/structure-models.md spells them (Inciting Incident, Midpoint, All Is Lost, Ten (Twist)), or the writer's own label when they adapt the model. The field is free text, and the CLI checks only that it is text, not that it names a known beatstory add chapter '{Title}' --number {N} --beat '{Beat}', or add beat: {Beat} to an existing chapter's frontmatter. Quote a value that looks like a number or contains : or # (beat: "Try/Fail #2"), since an unquoted # starts a commentstory validate warns beat-too-long above 60 characters. What happens in the beat goes in the chapter's ## Outlinebeat off the chapters between beats. A beat that runs over several chapters, such as Fun and Games, goes on the chapter where it startsstory reindex ., story wordcount . --write, and story check ., then story grid .. Once any chapter has a beat, the grid shows a (beat) row above its hook and outcome rows. Check each beat against its position in the model (a Midpoint near the middle chapter, All Is Lost near three quarters of the way through): beats that bunch up, or a long run of chapters with none, are where a middle sagsstory.md for themesplot/_index.md for existing arcscharacters/_index.md to understand available characterstest cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.