agentleFS
bybren-llcbybren-llc/story-systems-template/.claude/skills/logline/SKILL.md

logline

Skill66 starsChanged 4 months agoMITView on GitHub

This skill provides logline (hook) writing techniques for screenplays. Covers the four components (characters, conflict, setting, action), formulas for effective loglines, and common mistakes to avoid.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do they understand the genre?

    line 194
  2. Distinctive:

    Do they know who the protagonist is?

    line 195
  3. Distinctive:

    Do they want to know what happens?

    line 197
  4. Distinctive:

    If "no" to any, revise.

    line 200

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Logline Skill

Invocation Triggers

Apply this skill when:

  • Distilling a story to its essential hook
  • Preparing pitch materials
  • Testing if a concept is clear and compelling
  • Marketing a screenplay

What is a Logline?

A logline (also called a "hook") is a one to two sentence description of your movie that captures the essence of the story in a way that makes people want to see it.

The Four Components of a Hook

Per WTFB methodology, every effective hook contains these four elements:

1. Characters

  • Who are they?
  • What do they want?
  • What are their goals?

2. Conflict

  • What is the main obstacle to achieving their goal?
  • Who or what opposes them?

3. Setting

  • Time period
  • Genre
  • Style/tone

4. Action

  • What exciting things happen?
  • Never be boring!

Logline Formula

[ADJECTIVE] [PROTAGONIST TYPE] must [GOAL/ACTION]
when [INCITING INCIDENT/CONFLICT],
or else [STAKES].

Alternative Formula

When [SETUP], a [PROTAGONIST] must [OBJECTIVE]
before [ANTAGONIST] [THREAT].

Genre-Specific Formula

A [GENRE] about [PROTAGONIST] who [SITUATION]
until [CATALYST] forces them to [ACTION]
against [ANTAGONIST/OBSTACLE].

Classic Logline Examples

Raiders of the Lost Ark

"An archeologist is hired by the U.S. government to find the Ark of the Covenant before the Nazis."

Breakdown:

  • Character: Archeologist (implies adventure, intelligence)
  • Conflict: Race against Nazis
  • Setting: Implied WWII era, adventure genre
  • Action: "Find" + competing with Nazis = excitement

Gladiator

"A Roman general is betrayed and his family killed by an insane emperor. Now a gladiator, he comes to Rome for revenge."

Breakdown:

  • Character: Roman general (status, skill)
  • Conflict: Betrayal, loss, revenge against emperor
  • Setting: Roman era, epic drama
  • Action: Gladiator combat, revenge journey

Logline Development Worksheet

Step 1: Core Elements

PROTAGONIST: ___________________________________
(Be specific: not "a man" but "a disgraced surgeon")

GOAL: ___________________________________
(What do they actively pursue?)

ANTAGONIST/OBSTACLE: ___________________________________
(Person, force, or circumstance opposing them)

STAKES: ___________________________________
(What happens if they fail?)

UNIQUE ELEMENT: ___________________________________
(What makes THIS story different?)

Step 2: Draft Loglines

Draft 1 (Basic):

___________________________________________________
___________________________________________________

Draft 2 (Add specificity):

___________________________________________________
___________________________________________________

Draft 3 (Add stakes):

___________________________________________________
___________________________________________________

Final Logline:

___________________________________________________
___________________________________________________

Logline Quality Checklist

Must Have

  • Protagonist clearly identified
  • Goal/objective stated
  • Conflict/obstacle present
  • Implies genre
  • One to two sentences maximum
  • Creates desire to know more

Should Have

  • Unique hook or twist
  • Stakes implied or stated
  • Active voice (character DOES something)
  • Specific rather than vague

Must Avoid

  • No questions ("What if...?")
  • No character names (unless famous)
  • No theme statements
  • No backstory
  • No "and then" chains

Common Logline Mistakes

MistakeExampleFix
Too vague"A man faces challenges""A retired hitman hunts the men who killed his dog"
Too longMultiple sentencesCut to one powerful sentence
No conflict"A woman discovers her past""A woman must confront the cult that raised her"
Passive"A story about love""A dying man races to reconnect with his estranged daughter"
Lists events"First X, then Y, then Z"Focus on central conflict
Theme not story"An exploration of grief""A widow must solve her husband's murder"

Genre-Specific Tips

Action/Thriller

  • Emphasize physical stakes and ticking clock
  • "Must stop X before Y happens"

Comedy

  • Hint at the comedic situation or irony
  • Include the fish-out-of-water element

Drama

  • Focus on internal conflict made external
  • Emphasize emotional stakes

Horror

  • Establish the threat
  • Imply isolation or helplessness

Romance

  • Show the obstacle to love
  • Include what makes this couple unique

Logline Testing

Share your logline and ask:

  1. Do they understand the genre?
  2. Do they know who the protagonist is?
  3. Can they identify the conflict?
  4. Do they want to know what happens?
  5. Can they picture the movie?

If "no" to any, revise.

Validation Checklist

  • Logline is 25 words or fewer
  • Protagonist is specific and interesting
  • Goal is clear and active
  • Conflict/obstacle is compelling
  • Stakes are implied or stated
  • Genre is clear
  • Creates curiosity to see the film
  • No character names used
  • Active voice throughout

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.