beat-sync-montage skillA
beat-sync-montage is agent-read markdown (skill) from 0xsline/openchatcut: Plan and build a finished beat-synced montage where cut placement serves the content, not just the metronome. Use for 卡点混剪, 卡点剪辑, 踩点视频, beat-sync montage, rhythm edit, 节奏剪辑, 音乐驱动剪辑, or when the user wants cuts that land on the beat..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Beat Sync Montage Use this workflow when the edit should be driven by music. The failure mode to avoid is a metronome edit: every cut technically lands on a beat, and the result still feels mechanical, tiring, or unrelated to what is on screen. This workflow decides **what** to cut and **why**. It does not re-explain the music tools — when you reach an execution step, follow `music-intelligence` for `analyze_music`, `music_edit_plan`, and `sync_cuts_to_music`. Load it there. This is a OpenChatCut-native workflow. Use the current project, source assets, asset-frame inspection, AV/script context, and OpenChatCut editing tools. ## When to switch workflows - Beat-synced photos on a locked, empty track → `music-intelligence` handles this directly with `music_image_plan`. This workflow is for video montage. - One long source cut to speech rhythm → `long-video-to-shorts`. - Many clips packaged as highlights without music driving the cut → `multi-clips-to-reels`. - N distinct beat-synced variants from one pool → `batch-montage-variants`, using this workflow for each cut. ## Workflow …
Read the whole file at its exact version.
How to install
mdr add 0xsline/openchatcut/beat-sync-montage@git:20260907.033479fmdr add 0xsline/openchatcut/beat-sync-montage@sha256:aa4f43ff2061c283Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_5r4giogccqkrui43)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4900 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
0xsline/openchatcut · 2,013 stars · license AGPL-3.0 · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5r4giogccqkrui43 GET https://markdownregistry.com/api/v1/resolve?ref=0xsline/openchatcut/beat-sync-montage GET https://markdownregistry.com/api/v1/blob/aa4f43ff2061c2833af0c9c7f72eb0327558711644dc8e34696fc7ca17c911d1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.