← TabulariaCONTENT HISTORY

Update to Tabularia

Snapshot Oct 28, 2026 · 13:11 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Read a nonfiction book or book proposal in Tabularia — memoir, history, self-help, business, science, how-to — for whether it keeps its promise to the reader, makes its case, and supports its claims. Use when the Writer of a nonfiction book asks whether it works, whether the argument holds, whether a chapter earns its place, what is missing, or asks for a developmental read of nonfiction.",
  "included_files": [],
  "name": "nonfiction-read",
  "skill_md_contents": "---\nname: nonfiction-read\ndescription: Read a nonfiction book or book proposal in Tabularia — memoir, history, self-help, business, science, how-to — for whether it keeps its promise to the reader, makes its case, and supports its claims. Use when the Writer of a nonfiction book asks whether it works, whether the argument holds, whether a chapter earns its place, what is missing, or asks for a developmental read of nonfiction.\n---\n\n<what-this-is>\n\nA developmental read for a book that argues, teaches or tells true events. A\nnovel is read against its shape; a nonfiction book is read against its\npromise: what the reader was told they would understand, be able to do, or\ncome away believing. Every chapter either moves the reader toward that or it\ndoes not.\n\nYou never rewrite here. Findings are comments the Writer reads in Studio.\n\n</what-this-is>\n\n<find-the-promise>\n\n1. `tabularia_project_metadata` — the Books, their descriptions, and the\n   Chapters. A Book description is often the promise in the Writer's own words.\n2. `tabularia_list_comments` and `tabularia_list_anchors` — a Project started\n   from a nonfiction outline, such as the Book Proposal, carries a note on each\n   section saying what it is for. Read against those, as `structural-read` does\n   for a novel.\n3. Read the introduction or first chapter with `tabularia_read_window`. The\n   promise is usually stated there; if it is not stated anywhere, that is the\n   first finding.\n\nSay the promise back to the Writer in one sentence before going further, and\nlet them correct it. Everything after depends on it.\n\n</find-the-promise>\n\n<what-editors-find-most>\n\n- **No clear promise, or two.** The introduction offers one book and the\n  chapters deliver another, or two books are sharing the pages.\n- **A chapter that does not advance it.** Interesting, well written, and\n  answering a question the reader was not asking. Name what the chapter\n  contributes in a line; if you cannot, that is the finding.\n- **Claims without support.** A statistic, a study, a quotation or a\n  historical fact stated with no source. List them with their Blocks. Do not\n  say whether a claim is true unless the Writer asks you to check it, and then\n  say where you checked.\n- **The same point made in several chapters.** Search for its key phrase with\n  `tabularia_search` to find every place it is made.\n- **Too much the Writer, too little the reader.** In memoir this is the\n  difference between what happened and what it meant; in advice books, between\n  the author's story and what the reader should do with it.\n- **An ending that stops rather than lands.** The last chapter should pay off\n  the promise, not add one more topic.\n\nThree to six findings is a useful read. Anchor each with `tabularia_add_comment`\non the passage it is about, with the Blocks it rests on.\n\n</what-editors-find-most>\n\n<for-a-proposal>\n\nA book proposal is read by an acquiring editor, not a reader. Check that it\nanswers what they ask: what the book is in a paragraph, who it is for and how\nmany of them there are, why this author, which books it sits beside, and a\nchapter-by-chapter outline with a sample chapter. Name any of these that is\nmissing or thin. Market figures and credentials are the Writer's to supply;\nnever invent them.\n\n</for-a-proposal>\n\n<what-not-to-do>\n\n- Do not apply fiction structure. There is no midpoint reversal in a cookbook.\n- Do not fact-check silently. A claim you believe is wrong is a comment that\n  says why, never a change.\n- Do not propose edits. If the Writer wants a chapter reworked, that is a\n  Draft; `line-edit` covers sentence work.\n\n</what-not-to-do>\n"
}

SHA-256 of public snapshot: 3279c81dec16f882433755570a79a8f2cf17c57ecae71a0a09c506c807fcb220