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

Video Editor

ASecurity

Edit compelling videos with narrative structure, pacing, cuts, sound design, and color workflow.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreact

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill video-editor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Video Editor?

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

Security grade badge for Video Editor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-video-editor/badge)](https://www.skillsdirectory.com/skills/aicodedecode-video-editor)

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: video-editor
description: Edit compelling videos with narrative structure, pacing, cuts, sound design, and color workflow.
category: video
---

## Overview

Editing is where footage becomes story: the selection, arrangement, and rhythm of shots determine
whether viewers watch to the end or click away in ten seconds. This skill covers the creative
editing craft — narrative structure, pacing, cutting technique, sound design, and color — plus the
project organization that keeps complex edits manageable.

## When to use

- Editing YouTube videos, shorts, documentaries, or marketing videos

- Structuring raw footage into a compelling narrative

- Improving pacing and retention in existing edits

- Learning cutting technique, transitions, and sound design

- Organizing large editing projects and media

## Core concepts

- - **Story first, software second.** Before touching the timeline: what's the video about in one
  sentence? What's the hook (first 15 seconds), the turns, the payoff? Edit to the story, not to the
  footage you happen to like.
- - **The hook is everything.** First 5-15 seconds decide retention: state the payoff, pose the
  question, or show the most compelling moment. No logos, no "hey guys welcome back," no
  throat-clearing.
- - **Cutting on action and emotion.** Cut during movement to hide the cut; cut to reactions to land
  emotion. J-cuts (audio leads video) and L-cuts (video leads audio) create fluid, professional flow
  — hard cuts on silence feel amateur.
- - **Pacing = retention.** Vary rhythm: fast montages for energy, held shots for weight. Cut
  ruthlessly — every second must earn its place. If you're bored watching your own edit, the
  audience left minutes ago.
- - **Sound design is 50% of the edit.** Music (licensed, leveled under dialogue), SFX (whooshes,
  impacts, ambience — subtle layers sell reality), and clean dialogue. Mute the video: does the
  audio alone tell a story?
- - **Color: correct then grade.** Correction (fix white balance, exposure, match shots) before
  grading (creative look). Consistent color across shots is more important than a fancy LUT —
  mismatched shots scream amateur.

## Practical workflow

1. 1. **Ingest and organize.** Folder structure (footage/audio/graphics/exports), descriptive bin
   names, sync multi-cam/audio, mark selects. An hour of organization saves ten of hunting.
2. 2. **Build the radio edit.** Cut the story using audio first (dialogue/voiceover) — if it works
   as audio-only, the visuals will support it. Arrange selects into the narrative arc: hook → setup
   → development → payoff.
3. 3. **Rough cut.** Lay visuals to the radio edit. Don't polish — focus on structure and pacing.
   Watch through: does the story flow? Fix structure now; it's 10x harder later.
4. 4. **Refine the cut.** Tighten every edit point (trim dead air, cut on action), add B-roll to
   cover cuts and illustrate points, pace to the music's energy. The 10% trim: cut your favorite
   shot if it doesn't serve the story.
5. 5. **Sound design pass.** Level dialogue consistently, add music (duck under speech), layer SFX
   and ambience, check the mix on headphones and laptop speakers. Normalize loudness to platform
   spec.
6. 6. **Color pass.** Correct all shots (exposure, WB, match), then apply the creative grade
   consistently. Check skin tones — the fastest grade quality test.
7. 7. **Graphics and titles.** Lower thirds, titles, captions — restrained and on-brand. Burned-in
   captions for social (85% watch muted). Keep text readable at phone size.
8. 8. **Export and review.** Export per delivery spec, watch the full export on the target device,
   get fresh eyes on it, fix, and re-export. Never ship the first export unwatched.

## Common pitfalls

- **Slow openings.** 60 seconds of intro before the content. The hook goes first — always.

- - **Falling in love with footage.** Keeping a beautiful shot that breaks pacing or story. Kill
  your darlings; the audience never saw what you cut.
- - **Transition abuse.** Star wipes, 3D flips, and spin transitions. Cut or dissolve 95% of the
  time — fancy transitions call attention to the edit instead of the story.
- - **Neglecting audio.** Great visuals with peaking, echoing, or inconsistent audio. Fix audio
  before adding a single effect.
- - **No B-roll discipline.** Talking head for 10 straight minutes. B-roll covers cuts, illustrates
  points, and resets attention — plan for it in the shoot, not the edit.
- - **Skipping the fresh-eyes review.** Editing so long you can't see it anymore. A new viewer
  catches pacing dead spots and confusing moments you've gone blind to.

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', ...

698461 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 →