Clipping Channel
Long-form in, clips out. The moments worth cutting found, reframed, captioned, and posted on cadence.
By naïve·media/clipping v1.0.0
What it is
Point it at a podcast, a stream, or a back catalogue you hold the rights to. A clipper and a channel manager run it between them: the manager decides what is worth cutting next, the clipper takes the source it was pointed at and cuts the few moments that carry — hook first, one idea, vertical, captioned. It cuts from nothing you did not name. Every clip lands in a review queue, and the queue is the only way out.
It cuts only from the source you named. A clip from anywhere else is a rights problem, so the clipper stops instead of guessing
A few vertical cuts per source, each one hook-first, one idea, under sixty seconds — not every moment the scorer liked
The manager points the clipper at what is worth cutting next, so the back catalogue gets worked through, not just the newest upload
Every cut lands as a pending post with its caption drafted. Nothing reaches an account without you
Ideal for Editors, studios, and creators who want a clipping operation running across many accounts at once.
The week it runs
media/clipping · v1.0.0 · published Sep 7, 2026
4 timers are provisioned with this template — 22 unattended runs a week, $30 of budget between them. Each fire opens a session with the message below and spends against its own cap. These are the words your crew is sent, not a summary of them.
- 07:00every day at 07:00clipper0 7 * * *America/New_York
Cut the next clips. Read the source channel the operator named (channel.get_onboarding) and the plan and queue (channel.list_posts), take the source video the channel manager pointed you at that has no clips filed against it yet, and cut the few most engaging vertical clips from it. File each as a pending post. Cut nothing from a source the operator has not named — if there is no named source with work left in it, file nothing and stop.
$2 / fire - 08:00every day at 08:00channel-manager0 8 * * *America/New_York
Sweep the queue. Read every pending and ready post (channel.list_posts), and on each one fix the caption, the kind and the scheduled day with channel.update_post so the operator opens the dashboard to rows that are ready to approve. Flag in the caption anything you could not fix. Approve, reject and publish are the operator's — never yours.
$1 / fire - 09:00every Monday at 09:00channel-manager0 9 * * 1America/New_York
Plan the week. Read the channel profile and its niche (channel.get_onboarding), what has posted and what is still queued (channel.list_posts), and the looks available to produce in (channel.list_style_templates). Then file this week's plan: one brief per planned slot, each naming the style template, the account it is for (channel.list_accounts) and the day it should go out. Brief the specialist through the plan, not by publishing anything yourself.
$2 / fire - 18:00every day at 18:00channel-manager0 18 * * *America/New_York
Read the comments on what this channel has posted today and on the pieces still gathering them, and reply in the channel's voice. Every reply acts on a connected account, so it stops at the operator's Approvals screen with its text in front of a person — write the reply you would stand behind, and leave the ones you would not.
$1 / fire
The crew
read from the media release
The 2 agents naive up provisions into your organization, and the timers each one owns. Every agent runs under the same cap: $10 a day, $2 a task.
clipper
Cuts the most engaging vertical clips out of the channel's source videos, captions them, and files them as pending posts.
1 timer·07:00·$14/wk
anthropic/claude-sonnet-5
channel-manager
Runs the channel: plans the calendar, drafts captions, manages the post queue and replies to comments. Never publishes without an approved post.
3 timers·08:0009:0018:00·$16/wk
anthropic/claude-sonnet-5
What stays yours
The same three rules across every template. They are the blueprint's, not the crew's — an agent cannot widen them.
Nothing publishes itself
Every tool that acts outside your organization — a post, an email, a reply — is granted
ask, notallow. The call parks the session with its arguments in front of you and waits. Approval is a person, every time.A budget it cannot raise
$10 a day per agent and $2 a task, declared in the template and enforced by the platform. A run that would exceed its cap stops rather than spends.
Denied by default
An agent is offered the tools its template names and nothing else. Everything it was not granted is denied by name — the shell included, which is also why a content agent never provisions a machine it would not use.
What it ships
v1.0.0
A template is a repo: the apps below, their server, and a naive.config.ts declaring the crew. Clone it, bind it to your organization, bring it up.
channel
fullstackMedia channel dashboard — post queue, style templates, accounts, analytics.
App, server and database — serves its own MCP endpoint to the crew
build 613ab4bb410d48c0…
- $ naive template media --template clipping# clone the blueprint repo
- $ naive claim --key sk_...# bind the clone to your organization
- $ naive up# provision the apps, the agents, their budgets
The number
Measured, not modelled: live accounts run autonomously, against a control arm.
Launch your clipping channel
2 agents, 1 app, a budget. One command.