Run any Skill in Manus with one click

Get Started

brief-to-script

Stars12

Forks3

UpdatedApril 29, 2026 at 00:14

Turn a topic, packaging hint, or blueprint into a script file that the rest of the pack can use.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

45ck

45ck/content-machine

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	brief-to-script
description	Turn a topic, packaging hint, or blueprint into a script file that the rest of the pack can use.

Brief To Script

Use When

The user wants a fresh script from a topic or short brief.
The agent already has packaging, research, or blueprint files and needs the next script file.
Claude Code or Codex should produce a reusable script.json rather than freeform prose.

What This Skill Owns

Hook quality and first-line momentum.
Scene rhythm that can survive chunked captions.
Matching script structure to the chosen archetype or blueprint.
Writing for spoken delivery instead of blog-style reading.

Core Approach

Start from the packaging promise, not the topic label.
Build around spoken payoff beats, not paragraph logic.
Keep scenes short enough that captions and visuals can both breathe.
Write lines that survive voice delivery without sounding read off a page.
If a blueprint exists, treat it as structure and pacing guidance, not handcuffs for exact wording.

Inputs

a topic, angle, or packaging promise
optional archetype such as listicle, versus, or howto
optional research, packaging, or blueprint files

Outputs

one reusable script.json
scenes that downstream audio, caption, and visual steps can actually use

Output Contract

Writes one script.json file to the requested outputPath.
If packagingPath, researchPath, or blueprintPath are supplied, they must already exist.
The main success condition is that the script is speakable, scannable, and editable downstream.

Optional Runtime Surface

Repo-side runner: node ./node_modules/@45ck/content-machine/agent/run-tool.mjs brief-to-script
Supporting code: src/harness/brief-to-script.ts, src/script/*

Validation Checklist

outputPath exists.
Script title and scene count are non-empty.
The hook lands quickly and the body supports short-form pacing.
Lines read like speech, not article prose.
If a blueprint was provided, downstream checks should confirm the generated script still matches that blueprint.

More from this repository

same repository

short-form-production-playbook

45ck/content-machine

Plan, build, and fix short-form videos like an editor, using hook-first structure, caption-aware visual design, Remotion/FFmpeg assembly, and reject-regenerate review loops instead of one-shot automation.

2026-05-0712

generate-short

45ck/content-machine

Build a full short from brief to reviewed MP4 while keeping script, audio, visuals, captions, and validation aligned as one edit.

2026-05-0312

hook-packaging

45ck/content-machine

Generate and evaluate multiple short-form hook, title, cover, opening-frame, and platform-packaging variants before scripting or rendering, then choose a default and preserve the rationale.

2026-05-0312

metrics-feedback-loop

45ck/content-machine

Turn publish receipts and performance metrics into reusable style-profile or niche-profile updates that say what to repeat, kill, or test next.

2026-05-0312

platform-packaging

45ck/content-machine

Generate platform-specific publish metadata, fit checks, and upload checklists for short-form and social video without auto-uploading.

2026-05-0312

retention-pass

45ck/content-machine

Review scripts, timelines, scene plans, or rendered shorts for retention and mobile pacing before final render approval or publish readiness.

2026-05-0312

name	brief-to-script
description	Turn a topic, packaging hint, or blueprint into a script file that the rest of the pack can use.

Brief To Script

Use When

The user wants a fresh script from a topic or short brief.
The agent already has packaging, research, or blueprint files and needs the next script file.
Claude Code or Codex should produce a reusable script.json rather than freeform prose.

What This Skill Owns

Hook quality and first-line momentum.
Scene rhythm that can survive chunked captions.
Matching script structure to the chosen archetype or blueprint.
Writing for spoken delivery instead of blog-style reading.

Core Approach

Start from the packaging promise, not the topic label.
Build around spoken payoff beats, not paragraph logic.
Keep scenes short enough that captions and visuals can both breathe.
Write lines that survive voice delivery without sounding read off a page.
If a blueprint exists, treat it as structure and pacing guidance, not handcuffs for exact wording.

Inputs

a topic, angle, or packaging promise
optional archetype such as listicle, versus, or howto
optional research, packaging, or blueprint files

Outputs

one reusable script.json
scenes that downstream audio, caption, and visual steps can actually use

Output Contract

Writes one script.json file to the requested outputPath.
If packagingPath, researchPath, or blueprintPath are supplied, they must already exist.
The main success condition is that the script is speakable, scannable, and editable downstream.

Optional Runtime Surface

Repo-side runner: node ./node_modules/@45ck/content-machine/agent/run-tool.mjs brief-to-script
Supporting code: src/harness/brief-to-script.ts, src/script/*

Validation Checklist

outputPath exists.
Script title and scene count are non-empty.
The hook lands quickly and the body supports short-form pacing.
Lines read like speech, not article prose.
If a blueprint was provided, downstream checks should confirm the generated script still matches that blueprint.