{"id":67783,"plugin_id":"plugin_asdk_app_6aca99f4ddf481919cb0214e89117cb7","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T13:11:02.262Z","digest":"59701e592ecc558ed6b9ac351c62df656a1f8703f417d5ca4a69b1ca8f705262","against":null,"payload":{"description":"Read a screenplay or teleplay in Tabularia the way a studio reader writes coverage — premise, structure, character, dialogue and format — and check its format against industry convention. Use when the Writer of a script asks for coverage, notes, a read of their screenplay, pilot or episode, whether the format is right, or whether it is ready to send out.","included_files":[],"name":"screenplay-read","skill_md_contents":"---\nname: screenplay-read\ndescription: Read a screenplay or teleplay in Tabularia the way a studio reader writes coverage — premise, structure, character, dialogue and format — and check its format against industry convention. Use when the Writer of a script asks for coverage, notes, a read of their screenplay, pilot or episode, whether the format is right, or whether it is ready to send out.\n---\n\n<what-this-is>\n\nTwo jobs, and the Writer usually wants one of them:\n\n- **Coverage** — the read a producer's reader writes: a logline, a short\n  synopsis, notes on premise, structure, character and dialogue, and a verdict.\n- **A format check** — whether the pages look like a professional script,\n  because a reader who sees the wrong format often stops before the story.\n\nNeither changes the script. Findings are comments.\n\n</what-this-is>\n\n<read-the-script>\n\n1. `tabularia_list_drafts`, then `tabularia_project_metadata`.\n2. `tabularia_list_anchors` and `tabularia_list_comments` — a Project started\n   from a screenplay shape (Three-Act, Fifteen-Beat, Hero's Journey, or\n   Television Act-Outs) carries what each act or beat is for.\n3. Read the whole script with `tabularia_read_window`, 120 Blocks at a time.\n   A script is read in one sitting; coverage of half of one is not coverage.\n\nScene headings — `INT.` or `EXT.`, a place, and a time of day — mark each\nscene. Use them to keep your place and to cite where each finding sits, along\nwith the Block index.\n\n</read-the-script>\n\n<coverage>\n\n- **Logline.** One sentence: the protagonist, what they want, what stands in\n  the way.\n- **Synopsis.** Half a page, present tense, the whole story.\n- **Premise.** Is the idea clear and does it promise something only this\n  script delivers?\n- **Structure.** Against the shape in the Project, or the conventional one for\n  the form: the inciting incident early, a turn into the second act, a\n  midpoint, a low point, a climax. For television, does each act end on a turn\n  that would hold an audience through a break?\n- **Character.** Does the protagonist want something, change, and drive the\n  action rather than watch it?\n- **Dialogue.** Do the characters sound different from each other? Is\n  information delivered in speeches nobody would say?\n- **Verdict.** Pass, consider or recommend, with one line of why. Say plainly\n  that it is your read, not a prediction of any buyer's.\n\nPut each note as a comment with `tabularia_add_comment` on the scene it is\nabout, and give the logline, synopsis and verdict in the chat.\n\n</coverage>\n\n<format>\n\nWhat readers expect, and what to flag when it is missing:\n\n- Scene headings in capitals: `INT.` or `EXT.`, a location, a time of day.\n- Action in present tense, in short paragraphs — four lines at most — saying\n  only what can be seen or heard.\n- A character's name in capitals the first time they appear in action.\n- Character cues in capitals above their dialogue; parentheticals short and\n  rare, never stage directions in disguise.\n- Transitions such as `CUT TO:` used sparingly; most scripts need almost none.\n- No camera directions unless the shot is the point.\n\nList format slips with their Blocks rather than commenting on each one: a\nscript with forty of the same slip needs one note saying so.\n\nPage count matters to readers — about a minute of screen time a page, and\nroughly 90 to 120 pages for a feature. Ask the Writer for the last page\nnumber Studio shows rather than estimating it from the word count.\n\n</format>\n\n<what-not-to-do>\n\n- Do not read a script as prose. Sparse action lines and fragments are the\n  form, not a fault; `prose-read` and its counts do not apply.\n- Do not rewrite scenes. If the Writer asks for a rewrite, it goes in a Draft.\n\n</what-not-to-do>\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}