🎯 Skills

Skills System Guide

Reusable Claude prompts that automate complex workflows

🧩 What are Skills?

Skills are reusable Claude prompts that automate complex, multi-step workflows. Each skill is a structured SKILL.md file stored in ~/.claude/skills/ and invoked directly from Claude Code.

πŸ“‹

Structured Workflows

Multi-step processes with gates and checkpoints

πŸ”„

Reusable

Install once, use across projects with variable substitution

πŸ€–

AI-Powered

Claude follows the skill instructions automatically via MCP

πŸ“¦ Available Skills

Featured

πŸ“– Story Engine v0.9

YouTube story channel script writing automation. Designed for traditional tales, folk stories, and historical narratives. Covers the full pipeline from story analysis to upload-ready assets.

9-Wave workflow Script writing TTS / SFX Storyboard CSV Image / Video Gen

Variables

PROJECT (required) β€” Path to the episode folder

🎭 Story Engine Genres

The story-engine skill supports three genres, automatically selected by your input language and topic keywords:

Genre Language Style Examples
yadam Korean (ν•œκ΅­μ–΄) Korean historical tales β€” Joseon dynasty court intrigue, folk tales, ghost stories "μ•Όλ‹΄ λŒ€λ³Έ 써쀘", "ep11 μ‹œμž‘ν•˜μž"
dark-history English Western dark history β€” Medieval mystery, Tudor intrigue, gothic tales, true crime "Write a script about Salem witch trials", "Start ep1 - Jack the Ripper"
bespoke Any language Universal β€” synthesizes meta-prompts from 3–5 user-provided successful reference scripts. Any topic, any language "Write an economy YouTube script" (needs 3–5 reference scripts)

Auto-detection: Genre is auto-detected from your input language and topic keywords. Use --genre yadam, --genre dark-history, or --genre bespoke to override.

yadam Meta-Prompts

5 Korean meta-prompt files: synopsis, preflight, screenplay, narrative, suspense

dark-history Meta-Prompts

5 English meta-prompt files based on Google DeepMind's Dramatron framework

bespoke Meta-Prompts

Per-output-language ko/en files (5 each) + a per-episode supplement synthesized from 3–5 user reference scripts

πŸ”„ 9-Wave Workflow

The Story Engine follows a strict 9-Wave pipeline with gate checks between phases.

W1

Story Design

Analyze references and fact-check to identify patterns and strengths, then set the story direction. Branches between new production and rewrite.

W2

Synopsis + Preflight

Create a 20-chapter Setup → Rising → Climax → Resolution → Hook synopsis, then review structure, foreshadowing, and suspense before writing.

W3

Script Writing + Review User Approval Required

Write the full script in 5 parts (Introduction → Development → Twist → Resolution → Hook); a sub-agent reviews up to 5 rounds. Ends with a user approval checkpoint.

W4

Production Extract

Split the script into narration, character voices, and SFX cues, then validate.

W5

TTS / SFX Generate

Generate audio with AI TTS APIs (ElevenLabs, Typecast) and sound effects, with timecode verification.

W6

Storyboard CSV

Create references.csv and scenes.csv for image/video generation with AutoFlowCut, reviewed via batch QA.

W7

Image Production User Approval Required

Batch-generate reference and scene images/videos via AutoFlowCut MCP tools and run image QA. Ends with a user approval checkpoint.

W8

Assembly

SFX scene matching, audio import, and CapCut export assemble the edit project.

W9

Upload Info

Prepare title, description, tags, and thumbnail for YouTube upload.

βš™οΈ Skill Management

list_skills()

View all available and installed skills with their status and metadata.

install_skill(name, variables)

Install a skill with template variable substitution. The skill file is copied to ~/.claude/skills/.

uninstall_skill(name)

Remove an installed skill from the skills directory.

πŸ› οΈ Creating Custom Skills

You can create your own skills to automate any workflow.

File Structure

skills/
  {skill-name}/
    SKILL.md          # Workflow instructions
    metadata.json     # Name, description, variables
    docs/             # Reference documents (optional)

Template Variables

Use {{VAR_NAME}} placeholders in SKILL.md. They are replaced with actual values during installation.

Example: {{PROJECT}} in the skill file becomes /Users/me/workspace/ep01 after installation.