storyboard-manager

6
1
Source

Assist writers with story planning, character development, plot structuring, chapter writing, timeline tracking, and consistency checking. Use this skill when working with creative writing projects organized in folders containing characters, chapters, story planning documents, and summaries. Trigger this skill for tasks like "Help me develop this character," "Write the next chapter," "Check consistency across my story," or "Track the timeline of events."

Install

mkdir -p .claude/skills/storyboard-manager && curl -L -o skill.zip "https://mcp.directory/api/skills/download/3683" && unzip -o skill.zip -d .claude/skills/storyboard-manager && rm skill.zip

Installs to .claude/skills/storyboard-manager

About this skill

Storyboard Manager

Overview

The Storyboard Manager skill equips Claude with specialized knowledge and tools for creative writing workflows. It provides frameworks for character development, story structure patterns, automated timeline tracking, and consistency checking across narrative projects. This skill automatically adapts to various storyboard folder structures while maintaining best practices for novel, screenplay, and serialized fiction writing.

Core Capabilities

The skill provides four main capabilities:

1. Character Development & Management

Support creating deep, consistent character profiles with backstories, arcs, and relationships.

2. Story Planning & Structure

Guide plot development using established frameworks (Three-Act, Hero's Journey, Save the Cat, etc.) and help organize narrative elements.

3. Chapter & Scene Writing

Generate chapter content, scene breakdowns, and dialogue that maintains consistency with established characters and plot.

4. Timeline Tracking & Consistency Checking

Use automated tools to verify chronological consistency, character continuity, and world-building coherence.

Detecting Project Structure

The Storyboard Manager automatically detects and adapts to various folder organizations. Look for these common directory patterns:

Character folders: characters/, Characters/, cast/, Cast/ Chapter folders: chapters/, Chapters/, scenes/, Scenes/, story/ Planning folders: story-planning/, planning/, outline/, notes/ Summary files: summary.md, README.md, overview.md

When triggered, scan the project root to identify the structure and adjust workflows accordingly. If no standard structure exists, recommend organizing files using the pattern: characters/, chapters/, story-planning/, and summary.md.

Workflow Decision Tree

Use this decision tree to determine the appropriate workflow:

User Request
├─ Character-related? ("develop character," "create backstory," "character arc")
│  └─ → Character Development Workflow
│
├─ Planning/Plot? ("outline story," "plan act 2," "plot structure")
│  └─ → Story Planning Workflow
│
├─ Writing content? ("write chapter," "generate scene," "continue story")
│  └─ → Chapter/Scene Writing Workflow
│
└─ Checking/Analysis? ("check consistency," "track timeline," "find contradictions")
   ├─ Timeline? → Use timeline_tracker.py script
   └─ Consistency? → Use consistency_checker.py script

Character Development Workflow

Step 1: Gather Context

Before developing a character, read existing character files to understand:

  • Established naming conventions and profile format
  • Existing characters and relationships
  • Story genre and tone
  • Character archetypes already in use

Use the Read tool to examine existing character files in the characters directory.

Step 2: Access Character Development Framework

When detailed character guidance is needed, read references/character_development.md which contains:

  • Core character elements (personality, motivation, goals)
  • Backstory framework (ghost/wound, formative relationships)
  • Character arc types (positive change, flat, negative)
  • Relationship dynamics
  • Voice development techniques
  • Consistency guidelines

To efficiently find specific guidance, use Grep to search for relevant sections:

# Example: Find guidance on character arcs
grep -i "character arc" references/character_development.md

Step 3: Develop Character Profile

Create or enhance character profiles with these essential elements:

Basic Information

  • Name, age, role, physical appearance
  • Key personality traits (both positive and negative)

Background

  • Origin and formative experiences
  • Ghost/wound that shapes their behavior
  • Key relationships and family dynamics

Character Arc

  • Starting belief or flaw
  • Want vs. Need (external goal vs. internal growth)
  • Transformation journey
  • End state

Relationships

  • Connections to other characters
  • Dynamic types (ally, rival, mentor, etc.)
  • How relationships evolve

Unique Elements

  • Abilities, skills, or special knowledge
  • Secrets or hidden aspects
  • Voice/speech patterns
  • Character-specific quirks

Step 4: Ensure Consistency

Cross-reference with:

  • Existing character profiles (avoid redundancy in roles/traits)
  • Story planning documents (ensure alignment with plot needs)
  • Summary/overview (match genre and tone)

Step 5: Create or Update File

Write the character profile to characters/[character-name].md using markdown format. Match the existing style and structure found in other character files.

Story Planning Workflow

Step 1: Assess Current Planning State

Read existing planning documents to understand:

  • Story concept and premise
  • Established plot points or outline
  • Target audience and genre
  • Themes and central questions
  • Planned structure (if any)

Look in folders like story-planning/, outline/, or files like summary.md.

Step 2: Access Story Structure Reference

For detailed structural guidance, read references/story_structures.md which includes:

  • Three-Act Structure
  • Hero's Journey (Campbell's Monomyth)
  • Save the Cat Beat Sheet
  • Character arc templates
  • Scene structure components
  • Pacing guidelines by genre
  • Subplot integration techniques
  • Genre-specific structures

Use Grep to find specific frameworks:

# Example: Find Three-Act Structure details
grep -A 20 "Three-Act Structure" references/story_structures.md

Step 3: Determine Structure Needs

Based on the user's request and story genre, recommend appropriate frameworks:

  • Thriller/Mystery: Three-Act with strong midpoint reversal
  • Fantasy/Adventure: Hero's Journey for quest narratives
  • YA/Contemporary: Save the Cat for tight emotional beats
  • Literary Fiction: Focus on character arc structure
  • Romance: Genre-specific structure with relationship beats

Step 4: Develop Planning Document

Create or enhance planning documents with:

Story Overview

  • Premise in 2-3 sentences
  • Genre, target audience, tone
  • Central themes and questions

Plot Structure

  • Act/chapter breakdown with key events
  • Inciting incident and plot points
  • Midpoint twist or revelation
  • Climax and resolution

Character Arcs

  • How each main character transforms
  • Arc integration with plot beats

World-Building Elements (if applicable)

  • Setting and locations
  • Magic systems or technology
  • Social structures or rules
  • Historical context

Timeline

  • Story duration
  • Key event sequence
  • Pacing considerations

Step 5: Create Planning File

Write planning documents to story-planning/[document-name].md. Use clear hierarchical structure with markdown headers for easy navigation.

Chapter & Scene Writing Workflow

Step 1: Gather Story Context

Before writing any content, comprehensively read:

Character Files: All relevant character profiles to understand voices, motivations, arcs Planning Documents: Story structure, plot points, current story position Previous Chapters: Recent chapters to maintain continuity (read at least 1-2 prior chapters) Summary: Overall story premise and themes

This ensures the new content aligns with established elements.

Step 2: Identify Chapter Requirements

Determine:

  • Story Position: Where does this fit in the overall structure?
  • POV Character: Whose perspective?
  • Scene Goal: What does the POV character want in this scene?
  • Conflict: What opposes their goal?
  • Outcome: How does the scene end? (typically with a complication)
  • Character Development: What arc beats occur here?
  • Plot Advancement: What story questions are raised or answered?

Step 3: Structure the Chapter

Apply scene structure components:

Scene (Action)

  1. Goal - What the POV character pursues
  2. Conflict - Opposition encountered
  3. Disaster - Negative outcome that propels forward

Sequel (Reaction)

  1. Reaction - Emotional response to disaster
  2. Dilemma - Processing options
  3. Decision - Choice leading to next goal

Alternate between high-tension (action, conflict) and low-tension (reflection, world-building) beats for pacing.

Step 4: Write with Character Consistency

Maintain character voice by referencing:

  • Established personality traits
  • Speech patterns and vocabulary
  • Behavioral patterns (under stress, when happy, decision-making style)
  • Current position in character arc
  • Relationships with other characters present

Step 5: Integrate Timeline Markers

Include timeline references to maintain chronological clarity:

  • Explicit markers: "Day 3," "Two weeks later"
  • Implicit markers: Time of day, seasonal cues, event references
  • Format: **Timeline:** Day 5, Evening in chapter header or as section break

Step 6: Create Chapter File

Write chapter content to chapters/chapter-[number].md or chapters/[chapter-name].md. Include:

Chapter Header

# Chapter [Number]: [Optional Title]

**Timeline:** [When this occurs]
**POV:** [Character name]
**Location:** [Where this takes place]

Chapter Content

  • Scene-by-scene breakdown
  • Dialogue and action
  • Character thoughts (for POV character)
  • Descriptive elements

Step 7: Note Continuity Elements

After writing, document any new information introduced:

  • Character revelations or development
  • Plot points or clues
  • World-building details
  • Timeline events

This helps maintain consistency in future chapters.

Timeline Tracking

When to Use Timeline Tracking

Invoke the timeline tracker when:

  • User requests timeline analysis or event sequencing
  • Checking chronological consistency
  • Planning event order across chapters
  • Identifying unmarked time periods

Running the Timeline Tracker

Execute the script from the project root:

python3 .claude/skills/storyboard-manager/scripts/timeline_tracker.py . --output markdown

Output format options:

  • `markdo

Content truncated.

travel-planner

ailabs-393

This skill should be used whenever users need help planning trips, creating travel itineraries, managing travel budgets, or seeking destination advice. On first use, collects comprehensive travel preferences including budget level, travel style, interests, and dietary restrictions. Generates detailed travel plans with day-by-day itineraries, budget breakdowns, packing checklists, cultural do's and don'ts, and region-specific schedules. Maintains database of preferences and past trips for personalized recommendations.

11666

finance-manager

ailabs-393

Comprehensive personal finance management system for analyzing transaction data, generating insights, creating visualizations, and providing actionable financial recommendations. Use when users need to analyze spending patterns, track budgets, visualize financial data, extract transactions from PDFs, calculate savings rates, identify spending trends, generate financial reports, or receive personalized budget recommendations. Triggers include requests like "analyze my finances", "track my spending", "create a financial report", "extract transactions from PDF", "visualize my budget", "where is my money going", "financial insights", "spending breakdown", or any finance-related analysis tasks.

1710

tech-debt-analyzer

ailabs-393

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

215

script-writer

ailabs-393

This skill should be used whenever users need YouTube video scripts written. On first use, collects comprehensive preferences including script type, tone, target audience, style, video length, hook style, use of humor, personality, and storytelling approach. Generates complete, production-ready YouTube scripts tailored to user's specifications for any topic. Maintains database of preferences and past scripts for consistent style.

144

social-media-generator

ailabs-393

This skill should be used when the user requests social media content creation for Twitter, Instagram, LinkedIn, or Facebook. It generates platform-optimized posts and saves them in an organized folder structure with meaningful filenames based on event details.

314

business-document-generator

ailabs-393

This skill should be used when the user requests to create professional business documents (proposals, business plans, or budgets) from templates. It provides PDF templates and a Python script for generating filled documents from user data.

133

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5731,370

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1161,191

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4181,109

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,194748

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,154684

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,315614

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.