multi-clips-to-reels skillA
multi-clips-to-reels is agent-read markdown (skill) from 0xsline/openchatcut: Turn multiple product shots, event footage, travel clips, gameplay moments, UGC/product footage, B-roll, or mixed media into social-ready reels, highlights, recaps, or montage-style short videos from existing project media..
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
# Multi Clips to Reels Use this workflow when multiple raw clips or assets carry the output. The task is to select, sequence, and package the strongest footage into one or more reels, highlights, recaps, or short videos. This is a OpenChatCut-native workflow. Use the current project, source assets, asset-frame inspection, AV/script context, and OpenChatCut editing tools. Use the current timeline when it already contains relevant cuts or for final verification; do not depend on timeline screenshots as the primary way to understand raw source clips. Do not depend on external download, transcription, ffmpeg, or auto-crop pipelines unless the user explicitly asks for an external source that is not already in the project. ## Workflow 1. Read the project state before editing. Inventory usable source assets: duration, aspect ratio, visual subject, motion/energy, audio quality, duplicates, current timeline state when relevant, obvious hero shots, and fixed-role assets such as logos, QR codes, product photos, brand screenshots, or supplied audio. …
Read the whole file at its exact version.
How to install
mdr add 0xsline/openchatcut/multi-clips-to-reels@git:20260801.23ff26cmdr add 0xsline/openchatcut/multi-clips-to-reels@sha256:0ceb884dbd3eacb7Pin 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_xdc6xq7gcat7uuan)
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 (5744 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_xdc6xq7gcat7uuan GET https://markdownregistry.com/api/v1/resolve?ref=0xsline/openchatcut/multi-clips-to-reels GET https://markdownregistry.com/api/v1/blob/0ceb884dbd3eacb7dafe2d5ee7d1e0be13a05e8849927cc9b6d6a387180903aa
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.