← TabulariaCONTENT HISTORY
WHAT CHANGED
Update to Tabularia
Snapshot Oct 28, 2026 · 13:11 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Tabularia and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Find contradictions across a Tabularia Manuscript — a character's eye color that changes, a wound that heals too fast, a date that does not survive the next chapter. Use when the Writer asks about continuity, consistency, plot holes, timeline problems, whether the book still matches their character Sheets, or whether they have contradicted themselves. Asked for a thorough, full or complete check, or one before submission, read the whole book as well.",
"included_files": [],
"name": "continuity-check",
"skill_md_contents": "---\nname: continuity-check\ndescription: Find contradictions across a Tabularia Manuscript — a character's eye color that changes, a wound that heals too fast, a date that does not survive the next chapter. Use when the Writer asks about continuity, consistency, plot holes, timeline problems, whether the book still matches their character Sheets, or whether they have contradicted themselves. Asked for a thorough, full or complete check, or one before submission, read the whole book as well.\n---\n\n<what-this-is>\n\nContinuity work is search, not reading. The contradiction is almost never in the\npassage the Writer is looking at — it is in the chapter they wrote four months\nago and have not opened since.\n\nSo the ordinary check does not read the book front to back looking for\nproblems. It finds the facts, then checks each one everywhere it appears.\n\nIn nonfiction the facts are different and the job is the same: a person's\nname, title or dates given two ways, a figure quoted differently in two\nchapters, an event placed in two different years. Build the list from those.\n\n</what-this-is>\n\n<two-depths>\n\n**Quick** is the default, and it is everything below up to the thorough check:\nstart from what the Project tracks, then search. It is fast and it is exact\nabout what it covered, but it can only check a fact somebody thought to search\nfor. A door locked in chapter three and walked through in chapter forty, with\nno Sheet or Timeline mentioning the door, never comes up.\n\n**Thorough** reads the whole Manuscript in order as well, and catches the facts\nnobody listed. Run it when the Writer asks for a thorough, full or complete\ncheck, or says the book is going to an editor, agent or printer. Before\nstarting, tell them it reads every chapter and on a novel takes a long while\nand a good deal of their usage, and go ahead only once they have said yes.\n\nWhen you finish a quick check, say in one line what it cannot catch and that a\nthorough check would, so the Writer can choose it knowingly.\n\n</two-depths>\n\n<start-from-what-the-project-already-tracks>\n\n1. `tabularia_list_sheets` — the characters, places and whatever else the\n Project keeps beside the book, each with its aliases, template fields and\n notes. Start here. This is the Writer's own record of what is true, so it is\n at once the fact list you are about to check and the thing the prose has to\n agree with. A Sheet that disagrees with the prose is as strong a finding as a\n Timeline that does, and for the same reason: the Writer wrote both.\n2. `tabularia_list_timelines` — the Writer's own Timelines and markers. These are\n the dates and sequences they have already decided matter. A Timeline that\n disagrees with the prose is the strongest kind of finding, because the Writer\n wrote both.\n3. `tabularia_list_anchors` — the Outline, and the point and range Anchors where\n they have marked things.\n4. `tabularia_project_metadata` — how many Books, and whether this is a Series.\n A continuity check across a Series is a different scale of job; say so before\n starting one.\n\n</start-from-what-the-project-already-tracks>\n\n<then-search>\n\n`tabularia_search` finds wording across every open Project and answers with the\nBlock index and surrounding context of every occurrence. That is the tool for\nthis entire job.\n\nThe answer is a page of matches, and it tells you which page it is: read\n`matchCount` and `truncated` rather than counting the list. When `truncated` is\ntrue there are more, and you ask again with a later `from`. A name you report\nas appearing eleven times when the first page held eleven of forty is the\nmistake this whole skill exists to avoid.\n\nBuild a list of checkable facts first, then search each one:\n\n- **Proper nouns** — every character, place, ship, house, spell. Search the name\n and read every match, not the first three. Search every alias its Sheet\n carries as well as the name: a character the book calls Mira in half its\n chapters and the Ravener in the other half is one search that finds half the\n passages, and the count you report is wrong for exactly the character it\n matters most for.\n- **What the Sheets already assert** — every filled template field is a claim\n the prose can break. An age, a home, a rank, who someone is married to. Check\n each against the passages that mention it.\n- **Physical facts** — eye and hair color, scars, height, age, injuries. These\n are where contradictions actually live.\n- **Time and sequence** — days of the week, seasons, \"three days later\", ages,\n how long a journey takes. Check these against the Timelines.\n- **Objects and their state** — the letter that was burned, the sword that broke,\n the door that was locked.\n- **Relationships and what people know** — who has met whom, who knows the\n secret, who was in the room.\n- **Where everyone is** — a character in two places on the same day, or in a\n scene after they left town or died.\n- **Days and weather** — a named weekday that cannot follow the last one, a\n storm in one scene and a clear sky in another on the same afternoon.\n- **The past as recalled** — a character remembering two earlier events in a\n different order, or differently, from how the book told them.\n- **Spelling** — a name spelled two ways. Search the variants you can think of,\n not just the Sheet's spelling.\n\nCopy editors find chronology the most common slip, and it is as frequent in a\nsimple timeline as a complicated one. Check ages against the dates the past is\nset at, not just against each other.\n\nWhen a Writer names a specific worry, start there and widen only if it is clean.\n\n</then-search>\n\n<the-thorough-check>\n\nDo the quick check first. Its Sheets, Timelines and search results are the\nstart of the ledger below, and a contradiction it already found does not need\nfinding twice.\n\nThen read with `tabularia_read_window`, 120 Blocks at a time from Block 0,\nuntil it reports no more Blocks. Do not use `tabularia_read_manuscript` for\nthis: a novel in one answer is more than you can hold and check at once, and\nthe window's Block indexes are what each finding cites.\n\nAs you read, keep a ledger: every fact the prose establishes, each with the\nBlock index where it was established. The kinds of fact are the ones the search\nlist above names, plus anything the story hangs on that no Sheet records.\nCheck each new statement against the ledger before adding it. When one\ndisagrees, search for the fact with `tabularia_search` before reporting it: a\nthird passage often settles which of the two is the slip, or shows the change\nwas deliberate.\n\nKeep the ledger to facts, not summary. A ledger that retells the plot fills up\nby the middle of the book and stops being checkable.\n\nReport as the quick check does, and add how far you read: from Block 0 to the\nlast Block, or, if you stopped, where and why. A thorough check that quietly\nread half the book is worse than a quick one, because the Writer believes it.\n\n</the-thorough-check>\n\n<what-counts-as-a-finding>\n\nA finding needs **two passages that cannot both be true**, and you must cite\nboth, with their Block indexes. \"Check Mira's age\" is not a finding. \"Block 88\nmakes Mira nineteen at the siege; Block 412 puts the siege six years after her\nsixteenth birthday, which makes her twenty-two\" is.\n\nA Sheet counts as one of the two. Cite it the way you would cite a passage —\nthe Sheet's name and the field — and say plainly that the Sheet may be the side\nthat is out of date, because a Writer who changed a character's age in the\nprose and never went back to the Sheet has not made a continuity error.\n\nFour things that look like findings and are not:\n\n- **Deliberate contradiction.** An unreliable narrator, a lying character, a\n faulty memory. If a contradiction sits with a character who has reason to lie,\n say that you have noticed it and that it may be intended.\n- **A Draft disagreeing with the Base.** Check `tabularia_list_drafts` before\n reporting. Two versions of a passage are meant to differ — that is what a Draft\n is. Only compare wording inside one composition.\n- **A name the Sheet already knows.** An alias listed on a Sheet is the same\n person under another name, not a slip and not a second character. Read the\n Sheets before reporting any name as inconsistent.\n- **Revision in progress.** If the Writer has an open Review Change or a\n proposal over one of the two passages, the contradiction may already be on its\n way out. `tabularia_list_review_changes` tells you.\n\n</what-counts-as-a-finding>\n\n<how-to-deliver>\n\nAnchor each finding with `tabularia_add_comment` on the passage you think is\nwrong — usually the later one — and name the other passage in the body with its\nBlock index so the Writer can jump to it.\n\nA Sheet is not a passage and cannot carry a comment, so anchor a Sheet finding\non the prose it disagrees with and name the Sheet and field in the body.\n\nDo not propose the fix. Which of two passages is wrong is a story decision, and\nthe wrong one is often the one that reads better. That holds for the Sheets as\nwell: do not correct one, and do not fill in a missing one, unless the Writer\nasks. If they do, `tabularia_write_sheet` is a proposal like any other, and you\nread the Sheets first so you update the one that is there instead of making a\nsecond.\n\nWhen the Writer's worry is a sequence rather than a contradiction — \"does the\nwar actually happen in the order I think it does?\" — build them a Timeline\ninstead of a list. `tabularia_create_timeline` makes one, and\n`tabularia_add_timeline_marker` marks each passage you found. They can then pin\nit as a Working Scope and read only those passages in order, which answers the\nquestion far better than anything you could write in the chat. Reuse a Timeline\nthat already carries the title rather than making a second.\n\nReport the sweep in the chat as well: what you searched for, how many matches\neach term had, what came back clean, and which depth this was. A Writer needs to know the check was\nthorough, and \"no contradictions found\" means nothing without the list of what\nwas actually checked.\n\n</how-to-deliver>\n"
}SHA-256 of public snapshot: c0bb787b0fea0517339d72e82df86b4275ec6b4c12ba3507307b9c0f2735ba8d