← 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": "Write a synopsis, a query letter, a pitch or back-cover copy for a Tabularia Manuscript from the book itself. Use when the Writer asks for a synopsis, query letter, pitch, logline, blurb, back-cover copy or book description, or is getting ready to submit to agents or publishers.",
  "included_files": [],
  "name": "synopsis-and-query",
  "skill_md_contents": "---\nname: synopsis-and-query\ndescription: Write a synopsis, a query letter, a pitch or back-cover copy for a Tabularia Manuscript from the book itself. Use when the Writer asks for a synopsis, query letter, pitch, logline, blurb, back-cover copy or book description, or is getting ready to submit to agents or publishers.\n---\n\n<what-this-is>\n\nThe documents a Writer needs to submit a book, written from the book rather\nthan from a summary of it. They are short, and every sentence has to be true of\nthe Manuscript: an agent who requests pages after a synopsis that promised a\ndifferent book does not request more.\n\nA nonfiction book is usually sold on a proposal rather than a query and a\nfinished manuscript; `nonfiction-read` covers what a proposal needs. For a\nscript, the logline and synopsis are part of `screenplay-read`.\n\n</what-this-is>\n\n<read-the-book>\n\n1. `tabularia_project_metadata` for the title, subtitle, series name, the Books\n   and their Chapters, and the description the Book already carries; and\n   `tabularia_statistics` for the word count. Quote that count, not your own.\n2. `tabularia_list_sheets` and `tabularia_list_comments`: the Writer's own notes\n   on who matters and what each part is for.\n3. Read the whole Manuscript with `tabularia_read_window`, 120 Blocks at a time.\n   A synopsis written from the first chapters and the last one gets the middle\n   wrong, and the middle is where the turns are.\n\nKeep, as you read, the protagonist's goal, what stands in the way, each turn\nthat changes the plan, and how it ends.\n\n</read-the-book>\n\n<what-each-one-is>\n\nAsk which the Writer wants, and for an agent or publisher's guidelines if they\nhave them. Guidelines win over everything below.\n\n- **Synopsis.** One to two pages in present tense, third person, telling the\n  whole story including the ending. Name only the characters the plot needs —\n  usually three to five — and give each their name in capitals the first time.\n  It is a plot document: what happens and why, not themes.\n- **Query letter.** Under 400 words: a hook paragraph, two or three paragraphs\n  on the protagonist, what they want, what stops them and what they stand to\n  lose, then title, genre, word count and comparable titles, then a short bio.\n  It does not give away the ending.\n- **Logline.** One sentence: who, what they want, and what is in the way.\n- **Back-cover copy.** For readers, not agents: the setup and the question, no\n  ending, in the book's own voice.\n\nComparable titles and the bio are the Writer's to supply. Leave a marked gap\nfor each rather than inventing them; a wrong comparison or a made-up credit is\nthe one thing in a query that can do real harm.\n\n</what-each-one-is>\n\n<how-to-deliver>\n\nGive the text in the chat, ready to copy into an email or a submission form.\nIf the Writer wants to keep it in the Project, save it with\n`tabularia_write_sheet` as a `concept` Sheet named for the document — \"Synopsis\",\n\"Query letter\" — with the text in `notes`, and update that one next time rather\nthan making another.\n\nThen say what you left out and why, in a line or two, so the Writer can put\nback a subplot they care about.\n\n</how-to-deliver>\n\n<what-not-to-do>\n\n- Do not hide the ending in a synopsis. Agents ask for it.\n- Do not set the Book's description from your back-cover copy, or change its\n  title or subtitle, unless the Writer asks. When they do,\n  `tabularia_set_book_details` sets the description, subtitle and series name\n  the Book's published files carry; give it only the fields they approved.\n- Do not describe the book with praise — \"gripping\", \"unforgettable\". The\n  events have to do that.\n- Do not change the Manuscript's wording, or suggest changes to it, as part of\n  this job.\n\n</what-not-to-do>\n"
}

SHA-256 of public snapshot: b4d7a3ca46ad696b6390223b27bf22e6cc36c0619311b7af807fb9f54a6b6853