Token导航 LogoToken导航

Agent Skill · 研究检索

storyboard-manager(故事板经理)

storyboard-manager 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

storyboard-manager 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 8,286。

总安装 16,735周安装 677GitHub Stars 356下载 5,254核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:storyboard-manager(故事板经理)
来源仓库:https://github.com/ailabs-393/ai-labs-claude-skills
仓库路径:skills/storyboard-manager
安装命令:
npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill storyboard-manager
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill storyboard-manager

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

storyboard-manager 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于快速信息收集和筛选的场景,如研究、调研或内容创作。通过关键词匹配和来源分析,帮助 Agent 高效定位相关内容。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。可结合来源仓库和原始 README 继续核验具体用法和实现细节。

来源仓库内路径:skills/storyboard-manager

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill story…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

storyboard-manager 怎么安装?

在终端执行 npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill storyboard-mana…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

storyboard-manager 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

storyboard-manager 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

storyboard-manager 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

storyboard-manager 用的人多吗?

公开数据是累计安装 16,735 次,近一周安装 677 次,下载 5,254 次,GitHub 356 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

storyboard-manager 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
storyboard-manager

故事板经理 · 本页

16,735356只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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:

  • markdown - Human-readable report (default)
  • json - Structured data for further processing

Understanding Timeline Output

The script provides:

Statistics

  • Total events tracked
  • Total characters appearing
  • Events per character

Timeline View

  • Chronological sequence of events
  • Chapter/scene locations
  • Characters present in each event
  • Preview of event content

Warnings

  • Events without timeline markers
  • Characters mentioned but not defined in character files

Acting on Timeline Results

After running the tracker:

  1. Review warnings - Address missing timeline markers by adding them to chapters
  2. Check sequence - Verify events occur in logical order
  3. Identify gaps - Look for time periods without events
  4. Character tracking - Ensure characters appear consistently with their arc

Add timeline markers to chapters where missing:

**Timeline:** Day 7, Morning

Or use inline markers:

Three days had passed since the incident...

Consistency Checking

When to Use Consistency Checking

Invoke the consistency checker when:

  • User requests consistency analysis
  • Before finalizing chapters or acts
  • After making significant character or plot changes
  • When tracking contradictions or errors

Running the Consistency Checker

Execute the script from the project root:

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

Output format options:

  • markdown - Human-readable report with issue details (default)
  • json - Structured data for programmatic analysis

Understanding Consistency Output

The script identifies issues in three severity levels:

Critical (🔴)

  • Major contradictions requiring immediate attention
  • Character appearing after death
  • Fundamental plot contradictions

Warning (⚠️)

  • Potential inconsistencies to review
  • Age discrepancies
  • Physical description contradictions
  • Relationship conflicts

Info (ℹ️)

  • Minor issues or variations
  • Name capitalization inconsistencies
  • Stylistic variations

Acting on Consistency Results

For each issue reported:

  1. Read flagged locations - Review the specific files mentioned
  2. Determine truth - Decide which version is correct (usually character profile is authoritative)
  3. Update files - Fix contradictions using the Edit tool
  4. Re-run checker - Verify fixes resolved the issues

Example workflow for character age inconsistency:

Issue: Age inconsistency for Maya
- Profile: 18 years old
- Chapter 3: mentions "21-year-old Maya"

Fix: Edit chapter-3.md to change "21-year-old" to "18-year-old"

Consistency Checking Limitations

The automated checker catches:

  • Physical attribute contradictions
  • Age discrepancies
  • Name variations
  • Basic world-building facts

The checker cannot catch:

  • Subtle personality inconsistencies
  • Complex plot logic errors
  • Thematic contradictions
  • Nuanced relationship changes

Manual review is still essential for deep consistency.

Best Practices

Progressive Context Loading

Don't load all reference files at once. Instead:

  1. Scan project structure first
  2. Read only relevant character files for the current task
  3. Access reference documentation only when specific guidance is needed
  4. Use Grep to find specific sections in large reference files

Maintaining Genre Voice

Match the story's established tone:

  • YA: Present tense, immediate emotional connection, contemporary language
  • Fantasy: Rich descriptive language, world-building integration
  • Thriller: Short sentences, high tension, sensory details
  • Literary: Complex prose, internal reflection, symbolic elements

Reference the summary.md to identify target audience and adjust accordingly.

Character Arc Integration

Every chapter should serve character arcs:

  • Track where each character is in their arc
  • Show incremental change, not sudden transformation
  • Use plot events to test character beliefs
  • Demonstrate growth through choices and behavior

Balancing Show vs. Tell

For narrative writing:

  • Show emotions through actions, dialogue, physical reactions
  • Tell to compress time, provide necessary information efficiently
  • Use character-filtered description (what would this POV character notice?)

Handling Multiple POV

When stories have multiple perspectives:

  • Create distinct voices for each POV character
  • Ensure each POV section advances both that character's arc and the plot
  • Vary sentence structure and vocabulary by character
  • Track what each character knows vs. doesn't know

Common User Requests & Responses

"Help me develop a character backstory"

  1. Read existing character files for context
  2. Read the character profile (if exists) to enhance
  3. Access character_development.md reference for backstory framework
  4. Create detailed backstory covering: ghost/wound, formative relationships, key history
  5. Integrate with their character arc and story role

"Write the next chapter"

  1. Read summary.md and story planning documents
  2. Read all character profiles for characters appearing in chapter
  3. Read previous 2 chapters for continuity
  4. Identify chapter position in story structure
  5. Write chapter with scene/sequel structure
  6. Include timeline markers and POV/location headers

"Outline Act 2"

  1. Read summary and any existing planning documents
  2. Access story_structures.md for structural guidance
  3. Identify act 2 requirements (complications, midpoint, rising tension)
  4. Create beat-by-beat outline aligned with character arcs
  5. Note how plot and character arcs intersect

"Check my story for consistency"

  1. Run consistency_checker.py script
  2. Review output identifying issues
  3. Read flagged files to understand contradictions
  4. Recommend specific fixes for each issue
  5. Offer to make edits if user confirms

"Track the timeline of my story"

  1. Run timeline_tracker.py script
  2. Review output showing event sequence
  3. Identify gaps or inconsistencies in chronology
  4. Recommend adding timeline markers where missing
  5. Provide timeline summary organized by character or chapter

"What structure should I use for my thriller?"

  1. Access story_structures.md reference
  2. Recommend Three-Act Structure or Save the Cat
  3. Explain thriller-specific requirements (escalating tension, ticking clock)
  4. Provide beat sheet adapted to their story concept
  5. Offer to create detailed planning document

Resources

scripts/timeline_tracker.py

Python script that analyzes markdown files to extract and organize timeline events. Tracks character appearances, identifies time markers, groups events chronologically, and flags consistency issues.

Usage: Run from project root with python3.claude/skills/storyboard-manager/scripts/timeline_tracker.py.

scripts/consistency_checker.py

Python script that detects inconsistencies in character details, physical descriptions, ages, names, and world-building facts across all story files. Outputs severity-ranked issues with file locations.

Usage: Run from project root with python3.claude/skills/storyboard-manager/scripts/consistency_checker.py.

references/character_development.md

Comprehensive framework for creating multi-dimensional characters including core elements, backstory structure, arc types, relationship dynamics, voice development, and consistency guidelines.

Load when: Developing new characters, enhancing existing profiles, resolving character consistency issues, or planning character arcs.

references/story_structures.md

Detailed reference covering major story structures (Three-Act, Hero's Journey, Save the Cat), character arc templates, scene structure, pacing guidelines, plot development techniques, and genre-specific structures.

Load when: Planning story outline, structuring acts, organizing plot beats, determining pacing, or applying specific narrative frameworks.

平台分布

Claude Code

28.57%
按下载量换算1,501

OpenCode

23.31%
按下载量换算1,225

Cursor

15.05%
按下载量换算791

Antigravity

12.59%
按下载量换算661

Codex

6.65%
按下载量换算349

Gemini CLI

3.64%
按下载量换算191

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills