Update to Prepublish

{
  "description": "Help a freelance YouTube scriptwriter, ghostwriter, editor or small scriptwriting agency quality-check a script before delivering it to a client channel, using Prepublish's audit, hook and pre-flight tools, then produce a client-ready review note that explains what was checked, what was changed and what remains. Use when the user says they write scripts for a client or channel owner, asks \"check this script before I send it to my client\", \"give me feedback my client will understand\", \"prepare a script review for a YouTube channel\", \"QA a ghostwritten script\", or needs a second reader for a deliverable. Also use for channel owners reviewing a script a writer delivered to them.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 491
    },
    {
      "relative_path": "assets/client-review-note.md",
      "size_in_bytes": 1008
    },
    {
      "relative_path": "assets/icon-small.png",
      "size_in_bytes": 15255
    },
    {
      "relative_path": "references/claims-and-limits.md",
      "size_in_bytes": 2620
    },
    {
      "relative_path": "references/report-fields.md",
      "size_in_bytes": 3680
    },
    {
      "relative_path": "references/tools.md",
      "size_in_bytes": 5791
    }
  ],
  "name": "scriptwriter-client-review",
  "skill_md_contents": "---\nname: scriptwriter-client-review\ndescription: 'Help a freelance YouTube scriptwriter, ghostwriter, editor or small scriptwriting agency quality-check a script before delivering it to a client channel, using Prepublish''s audit, hook and pre-flight tools, then produce a client-ready review note that explains what was checked, what was changed and what remains. Use when the user says they write scripts for a client or channel owner, asks \"check this script before I send it to my client\", \"give me feedback my client will understand\", \"prepare a script review for a YouTube channel\", \"QA a ghostwritten script\", or needs a second reader for a deliverable. Also use for channel owners reviewing a script a writer delivered to them.'\n---\n\n# Client-ready script review\n\nFor writers who deliver scripts to someone else's channel, and for channel owners reviewing a writer's draft. The goal is a defensible, neutral second read: specific passages, specific fixes, and an honest statement of what the check covers.\n\nRead `references/tools.md`, `references/report-fields.md` and `references/claims-and-limits.md`. Use `assets/client-review-note.md` for the deliverable.\n\n## Inputs\n\n- The script, verbatim, and the working title the client approved.\n- The client's brief if the user has it: target runtime, audience, tone, must-include points. Use only what the user shares.\n- Who reads the note: the writer only (internal QA), or the client (external note). Default to internal until the user says otherwise.\n- Email for the free audit if the user has no Prepublish account (explain first, never invent).\n\n## Workflow\n\n1. Run `audit_script` with title, script and, when known, `video_duration_seconds`, `category` and `audience` from the brief.\n2. If the brief has a target runtime, run `script_runtime` on the script and compare.\n3. If the topic is sensitive, run `policy_preflight`. If the channel is faceless or formula-driven, run `check_authenticity`.\n4. For internal QA: present the flagged passages with rewrites, prioritised, and offer the `youtube-script-revision-loop` so the writer fixes the draft before delivery.\n5. For a client note: fill `assets/client-review-note.md`. Keep it factual, short and neutral. It should help the client trust the draft, not sell a tool.\n\n## Rules for client-facing text\n\n- Describe the check accurately: \"a text-level review of the script's hook, structure and pacing, plus a check against YouTube's published policy categories\". Never claim it predicts retention or views, and never promise results.\n- Do not include internal notes, the writer's private comments, or scores the user asked to leave out.\n- Credit rewrites honestly: rewrites from the writer, from Prepublish, or suggested by you are all fine to use, but do not misattribute them.\n- If the client's brief conflicts with a flagged issue (for example a required long sponsor read at the start), note the trade-off neutrally and let the client decide.\n- Never share the client's script with anyone or anything beyond the checks the user asked for.\n\n## Batch reviews\n\nWhen a writer has several scripts for the same client, review them one at a time in the order the user gives, and keep a one-line summary per script. Mention the daily free audit limit (3 for users without an account) before starting a batch larger than that.\n"
}