SkillAgentSearch skills...

story-systems-template

Creative project template for screenplays, novels, and film production. Multi-AI harness with upstream sync.

Install / Use

npx skills add bybren-llc/story-systems-template --skill logline

Installs into whichever agent you are using.

About this skill
♊

Gemini Rules

Gemini CLI config

Quality Score

73/100

Supported Platforms

Gemini CLI

Tags

Our assessment of story-systems-template

story-systems-template scores 73/100 on our quality scale, 1070th of 1,183 Content & Media skills we index.

Its Gemini Rules is 5.4 KB long, well organised into 30 sections with 8 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so story-systems-template is actively maintained.
  • Our last check on 2026-09-07 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

story-systems-template compared with similar skills

All 4 of these similar skills score higher than story-systems-template; compare them before choosing.

SkillScoreStarsUpdatedFormat
story-systems-template (this skill)by bybren-llc7303mo agoGemini Rules
siyuanby siyuan-note10046.9ktodayMCP Server
content-research-writerby ComposioHQ10077.4k38d agoSKILL.md
changelog-videoby heygen-com10067.0k7d agoSKILL.md
competitor-profilingby coreyhaines3110055.4k10d agoSKILL.md

Frequently asked questions

How do I install story-systems-template?
Run npx skills add bybren-llc/story-systems-template. The install tabs above show the steps for each supported agent.
Which AI agents does story-systems-template work with?
It is written for Gemini CLI, as a Gemini Rules file. Other agents that read the same format can often use it too.
Is story-systems-template safe to use?
It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is story-systems-template still maintained?
The repository was last updated about 3 months ago, so story-systems-template is actively maintained.

name: logline description: | 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.

Use when: distilling a story to its essential hook, preparing pitch materials, testing if a concept is compelling, or marketing a screenplay.

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

| Mistake | Example | Fix | |---------|---------|-----| | Too vague | "A man faces challenges" | "A retired hitman hunts the men who killed his dog" | | Too long | Multiple sentences | Cut 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

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
Updated2mo ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low