social-video-folder-autocutter
Skill19 starsChanged 6 months agoMITView on GitHub
Plan repeatable hard-drive folder-to-video pipelines for speaker-led multicam content, including 9:16 Reels/Shorts up to 3 minutes at 1.1x talking speed and 16:9 long-form 3-7 minute cuts, with Resolve handoff, Editframe asset generation, audio/caption gates, and narrative beat planning.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kitloomlk-stack/davinci-resolve-video-kitword for word, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kitloomlk-stack/davinci-resolve-video-kit★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- davinci-resolve-audio-cleanup-podcastSkill
- davinci-resolve-color-grade-webcamSkill
- davinci-resolve-computer-use-trainingSkill
- davinci-resolve-cut-screen-recordingSkill
- davinci-resolve-devrel-project-templateSkill
- davinci-resolve-export-multi-platformSkill
- davinci-resolve-setupSkill
- davinci-resolve-social-editorSkill
- davinci-resolve-titles-and-lower-thirdsSkill
- davinci-resolve-troubleshootingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 12 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this before editing when the user wants a repeatable pipeline from a folder of camera/audio files into social or long-form cuts.
- Very specific: line 18
run the DaVinci skill probe_media.py.
- Very specific: line 32
prefer wide/medium/close-up sequences over isolated filler shots.
- Distinctive: line 36
If the speaker is physically demonstrating a concept, prioritize that performance over generic B-roll.
- Distinctive: line 38
Keep B-roll source URLs/license notes in the plan, and keep raw B-roll sources disabled on a separate Resolve track for HITL replacement.
- Distinctive: line 39
Use Coverr as the default free B-roll source when the project lacks enough native visual evidence.
- Distinctive: line 42
Prefer Coverr clips that can function as visual evidence for a spoken claim.
- Distinctive: line 57
Use this loop when a prior cut is close and the user says it is nearly postable:
- Distinctive: line 59
Preserve the liked picture cut: Do not re-edit the spine unless the user asks.
- Distinctive: line 61
Keep caption text spoken-first: Do not replace spoken captions with topic cards.
- Distinctive: line 64
Only then hillclimb B-roll: Add B-roll where it solves a specific edit problem: jump cut coverage, proof of a claim, visual explanation, …
- Distinctive: line 81
Use Editframe in parallel for motion assets, not as the primary NLE when the user expects Resolve source layers.
- Distinctive: line 92
Avoid using Editframe as the only deliverable for source-camera editing unless the user explicitly wants a rendered web-video output.
- Distinctive: line 96
Never call the job done unless these artifacts exist:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Social Video Folder Autocutter
Use this before editing when the user wants a repeatable pipeline from a folder of camera/audio files into social or long-form cuts.
Output Profiles
- Vertical social:
1080x1920, 9:16, up to 3 minutes, default 1.1x speed for speaker-led sections, Netflix-style captions, source layers preserved in Resolve. - Horizontal long-form:
1920x1080, 16:9, 3-7 minutes, default normal speed, lower thirds/captions optional, source layers preserved in Resolve.
Required Pipeline
- Scan the folder:
- run the DaVinci skill
probe_media.py; - run
audio_quality_audit.py; - identify camera ISOs, HQ audio, intro/bumper, brand files, old renders, and existing Resolve exports.
- run the DaVinci skill
- Make a story plan:
- hook/agenda,
- body beats,
- recap/CTA,
- rejected or risky segments.
- Build edit decisions:
- source file, in/out, angle, reason, transition, crop, audio source, caption text.
- reject word-boundary-only cuts.
- Build a B-roll coverage plan:
- assign B-roll only where it proves a claim, establishes the event world, covers a jump cut, compresses time, or gives the audience an emotional/visual release.
- tag every B-roll candidate as
wide,medium,close-up,insert/detail,environment,screen/product, orhuman moment. - prefer wide/medium/close-up sequences over isolated filler shots.
- require source page/licensing metadata for stock footage and store it with the manifest.
- reject low-opacity overlays over faces unless the user explicitly asks for texture; default to full-opacity cutaways or designed picture-in-picture.
- On warm-traffic educational reels, use B-roll sparingly as proof/coverage. Keep the speaker on screen for trust-building beats, and reserve stock inserts for claims about work, learning, planning, community, or tool use.
- If the speaker is physically demonstrating a concept, prioritize that performance over generic B-roll. Use the board/prop as a quick visual aid, not a long replacement for the speaker.
- Reject static whiteboard/slide replacements longer than
3s-5sunless the user explicitly asks for a screen-recording style lesson. For Instagram, the speaker should remain visible across spoken educational beats. - Keep B-roll source URLs/license notes in the plan, and keep raw B-roll sources disabled on a separate Resolve track for HITL replacement.
- Use Coverr as the default free B-roll source when the project lacks enough native visual evidence. Store search query, source URL, creator/source attribution, license URL, download path, and rejection reason for any candidate not used.
- Coverr licensing/API notes must be recorded with the manifest: free downloads require attribution credit unless the account/license says otherwise; API usage requires clickable Coverr attribution; do not use Coverr assets for AI training/datasets or to build a competing stock/video service.
- For Chai With Jai workshop promos, default search intents should include:
small business owner,entrepreneur workshop,business planning,whiteboard,team collaboration,laptop work,coffee meeting,Jersey City,AI technology,coding,marketing campaign, andcommunity event. - Prefer Coverr clips that can function as visual evidence for a spoken claim. Reject generic city lights, abstract technology, slow lifestyle filler, or anything with identifiable brands/trademarks unless the usage is clearly safe.
- Generate review artifacts:
- low-res proxy or stills for critic review,
- audio ranking JSON,
- caption preview,
- Resolve/FCPXML/EDL plan.
- Build the real handoff:
- Resolve layered timeline for final editing,
- original repair audio disabled,
- clean dialogue and music separated,
- graphics/captions/B-roll on separate tracks,
- timeline audit passes.
Winning Instagram Reels Loop
Use this loop when a prior cut is close and the user says it is nearly postable:
- Preserve the liked picture cut. Do not re-edit the spine unless the user asks. Export or locate a picture spine without burned captions when possible.
- Caption from actual speech timing. Extract dialogue from the liked cut, run Whisper word-level transcription, and build short burned-in phrase captions. Correct only high-confidence domain terms such as names, event titles, dates, and obvious ASR artifacts.
- Keep caption text spoken-first. Do not replace spoken captions with topic cards. Topic cards may remain as a separate top lane, but the lower caption lane must match what the speaker says.
- Verify phone-safe stills. Inspect opening, mid-body, B-roll/whiteboard, CTA, and closing frames. Captions must avoid the speaker's mouth/chin and Instagram's bottom UI region.
- Verify audio. Target
-14to-16 LUFSintegrated, true peak below-1 dBTP, with music ducked under speech. - Only then hillclimb B-roll. Add B-roll where it solves a specific edit problem: jump cut coverage, proof of a claim, visual explanation, location/event context, or emotional reset.
Required Output Artifacts For Repeat Use
For each folder cut, create or update:
story_plan.mdedit_decisions.csvor.jsonbroll_plan.jsonbroll_asset_manifest.jsoncaption_chunks.txtcaptions.assor Resolve caption trackverification_report.json- Resolve timeline or handoff report
Editframe Role
Use Editframe in parallel for motion assets, not as the primary NLE when the user expects Resolve source layers.
Good uses:
- animated branded bumpers,
- Netflix-style/word-highlight caption assets,
- lower thirds,
- waveform/title cards,
- social-safe graphic overlays,
- fast HTML/React review proxies.
Avoid using Editframe as the only deliverable for source-camera editing unless the user explicitly wants a rendered web-video output. Editframe renders can be imported back into Resolve as V3/V4 graphics or bumper layers.
Handoff Contract
Never call the job done unless these artifacts exist:
- media manifest,
- story plan,
- edit decisions,
- audio quality audit,
- caption artifact or burned-in review,
- layered Resolve timeline or interchange file,
- timeline audit report.
Useful Command
python3 skills/social-video-folder-autocutter/scripts/create_folder_cut_brief.py \
/path/to/project-folder --out /path/to/project-folder/output/folder_cut_brief.jsonThen use davinci-resolve-social-editor for the Resolve build.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

