← 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": "Build a Timeline or select filtered Outline rows, then revise the passages they cover in an inactive Draft the Writer can review and merge. Use when the Writer asks to revise a character arc, plot thread, chronology, or scattered scenes without changing the Base Manuscript, or asks for a Draft from a Timeline or filtered Outline.",
"included_files": [],
"name": "story-thread-draft",
"skill_md_contents": "---\nname: story-thread-draft\ndescription: Build a Timeline or select filtered Outline rows, then revise the passages they cover in an inactive Draft the Writer can review and merge. Use when the Writer asks to revise a character arc, plot thread, chronology, or scattered scenes without changing the Base Manuscript, or asks for a Draft from a Timeline or filtered Outline.\n---\n\n<the-job>\n\nCollect the passages that belong to one story thread, capture them in a Draft,\nand write alternatives there. The Timeline or Outline selection says _where_;\nthe Writer decides which revisions, if any, to merge. Never write the Base\nDraft for this job, even though the connector would let you: the point is\nalternatives the Writer compares.\n\n</the-job>\n\n<find-the-passages>\n\n1. Read `tabularia_list_drafts`, `tabularia_list_timelines`, and the relevant\n Sheets. Check which Scoped Drafts are showing. The remote connector captures\n the last synced Base Manuscript, so say that plainly if the Writer is looking\n at different wording in a showing Draft.\n2. For a new Timeline, search the Manuscript for the people, places, objects,\n and events the Writer named. Read each search page until `truncated` is\n false, then read the candidate passages. A mention is not automatically a\n scene in the thread. Include a passage because it changes the thread, not\n merely because a name occurs in it.\n3. Reuse the existing Timeline when it already tracks that thread. Otherwise\n call `tabularia_create_timeline`, then `tabularia_add_timeline_marker` for\n the selected passages. Read `tabularia_list_timelines` again and check that\n every intended marker arrived. Creating markers changes the Timeline, so\n tell the Writer what was marked.\n4. For a filtered Outline, read the Outline markers from\n `tabularia_list_timelines`. Choose the exact marker ids of the visible rows\n the Writer described. Check each row's role and passage; a Chapter row\n captures its whole Chapter, while a Scene row captures that Scene. An\n Outline search or label filter in the Writer's browser is not available to\n the cloud connector, so never claim to have read that live filter. Ask for\n its criteria when the chosen rows cannot be determined from the Manuscript.\n\n</find-the-passages>\n\n<capture-and-revise>\n\n1. Call `tabularia_create_draft_from_source` with the Timeline id, or with\n `sourceKind: outline-filter` and exactly the selected Outline marker ids.\n Name the Draft for the thread and the revision idea. It starts inactive and\n records a fixed capture of the source's current Blocks; later marker or\n filter changes do not silently widen it. If this tool is unavailable, say\n that the current connector cannot retain the named source rather than\n passing guessed Block ids to `tabularia_create_draft`.\n2. Read the captured passages immediately before rewriting. Plan changes by\n cause and effect across the thread: what the character knows, what happens,\n what each scene now needs to set up or pay off. Keep the Writer's voice and\n preserve formatting in Markdown.\n3. Call `tabularia_write_draft` only for Blocks the new Draft covers. Use the\n returned Draft id, and supply the exact `readText` from the fresh read so a\n moved paragraph is refused. Read again after a conflict; never guess a new\n offset or overwrite a changed Block.\n4. Read the Draft back and verify that the intended passages changed and the\n rest did not. A missing or truncated read is unfinished verification, not\n evidence the whole thread was covered.\n\n</capture-and-revise>\n\n<deliver>\n\nName the Timeline or selected Outline rows, the Draft, and the passages you\nchanged. Explain any excluded search hits or unavailable passages. Tell the\nWriter the Draft is inactive and ready to inspect in Studio. Do not accept,\nreject, merge, publish, or delete anything on the Writer's behalf.\n\n</deliver>\n"
}SHA-256 of public snapshot: 8216bcad43b295690ad1619bf1858480d92e96ee2b97a593cd74531390c73b91