القائمة
Use when planning provider/model/tool usage, BYO keys, local runtime availability, dry-run costs, max-cost gates, capability checks, and explicit fallback decisions.
التثبيت باستخدام 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 | provider-budget-capability |
| description | Use when planning provider/model/tool usage, BYO keys, local runtime availability, dry-run costs, max-cost gates, capability checks, and explicit fallback decisions. |
Use this skill before generation-heavy workflows.
Report:
Rules:
--max-cost 0 should produce a plan but block paid generation.For managed local execution, write a readable request file:
{
"workflowId": "short-drama-episode-001",
"stage": "generate",
"maxCostUsd": 0,
"operations": [
{
"id": "character-three-view",
"capability": "image.generation",
"provider": "local-comfyui",
"runtime": "comfyui",
"mode": "local",
"availability": "available",
"estimatedCostUsd": 0,
"estimatedSeconds": 90,
"requiresByoKey": false
}
],
"fallbackOptions": []
}
Then ask Clash to write the gate artifact:
clash production plan-dry-run-cost-gate \
--request plans/generate.dry-run-request.json \
--out reviews/gates/generate.dry-run-cost-gate.json \
--json
The result uses kind: "clash.workflow.dry-run-cost-gate" and records
availability, estimated cost/time, max-cost blocking, rejected fallback options,
fallbackUsed: false, and executionAllowed. This command must not execute
generation, download, render, or provider calls.