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

character-dialogue

Skill66 starsChanged 4 months agoMITView on GitHub

This skill provides Fountain format character and dialogue formatting rules. Covers character name formatting, extensions (V.O., O.S., CONT'D), dual dialogue, parentheticals, and proper dialogue block structure.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use @ prefix for names that aren't all caps:

    line 69
  2. Distinctive:

    Don't overuse - trust actors

    line 105
  3. Distinctive:

    Use for overlapping speech

    line 136
  4. Distinctive:

    Don't overuse - can be hard to follow

    line 139
  5. Distinctive:

    When a character first appears, their name is typically CAPITALIZED in action:

    line 144
  6. Distinctive:

    Avoid switching between SARAH/MS.

    line 178
  7. Distinctive:

    If character is known differently by different people, pick one for script

    line 179
  8. Distinctive:

    Keep lines speakable (read aloud)

    line 195
  9. Distinctive:

    Use pauses and silence

    line 202

≈ “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

Character & Dialogue Skill

Invocation Triggers

Apply this skill when:

  • Introducing characters
  • Writing dialogue blocks
  • Formatting character names
  • Handling dual dialogue
  • Using character extensions

Character Name Format

Basic Format

Character names must be:

  • ALL UPPERCASE
  • On their own line
  • Preceded by a blank line
  • Followed immediately by dialogue (no blank line)

SARAH
Hello, John.

Character Extensions

Extensions appear in parentheses after the name:

ExtensionMeaningWhen to Use
(V.O.)Voice OverCharacter narrating or not in scene
(O.S.)Off ScreenCharacter in scene but not visible
(O.C.)Off CameraSame as O.S. (alternate)
(CONT'D)ContinuedSame speaker after action interruption
(PRE-LAP)Pre-lapAudio starts before scene
(INTO PHONE)DeliverySpeaking into phone
(INTO RADIO)DeliverySpeaking into radio
(SUBTITLE)TranslationForeign dialogue translated
SARAH (V.O.)
I never should have trusted him.

JOHN (O.S.)
Sarah? Are you home?

SARAH
In here!

She turns toward the door.

SARAH (CONT'D)
I wasn't expecting you.

Forcing Mixed-Case Names

Use @ prefix for names that aren't all caps:

@McCLANE
Yippee ki-yay.

@DeVITO
Don't start with me.

Dialogue Format

Basic Dialogue

SARAH
This is a line of dialogue. It can
span multiple lines naturally.

Dialogue with Parenthetical

SARAH
(hesitant)
I don't think that's a good idea.

JOHN
(laughing)
You always say that.
(serious now)
But this time I agree.

Parenthetical Guidelines

  • Use sparingly
  • Brief direction only
  • Lower case
  • On own line within dialogue block
  • Don't overuse - trust actors

Good parentheticals:

(whispering)
(to John)
(beat)
(re: the gun)
(into phone)

Bad parentheticals (avoid):

(angrily, as if she can't believe what she's hearing)
(walking across the room and picking up the vase)

Dual Dialogue (Simultaneous Speech)

Characters speaking at the same time:

JACK
I love you!

JILL ^
I hate you!

The ^ after the second character name triggers side-by-side formatting.

Dual Dialogue Guidelines

  • Use for overlapping speech
  • Second character gets the ^
  • Both should be roughly equal length
  • Don't overuse - can be hard to follow

Character Introduction

First Appearance Format

When a character first appears, their name is typically CAPITALIZED in action:

INT. COFFEE SHOP - DAY

SARAH CHEN (30s, sharp eyes, perpetually exhausted)
sits alone at a corner table.

Introduction Best Practices

  • Age range, not exact age
  • Brief physical impression
  • One character-defining detail
  • Active description when possible

Good introductions:

JOHN MARCUS (40s, ex-military bearing, softened by life)

DETECTIVE PARK (50s, seen too much, says too little)

YOUNG SARAH (8, all skinned knees and fierce determination)

Avoid:

SARAH, a beautiful woman in her 30s, enters.  // "beautiful" is vague

JOHN is tall with brown hair and blue eyes.  // casting details

Character Consistency

Naming Rules

  • Pick one name, use it consistently
  • Avoid switching between SARAH/MS. CHEN/SHE
  • If character is known differently by different people, pick one for script

Exception Patterns

// Character is introduced under false identity
STRANGER (later revealed as JOHN)
Nice to meet you.

// Later, after reveal
JOHN
Sorry about the deception.

Dialogue Best Practices

Line Length

  • Keep lines speakable (read aloud)
  • Break at natural breath points
  • One thought per line when possible

Subtext

  • Characters rarely say exactly what they mean
  • Let action contradict words
  • Use pauses and silence
SARAH
I'm fine.

She stares out the window, knuckles white on her coffee cup.

Avoiding "On the Nose"

Instead of:

JOHN
I'm angry because you betrayed me and now I can't trust you.

Try:

JOHN
(quiet)
I think you should leave.

Validation Checklist

  • Character names in UPPERCASE
  • Blank line before character names
  • No blank line between name and dialogue
  • Extensions in (PARENTHESES)
  • Parentheticals are brief and necessary
  • Mixed-case names use @ prefix
  • Dual dialogue uses ^ on second character
  • Character names are consistent 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.