メニュー
Use when defining video pipeline manifests, stage graphs, dry runs, approval gates, artifacts, capability requirements, and machine-readable QA plans for Clash agent workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to read, modify, search, add, or delete nodes on a project's canvas. Triggers on "canvas", "scene", "node", "add a clip", "edit the timeline", "what's in the canvas", "rearrange", "remove the X". Use the `clash canvas` CLI subcommands; always pass `--json` for parseable output.
Use when the user wants to list, switch, create, inspect, or delete Clash projects. Triggers on "project", "switch project", "open project", "new project", "delete project", or any reference to a project by name. Use the `clash projects` CLI subcommands.
Use when the user wants to cut, trim, split, reorder, or add media to a Project Timeline, or change its fps or composition size. Round-trip the Timeline through timelines/<id>.timeline.yaml with public `clash timeline list`, `pull`, and `apply` commands.
Use when the user wants to read, modify, search, add, or delete nodes on a project's canvas. Triggers on "canvas", "scene", "node", "add a clip", "edit the timeline", "what's in the canvas", "rearrange", "remove the X". Use the `clash canvas` CLI subcommands; always pass `--json` for parseable output.
Use when the user wants to list, switch, create, inspect, or delete Clash projects. Triggers on "project", "switch project", "open project", "new project", "delete project", or any reference to a project by name. Use the `clash projects` CLI subcommands.
AI video production with the Clash platform. Use this skill whenever the user mentions Clash, video projects, canvas editing, image/video generation, storyboards, or wants to create visual content. Also use when the user asks about managing Clash projects, tokens, or CLI setup.
| name | pipeline-manifest-architecture |
| description | Use when defining video pipeline manifests, stage graphs, dry runs, approval gates, artifacts, capability requirements, and machine-readable QA plans for Clash agent workflows. |
Model every production workflow as a stage graph with explicit artifacts.
Required manifest fields:
projectKindstageseditableFilesprotectedFilesrequiredSystemCapabilitiesartifacts: action, metadata, asset, projection, review-gate, export paths.gates, dryRun, and qaChecks when the workflow needs them.Rules:
casRequired: true.requiredSystemCapabilities means Clash-native automation bindings needed for
managed execution. It is not a gate for producing portable draft artifacts.Before a review/export gate, validate the manifest against actual local project files:
clash production validate-pipeline-manifest \
--pipeline pipeline.manifest.json \
--out qa/pipeline/pipeline-validation.json \
--json
This writes kind: "clash.production.pipeline-validation". The report blocks
when action, metadata, asset, projection, review-gate, or export artifacts are
missing, or when projection artifacts do not declare casRequired: true.
For local managed execution, keep the gate as a project-readable file and use Clash only for review management:
clash production plan-review-gate \
--pipeline pipeline.manifest.json \
--stage export \
--artifact projections/timelines/main.timeline.yaml \
--artifact qa/delivery/tiktok-15s.validation.json \
--out reviews/gates/export.review-gate.json \
--json
This writes kind: "clash.review.stage-gate" and records its version in
.clash/observed.json. Missing
artifacts keep the gate blocked; present artifacts move it to
pending-review. The observation is path-bound to this exact gate file.
Approve or request changes explicitly:
clash production approve-review-gate \
--gate reviews/gates/export.review-gate.json \
--reviewer qa-agent \
--decision approve \
--note "artifact checks pass" \
--json
Copied, unread, or stale gates are rejected automatically. Re-plan or re-read the gate when the path or contents change; approval has no force bypass.