Video Editing Agent (Descript via MCP)

Skill packs › Skill

Video Editing Agent (Descript via MCP)

Edit video in Descript via MCP — clean filler/pauses, add captions and simple transitions, cut a captioned highlights reel or short clips, and publish a share/download link. Non-destructive. Use when someone wants raw footage (talks, interviews, demos) turned into a finished cut without touching the Descript UI, e.g. a speaker reel.

Skill file video-editing-agent.md · last updated Aug 2, 2026

How to run it. Download any pack from the skill-pack directory, unzip it into your Claude project folder, and this skill is one of the files inside. You do not paste it anywhere — the agent reads it when the job calls for it.

Turn raw footage into a finished, captioned cut without anyone opening the Descript UI. This is the editing companion to video-repurposing-agent (which turns a talk into articles): this one produces the video deliverable — a cleaned talk, a captioned highlights reel, or short vertical clips — and hands back a share/download link. Dennis teaches “Claude operates Descript to edit your videos”; this is that, on tap.

Non-negotiables (safety first — this touches real footage):

  • Never edit a master destructively. Duplicate into a NEW project/composition (or import the media fresh) and edit the copy. Never delete media or overwrite the source.
  • Publish/export only — return share + download URLs; never replace an existing publish without being told to.
  • Loop to done and self-verify: poll wait_for_job until each job completes, then confirm and DISPLAY the resulting share/download URLs (Descript MCP requires you to surface them).
  • Draft/notify only — never send anything on the client’s behalf.

The job card (fill once per deliverable)

  • Source: a Descript project name/id (use list_projects / list_folders to find it) OR a media URL to import_media.
  • Deliverable: clean-talk (remove filler + long pauses, captions, light transitions, keep full length) · reel (60–120s captioned highlights montage) · clips (3–6 short vertical cuts for social).
  • Brand: caption style, intro/outro if any, aspect ratio (16:9 talk / 9:16 clips), target length.
  • Publish target: Descript share link (default) and/or download for upload elsewhere.

Steps

  1. Find the source. list_projects (filter by name) or list_folders. Confirm with get_project (media files, compositions, existing publishes — reuse an existing share URL instead of republishing when one already fits).
  2. Work on a copy. Create/import into a new project or a new composition so the master is untouched.
  3. Edit via prompt_project_agent (natural-language editing — do it in clear passes, verifying each):
  • Remove filler words (“um”, “uh”, “you know”) and long silences.
  • For reel/clips: select the strongest 60–120s (named guests, real numbers, a framework, a story only they can tell — the same STRONG-content test as the repurposing skill), assemble the montage, add captions.
  • Add captions (prefer a manually-corrected transcript; fix proper nouns against known entities), a simple lower-third if brand supplies one, and clean cut/transition timing.
  • Keep quotes verbatim; never fabricate footage or words.
  1. Export the transcript (export_transcript) and hand it to video-repurposing-agent → definitive-article-writer so one recording becomes both a clip AND site articles (the Content Factory loop).
  2. Publish (publish_project) as video (reel/clips) or the clean talk; wait_for_job; capture and DISPLAY the share + download URLs.
  3. Report one run note: source → deliverable(s) → share/download URLs → transcript path → what a human still needs to do (e.g. approve before posting). File a Skill-Learnings note if the run taught something.

Pairings

  • Upstream: raw talks/interviews/demos (e.g. the “Dennis Reel” project, conference interviews).
  • Downstream: video-repurposing-agent → definitive-article-writer → jennifer (grade A-) → dollar-a-day-strategist (put $1/day behind the winning clip). The proof pattern is Marko Sipila’s: phone-shot interviews → clips → repurposed articles → $1/day → customers.
  • Reference: blitzmetrics.com/build-agents/ (Descript operation), blitzmetrics.com/content-factory/.

Registered as a Cowork skill 2026-07-25. Wired to the descript-reel-editor scheduled task (weekly): it edits any Descript project whose name contains the tag [edit] (a safe opt-in that can never grab a master by accident), then reports share links. Trigger ad hoc any time with a job card.

Other skills: ai-search-visibility · boil-the-ocean · client-access-checklist · client-relationship-cadence · content-agent · content-factory

The full run order is on the skill-pack directory. Every skill here is one task from the Task Library — the library is the catalogue of what can be done; a pack is the subset you install; an agent is who runs it.

Where this sits in the system

A skill is a document. A pack is a folder of documents. Neither one does any work. Work happens when a job runs those skills on a schedule, checks its own output, and keeps its files somewhere it can read them again tomorrow. That is the whole difference between owning skills and having an agent.

  1. Skill — one task, written down to a standard, so an agent can run it without you in the room. There are 239 of them.
  2. PackYOU ARE HERE — those skills bundled into a download you install in one paste.
  3. Agent — a named role with a job description — not a chat window you retype every morning.
  4. Job — a schedule, a QA cycle, and somewhere to keep working files. Miss any of the three and nothing runs twice.
  5. Proof — every finished run written up in public, and the lesson pushed back into the skill.

The map: The System · every asset: Asset Tracker · next door: Asset Tracker.

Scroll to Top