DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to break a multi-episode series into acts and act outs with Screenwriting Skills

Get an act-by-act breakdown with act outs for each episode of your series, using the series structure skill.

  • Top pick
  • Content
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA TV writer or showrunner who has a series outline with 12 or more episodes and needs each episode split into acts before drafting.

The problemSeries scripts use medium-specific units such as teasers, act outs and cliffhangers that general feature structure guides do not cover.

The outcomeA per-episode act map with act-out placements and cliffhanger notes, drawn from the series structure skill.

What you need first

  • Claude Code or OpenAI Codex installed
  • Git available if you use the clone-and-copy install route
  • Your series outline, script pages or story notes as text

Steps

  1. Run /plugin marketplace add jtydhr88/screenwriting-skills in Claude Code.
  2. Run /plugin install screenwriting@screenwriting-skills in Claude Code.
  3. Paste your series outline into the chat and ask for an act breakdown per episode, naming the act-out for each.
  4. Check that every episode has a teaser or cold open placement and a stated act-out before you use the map.

Prompt for your agent

Using the screenwriting-skills repo (sw-series-structure), read the series outline in <path or pasted text> and produce an act breakdown for each episode with act-out and cliffhanger placements. Verify that every episode lists a teaser or cold open and at least one act-out before returning the result.

Caveat. The skill bodies are written in Chinese, so you get answers in your question's language but must rely on the agent's account if you want to audit the instructions.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page