Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →danjdewhurst/revision-continuity
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline consistency, line edit, developmental edit, polish a draft, or prepare existing story material for the next revision pass.
Passed 19 of 20 test cases with the skill, and 5 of 20 without it.
and 20 more in the full report
14 fixed5 passed either way1 still failing0 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
My story project is not tracked in git, and I declined to initialize a git repo. I want to save a snapshot named pre-beta-edit before starting line edits. A teammate suggested copying the whole project folder into project_backup/. How should I create this snapshot using the CLI tools?
| Checked | Without skill | With skill |
|---|---|---|
| The output recommends running story snapshot pre-beta-edit --path . to create the snapshot in .snapshots/. | Missed | Passed |
| The output warns against manually copying the project into a subfolder where scanner commands would scan the duplicate files. | Missed | Passed |
The instructions your model reads when the skill loads.
Revise existing Story Skills projects without losing continuity. Use this skill for targeted chapter edits, continuity audits, developmental revision, line edits, and pre-flight checks before drafting the next chapter.
A story project must already exist. Verify by checking for story.md in the project root, then run or inspect story report . when CLI access is available. Read story.md language (a missing field means en) and write every revision in that language; when a story prose or story voices check is reported as skipped for the language, do that check by reading.
Track a full revision as a ladder of named passes in story.md
revision-passes, so the work happens in order (big structural changes
before polishing sentences that may be cut) and survives between sessions:
story passes . --init # writes the default ladder, keeping existing entries
story passes . # checklist with the checks each pass runs
story passes . --start pacing # mark a pass in-progress
story passes . --done pacing # mark it done
story next . # with story status revising, recommends the next unfinished pass
The default ladder is structure, character, theme, continuity,
pacing, line, copyedit, proof. Each entry is {pass, status} with
status pending, in-progress, or done; add a custom kebab-case pass
(fact-check, length, sensitivity) with story passes . --start <name>, which
appends it as in-progress. The checks per pass, as story passes .
prints them, and the checklists in references/pass-checklists.md that
each pass works through:
| Pass | Checks | Checklists |
|---|---|---|
structure | story timeline ., story pacing ., story diagram arcs | Reverse outline, pacing waveform, removability audit |
character | story voices ., story knowledge <id> --at <chapter>, story diagram relationships | Developmental revision (motivation, arcs) |
theme | story report . | Theme audit |
continuity | story continuity ., story clues ., story links . | Continuity audit, reveal economy, fact check |
pacing | story pacing . | Pacing waveform |
line | story prose ., story voices . | Line edit (the line-editing skill) |
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.