video-to-jsonlisted
Install: claude install-skill franciscobmacedo/postreef-skills
# Video / post / article → JSON conforming to a schema
Two halves to this job: (1) getting the content into a form a model can read, (2) getting a model to fill a schema without inventing things. Most bad results come from skipping the design work in (2) or feeding a transcript to a schema that needed the picture.
## 1. Pick the input the schema actually needs
| Schema wants | Input needed | Why |
|---|---|---|
| What was said (recipe steps, claims, quotes, Q&A) | Transcript | Cheapest; captions carry the words |
| What people think (sentiment, questions, corrections) | Comments | Creators rarely say what's wrong; commenters do |
| Tone, music, delivery, or the video has no captions | Audio | Models can listen; captions can't be listened to |
| Anything only on screen: text overlays, on-screen ingredient lists, product shots, visual steps, before/after | Video frames | Cooking Shorts often show quantities as overlays and never say them |
| Article/blog post | Page text + lead image | Not a video; don't run it through a video pipeline |
If in doubt start with transcript + comments and only add audio/video when the result is thin. This ordering is also what keeps cost sane.
## 2. Design a schema the model will follow
Full rules and a worked example in `references/schema-rules.md`. The short version:
- Top-level `"type": "object"` with `properties`; each property has a `type` and a **`description` written as an instruction** ("Exact product name as shown on screen or said