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 Editing

ASecurity

Editorial decisions for talking-head video: what to cut, pacing, filler removal, structure of the final edit.

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

Works with

cli

Security Analysis

A100/100

Pro scans all 15 files and shows the line behind each finding

Scanned 9/29/2026

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

Installs into .claude/skills of the current project.

Are you the author of Video Editing?

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

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

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-editing
description: Editorial decisions for talking-head video: what to cut, pacing, filler removal, structure of the final edit.
---

# Video Editing Skill

## When to Use

Apply this skill when making editorial decisions for talking-head content:
where to cut, what to remove, how to pace, and how to structure the final edit.

## Tools

| Tool | Role |
|------|------|
| `transcriber` | Analyze speech for filler words, dead air, false starts |
| `video_trimmer` | Execute cuts and speed adjustments |
| `frame_sampler` | Sample frames to evaluate visual quality at potential cut points |
| `video_compose` | Assemble the final edit |

## Editing Principles for Talking Heads

### What to Cut

1. **Filler words:** "um", "uh", "like", "you know" — cut at word boundaries using word timestamps.
2. **False starts:** When the speaker restarts a sentence, keep only the final take.
3. **Dead air:** Silence longer than 1.5 seconds should be trimmed to ~0.5 seconds.
4. **Off-topic tangents:** If the speaker wanders, cut to the next relevant segment.
5. **Repeated points:** Keep the best delivery, remove redundant takes.

### What NOT to Cut

- **Breath pauses:** Natural 0.3-0.8 second pauses between sentences. These sound natural.
- **Emphasis pauses:** Intentional pauses for dramatic effect.
- **Reactions and transitions:** Verbal bridges like "So..." or "Now..." that provide flow.

### Cut Technique

- **J-cut:** Audio from the next segment starts ~0.5s before the visual cut. Makes transitions feel smooth.
- **L-cut:** Audio from the current segment continues ~0.5s after the visual cut. Maintains continuity.
- **Hard cut:** Instant transition. Use at major topic changes.

### Pacing

- **Short-form (< 60s):** Aggressive cuts. Minimal dead air. High energy.
- **Medium-form (1-10 min):** Balanced. Keep natural pauses for breathing room.
- **Long-form (> 10 min):** Let scenes breathe. Only cut obvious problems.

## Edit Decision Structure

The `edit_decisions` artifact should include:

- **cuts:** Ordered list of segments to keep (source, in/out points, speed)
- **overlays:** Timed overlay placements (images, diagrams, lower thirds)
- **subtitles:** Subtitle configuration (enabled, style, source file)
- **music:** Background music settings (asset, volume, ducking, fades)
- **transitions:** Transition type and timing between cuts

## Quality Checklist

- [ ] No visible jump cuts (smooth transitions between segments)
- [ ] Audio doesn't pop or click at cut points
- [ ] Pacing matches the content energy and target platform
- [ ] Speaker's face is never covered by overlays
- [ ] All cuts are at word boundaries (not mid-word)

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

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