Compile Timeline

VerifiedCaution

Compile the timeline from blueprint and selection YAML files, generating timeline.json and preview-manifest.json.

Sby Skills Guide Bot
ContentIntermediate
7/28/2026
Claude CodeCodex
#video-editing#timeline#rough-cut#render-pipeline#patch-application

Recommended for

Automated summary

Compiles a video project's rough cut from the creative brief, selects, and edit blueprint, producing timeline.json and the preview manifest, with a patch mode to apply review feedback.

Strengths

  • Checks required artifacts then runs a single command (npx tsx scripts/compile-timeline.ts)
  • Patch mode applies a review_patch.json and regenerates timeline.json together with preview-manifest.json
  • Explicit validation gate: any unresolved_blocker with status blocker fails the compile
  • Encourages correct freshness handling by re-rendering and confirming playback-contract-status is exact after a timeline update

Limitations

  • Assumes an existing project directory layout and TypeScript scripts (compile-timeline.ts, validate-schemas.ts)
  • Does not document the expected schema of the input files (creative_brief, selects_candidates, edit_blueprint)
  • adjacency_analysis.json is only emitted when active editing skills run transition analysis
When to use it

Use it once the input artifacts are ready and you need to generate or regenerate the timeline, optionally applying a review patch.

When not to use it

Avoid it while unresolved blockers remain or when creative_brief, selects_candidates, and edit_blueprint are not yet in place.

Security analysis

Caution
Quality score85/100

The skill is a legitimate local video-timeline compiler workflow. It does not exfiltrate data, download remote payloads, disable safety, or use obfuscated commands, but it does invoke a project script and can overwrite generated artifacts. That places it in the caution category rather than safe or risky.

Findings
  • •Runs a local TypeScript script via `npx tsx scripts/compile-timeline.ts`, which is legitimate but executes project code with filesystem effects.
  • •Patch mode explicitly overwrites `timeline.json` and regenerates `preview-manifest.json`, so accidental data loss is possible if used incorrectly.
  • •No `allowed-tools` are declared, leaving bash/script execution permissions implicit rather than constrained.
How this analysis is made

Examples

Compile the rough cut
Les artifacts sont prêts, compile le rough cut de projects/ep01 en 30 fps et génère timeline.json.
Apply a review patch
Apply projects/ep01/06_review/review_patch.json to the timeline and regenerate the preview manifest at 30 fps.
Regenerate after timeline change
The timeline was updated — re-render the preview and confirm playback-contract-status is exact before I open Studio.

name: compile-timeline description: Use when edit_blueprint.yaml and selects_candidates.yaml are ready and the user asks to compile the rough cut, generate timeline.json, or apply a review patch. metadata: filePattern: - '/05_timeline/timeline.json' - '/05_timeline/preview-manifest.json' - '**/05_timeline/adjacency_analysis.json' bashPattern: - 'compile-timeline'

compile-timeline

いつ使うか

  • 「コンパイルして」「タイムラインを生成して」と言われたとき。
  • creative_brief.yaml, selects_candidates.yaml, edit_blueprint.yaml が揃っているとき。

前提条件

  • scripts/compile-timeline.ts は compile 前後で scripts/validate-schemas.ts 相当の gate を見る。
  • 01_intent/unresolved_blockers.yaml に status: blocker があると compile gate が落ちる。
  • fps を 24 以外にしたい場合は --fps <num> を明示する。

やること(ステップ)

  1. 必要 artifact が存在することを確認する。
  2. compile を実行する。
npx tsx scripts/compile-timeline.ts projects/<project> --fps 30
  1. review patch を適用したい場合は patch mode を使う。
npx tsx scripts/compile-timeline.ts projects/<project> --patch projects/<project>/06_review/review_patch.json --fps 30
  1. 出力された timeline.json、preview-manifest.json、必要なら adjacency_analysis.json を確認する。
  2. 既存preview/finalがある状態でtimelineを更新した場合、それらをfreshとみなさない。Studio確認前にrenderを再実行し、playback-contract-status が exact であることを確認する。

出力 artifact

  • 05_timeline/timeline.json
  • 05_timeline/preview-manifest.json
  • 05_timeline/adjacency_analysis.json ただし active editing skills による transition 解析が走った場合

注意事項

  • scripts/compile-timeline.ts の createdAt は 01_intent/creative_brief.yaml.created_at から決まる。
  • patch mode は timeline.json を上書きし、同時に preview-manifest.json も再生成する。
  • manifest hashだけを手編集して古いpreviewをfresh扱いにしない。
  • adjacency_analysis.json は debug / explanation 用 artifact。常に生成されるわけではない。

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/compile-timeline-ms47vr51/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/compile-timeline-ms47vr51' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/compile-timeline-ms47vr51/download' --output '.skill-downloads/compile-timeline-ms47vr51/SKILL.md.part' && mv '.skill-downloads/compile-timeline-ms47vr51/SKILL.md.part' '.skill-downloads/compile-timeline-ms47vr51/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/compile-timeline-ms47vr51/SKILL.md' && test -s '.skill-downloads/compile-timeline-ms47vr51/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/compile-timeline' && cp -R '.skill-downloads/compile-timeline-ms47vr51' '.claude/skills/compile-timeline'

Codex
test -f '.skill-downloads/compile-timeline-ms47vr51/SKILL.md' && test -s '.skill-downloads/compile-timeline-ms47vr51/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/compile-timeline' && cp -R '.skill-downloads/compile-timeline-ms47vr51' '.agents/skills/compile-timeline'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/compile-timeline-ms47vr51'

openskills read 'compile-timeline-ms47vr51'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/compile-timeline-ms47vr51/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills