extract-source-sample

# extract-source-sample This is an **agent-executed** skill. There are no Python scripts. The agent reads the run folder, builds the JSON, and stamps catalog links by hand. The content-goose run folders aren't always cleanly structured (some have empty production/ JSON, some carry everything in working/) — an agent adapts, a script would brittle out. ## When to use - "Extract the source-sample.json for `<run>`." - "Get the upload-sample JSON for this ad so I can remix it." - "Prep `<run>` for remix." Do NOT use to: - Rewrite the script for a new brand (that's a separate agent step that consumes this skill's output). - Render the remix (that's the existing `remix-ad` skill). - Upload an ad to the library (that's `upload-ad-sample`). ## Inputs | Input | Required | Notes | |---|---|---| | `run-dir` | yes | Absolute path to a content-goose ad-run folder (e.g. `clients/ladder/ad-runs/run-02-podcast-skit`). | | `out` | no | Where to write the JSON. Default: `<run-dir>/remix/source-sample.json`. | That's the entire interface. ## What the agent must do ### 1. Read the run Open each file if it exists; tolerate missing files (most production/*.json in older runs are empty stubs — fall back to `working/`): - `working/script.json` — **primary source of truth** for scenes, voices, set. - `production/asset-manifest.json` — `assets[]` with role `active_master` points at the master mp4; per-asset `provider` + `metadata.model` produce the atom-skill rows. - `HOW_TO_MAKE_THIS_...