メニュー
Use when a pipeline step fails, an error occurs, schema validation fails, ffmpeg crashes, or API returns an error. Diagnose the root cause and attempt automatic recovery.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
MUST USE when the user asks to crop, reframe, trim, or improve composition of still photos, especially selected event photos, album photos, portraits, speakers, panels, workshops, or group photos. Use after photo selection or correction when the task is composition improvement rather than selecting images.
MUST USE when the user provides a photo ZIP, photo folder, or still-image event material and asks for photo selection, album selection, highlights, digest photos, curation, or quality filtering. Use this instead of analyze-footage when the source is primarily still photos and the requested work is selecting images rather than editing or video planning.
Use when timeline.json exists and the user asks to review the rough cut, critique the edit, or generate review_report.yaml and review_patch.json.
Use after changing prompts, skills, the compiler, or editorial policies — or when the user asks to measure edit quality, run regression evals, check agreement with approved edits, or says '評価して', '一致率を測って', 'eval を回して'. Compares agent output against human-approved golden projects.
MUST USE when starting a new video project, when the user provides footage and asks to edit/create a video, or when 01_intent/creative_brief.yaml does not yet exist. This skill interviews the user to understand their intent before any editing begins. Never skip this step.
MUST USE when the user is setting up this project for the first time, when dependencies are missing, API keys are not configured, or when 'npm run demo' fails. Triggers on: 'セットアップ', '環境構築', 'setup', 'install', 'API key', 'ffmpeg not found', 'GEMINI_API_KEY', 'cannot find module'.
| name | troubleshoot-error |
| description | Use when a pipeline step fails, an error occurs, schema validation fails, ffmpeg crashes, or API returns an error. Diagnose the root cause and attempt automatic recovery. |
| metadata | {"filePattern":[],"bashPattern":["error","failed","Error","FATAL"]} |
analyze / compile / review / render / export の途中で command が non-zero exit したときffmpeg / ffprobe / API connector が失敗したときscripts/validate-schemas.ts が canonical validatorscripts/compile-timeline.ts は compile 前に Gate 1、compile / patch 後に timeline schema を検証するscripts/analyze.ts は --skip-stt / --skip-vlm を持つ。GEMINI_API_KEY 未設定は warning + VLM skip であり、常に hard failure ではないreferences/error-catalog.md を参照することnpx tsx scripts/validate-schemas.ts projects/<project>
npx tsc --noEmit
ffprobe で source を直接確認する01_intent/unresolved_blockers.yaml と validator output を両方見るartifact, rule, message, details.instancePath から壊れている field を特定する02_media/source_map.json の path 解決を確認する--skip-vlm / --skip-stt に迂回するこの種の failure は無理に隠さず、次に必要な action を具体化して返す。
validate-schemas.ts は violation が 1 件でもあれば exit 1 になる。一方 compile_gate: blocked は Gate 1 blocker 専用の狭い判定status: blocker を勝手に resolved に変えない。質問が解決されたか、許可済み assumption がある場合だけ進めるGEMINI_API_KEY 未設定 warning と、401/403 の invalid key error を混同しない