Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Storyboard Artist

ASecurity

Visualize scripts and concepts with storyboards covering shot composition, pacing, and camera language.

2 stars
0 votes
8 copies
39 views
Added 9/29/2026
ai-agentsgoreactexpressaws

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill storyboard-artist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Storyboard Artist?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Storyboard Artist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-storyboard-artist/badge)](https://www.skillsdirectory.com/skills/aicodedecode-storyboard-artist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: storyboard-artist
description: Visualize scripts and concepts with storyboards covering shot composition, pacing, and camera language.
category: creative-design
---

## Overview

Storyboards are filmmaking's first draft: they translate scripts into shots,
revealing pacing
problems, unclear geography, and weak visual storytelling before a single frame
is shot. A good
storyboard artist thinks like a director — camera language, staging, and cutting
— and draws just
clearly enough to communicate, never more. Speed and clarity beat polish.

## When to use

- Storyboarding films, commercials, or animation

- Pre-visualizing product videos or explainers

- Planning shot sequences for client approval

- Communicating directorial vision to a crew

- Learning visual storytelling and film grammar

## Core concepts

- - - **Film grammar.** Shot sizes (extreme wide → close-up) control intimacy
  and information; angles
  (low = power, high = vulnerability) control psychology; movement (pan, dolly,
handheld) controls
  energy. Every shot choice should be intentional.
- - - **The 180-degree rule.** Keep the camera on one side of the action axis or
  the audience loses
  spatial orientation. Break it only deliberately (disorientation as effect).
- - **Staging and composition.** Rule of thirds, leading lines, depth layers
  (foreground/midground/background), and eye-lines. Each panel should guide the
eye to the story
  point instantly.
- - - **Cutting on action and emotion.** Storyboards show not just shots but why
  we cut: to follow
  action, to reveal reaction, to compress time. Note the motivation for key
cuts.
- - - **Clarity over beauty.** Storyboard panels are communication tools, not
  gallery pieces. Clear
  staging, readable expressions, and accurate geography beat rendered shading
every time. Directors
  storyboard in stick figures when needed.
- - - **Pacing on the page.** Panel density and size suggest timing: big panels
  linger, sequences of
  small panels accelerate. Animatics (timed slideshows) test pacing before
production.

## Practical workflow

1. 1. 1. **Break down the script.** Identify beats: what changes in each moment?
   Mark the emotional
   turns — those get the close-ups. List locations, characters, and key actions
per scene.
2. 2. 2. **Choose coverage.** For each beat: the master shot (geography), then
   coverage (close-ups,
   inserts, reactions). Plan the minimum shots that tell the story —
over-coverage wastes shoot
   days.
3. 3. 3. **Thumbnail the sequence.** Rough panels, fast: one thumbnail per shot,
   focusing on
   composition and camera. Explore 2-3 framings for key moments.
4. 4. 4. **Refine key panels.** Clean up staging, add arrows for camera/subject
   movement, note shot
   size and lens feel, add dialogue/action captions. Every panel answers: what
do we see, what
   moves, what do we hear?
5. 5. 5. **Check the flow.** Read the board as a film: does geography stay
   clear? Does the cutting
   build? Are there jump cuts or confusing transitions? Fix on paper — it's free
here.
6. 6. 6. **Add technical notes.** Camera movement, transitions
   (cut/dissolve/whip), VFX notes, timing
   estimates. The board becomes the shoot's shared reference.
7. 7. 7. **Present and revise.** Walk stakeholders through the board as the
   film: narrate it. Note what
   confuses them — that's what would confuse the audience. Revise before
production locks.

## Common pitfalls

- - - **Over-rendering panels.** Spending hours shading a panel that gets
  redrawn after the first
  script revision. Communicate clearly, render later (if ever).
- - - **Unclear geography.** Audience can't tell where characters are relative
  to each other.
  Establish with a wide, maintain with the 180 rule, re-establish after complex
movement.
- - - **Every shot a close-up (or wide).** No variety in shot sizes flattens the
  visual rhythm. Vary
  deliberately: wide for context, close for emotion.
- - - **Ignoring the cut.** Drawing beautiful panels with no thought to how they
  connect. Filmmaking
  is the cut — plan transitions, not just frames.
- - - **Too many/few panels.** Over-boarding every micro-beat wastes time;
  under-boarding leaves the
  crew guessing. Board the story beats and the tricky technical shots.
- - - **No movement notation.** Static panels with no arrows or notes leave
  camera and subject
  movement ambiguous — the most common storyboard communication failure.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →