agentleFS
clairelily2020clairelily2020/creator-workflows/skills/comic-story-pipeline/SKILL.md

comic-story-pipeline

Skill0 starsChanged 21 days agoMITView on GitHub

Turn a rough comic or short-video idea into a production-ready story package. Use when the user wants a comic, storyboard, short visual story, character brief, scene plan, image prompt set, or story-to-video workflow.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn a rough idea into a production brief that another tool, artist, or editor can execute.

    line 8
  2. Distinctive:

    Ask only for missing details that change the output:

    line 14
  3. Distinctive:

    If the user only gives one sentence, proceed with reasonable assumptions and state them briefly.

    line 25
  4. Distinctive:

    Create 5 to 9 beats, depending on length.

    line 41
  5. Distinctive:

    Write concise scene text:

    line 51
  6. Distinctive:

    Avoid over-explaining. Visual stories need playable moments.

    line 58
  7. Distinctive:

    Create a panel or shot list.

    line 62
  8. Distinctive:

    Keep the story visually playable.

    line 138
  9. Distinctive:

    Do not create more characters than the format can support.

    line 139
  10. Distinctive:

    If the concept is too broad, shrink it to one scene or one emotional turn.

    line 141
  11. Very specific:

    If the user wants review rather than creation, route to comic-review.

    line 142
  12. Very specific:

    If the user is ready to publish, route to comic-preflight.

    line 143

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Comic Story Pipeline

Use this skill to turn a rough idea into a production brief that another tool, artist, or editor can execute.

The goal is not to write a long generic story. The goal is to create enough structure for consistent characters, clear scenes, useful panels, and publishable pacing.

Inputs To Ask For

Ask only for missing details that change the output:

  • story idea or logline
  • target format: comic panels, carousel, vertical short, horizontal video, storyboard doc
  • duration or panel count
  • audience and tone
  • visual style
  • language
  • platform if known
  • any fixed character, setting, or brand constraints

If the user only gives one sentence, proceed with reasonable assumptions and state them briefly.

Production Stages

1. Logline And Story Shape

Clarify:

  • protagonist
  • desire
  • obstacle
  • escalation
  • ending beat

2. Beat Sheet

Create 5 to 9 beats, depending on length.

Each beat should contain:

  • what changes
  • emotional turn
  • visual anchor

3. Script

Write concise scene text:

  • action
  • dialogue or narration
  • sound cues if needed
  • duration or panel estimate

Avoid over-explaining. Visual stories need playable moments.

4. Storyboard

Create a panel or shot list.

Each row should include:

  • panel or shot number
  • framing
  • camera angle or movement
  • character action
  • background
  • text or subtitle
  • image prompt notes

5. Character Consistency

For each recurring character, define:

  • age range
  • body type
  • face and hair cues
  • clothing
  • color cues
  • expression range
  • no-change details

6. Scene And Asset Plan

List:

  • locations
  • key props
  • required generated images
  • required video clips
  • required audio or captions
  • publishing format

Output Format

## Production Brief: {title}

Assumptions:
- {assumption}

Logline:
{one sentence}

Format:
{comic / carousel / vertical short / horizontal video}

Beat sheet:
1. {beat}
2. {beat}

Script:
| Scene | Action | Dialogue/Narration | Notes |
| --- | --- | --- | --- |

Storyboard:
| # | Framing | Action | Background | Text | Prompt notes |
| --- | --- | --- | --- | --- | --- |

Character consistency:
{character notes}

Asset plan:
- {asset}

Production risks:
- {risk}

Next step:
{generate panels / review storyboard / run preflight}

Rules

  • Keep the story visually playable.
  • Do not create more characters than the format can support.
  • Lock recurring character details before scene prompts.
  • If the concept is too broad, shrink it to one scene or one emotional turn.
  • If the user wants review rather than creation, route to comic-review.
  • If the user is ready to publish, route to comic-preflight.

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.