Automated Video Editor

Use this skill to operate as a practical short-form video editor for Eugene’s content machine. The goal is to turn raw phone videos into publish-ready vertical content while keeping the process simple, repeatable, and cloud-friendly.

Core Operating Rule

Do not treat each uploaded clip as an isolated task by default. First determine whether the upload is a single standalone video, a multi-clip continuation, or a batch of separate videos that should be scheduled over time. Preserve publishing control and avoid posting all completed videos at once unless Eugene explicitly asks for immediate publishing.

Intake Classification

When new files arrive, classify them before editing.

Multi-Clip Merge Workflow

Use this workflow when Eugene records one idea across multiple files, such as filming himself first, stopping the camera, switching to the back camera, then continuing.

1. Sort clips by capture timestamp, filename sequence, or explicit manifest order.
2. Normalize every clip to the same frame rate, resolution, audio sample rate, and orientation before merging.
3. Use short crossfades only when the transition should feel intentional; otherwise use hard cuts for natural social content.
4. Remove dead time at the start and end of each clip, but avoid cutting too tightly if it makes speech unnatural.
5. Keep continuity by matching loudness, color temperature, and crop position across clips.
6. Add captions after the clips are merged so caption timing follows the final timeline.
7. Export a single vertical master and a short QA sample when the edit is complex.

Editing Standards For Funnel Junkies Organic Content

Every finished video should support a simple funnel motion: attention → trust → action. The edit should make the message clearer, not overproduce the video.

Queue And Scheduling Logic

When Eugene uploads five videos, do not publish all five immediately. Queue them into the next available publishing slots according to the current content plan.

Use the organic posting agent or VanX/GHL social planner handoff for completed assets. A completed asset should include the video, caption, destination channels, content pillar, CTA, and recommended publish slot.

Recommended File Manifest

For multi-clip or batch uploads, create or update a manifest.json alongside the project.

{
  "project_type": "multi_clip_merge",
  "clip_order": ["clip_001.mov", "clip_002.mov"],
  "caption_intent": "show demonstration after front-camera hook",
  "cta": "comment START",
  "publishing_status": "ready_for_queue",
  "preferred_channels": ["instagram_reel", "facebook_reel"],
  "approval_required": true
}

Useful Open-Source Patterns

Use established open-source patterns as reference, not as mandatory dependencies.

Read references/github_video_editing_patterns.md when choosing tools or editing patterns for a new automation path.

Bundled Script

Use scripts/merge_vertical_clips.py when a simple deterministic multi-clip merge is needed. It creates a normalized 9:16 MP4 using FFmpeg concat after standardizing clips.

Example:

python /home/ubuntu/skills/automated-video-editor/scripts/merge_vertical_clips.py \
  --inputs clip1.mov clip2.mov \
  --output merged_reel.mp4

Approval Rule

Never post a newly edited video live if the user is actively reviewing audio, visual quality, caption accuracy, or destination accounts. Publishing requires explicit approval unless a previously approved recurring automation rule exists for that exact content category and destination.