novahiz 0.1.0

package/bundled-skills/vault-skill-factory/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: vault-skill-factory
+description: >
+  Generate a portable, self-contained Agent Skill from mature, curated Obsidian wiki pages —
+  turning a cluster of verified knowledge into a reusable "digital expert" (SKILL.md + references/).
+  Use this skill when the user says "/vault-skill-factory", "make a skill from my wiki", "turn these
+  pages into a skill", "generate an agent skill from my vault", "package my notes on X as a skill",
+  "build a domain-expert skill from my wiki", or wants to distill recurring, mature wiki knowledge
+  into a shareable skill. Inspired by OpenKB's "drop in a book → out comes a digital expert" pattern.
+  The factory ONLY reads the vault and WRITES TO A REVIEW DIRECTORY — it never installs skills,
+  never writes into .skills/, and never touches global skill directories.
+---
+
+# Vault Skill Factory
+
+You turn a cluster of **mature, curated** wiki pages into a **portable Agent Skill**: a
+`SKILL.md` plus a `references/` folder, written to a review directory for the human to inspect
+and (only if they choose) install. This is the inverse of `wiki-capture`: capture turns a
+conversation into a page; the factory turns a body of pages into a reusable skill.
+
+## Hard guardrails (read first)
+
+- **Never write into `.skills/`** and **never run `setup.sh`** or create symlinks into any global
+  skill directory (`~/.claude/skills`, `~/.codex/skills`, …). Generated skills go to the review
+  dir only. Installation is a separate, explicit human decision.
+- **Never auto-install.** End by telling the user where the skill is and how to install it
+  *project-locally* if they want — do not do it for them.
+- Source pages are trusted vault content, but do not invent capabilities: the generated skill must
+  reflect what the pages actually say.
+
+## Before You Start
+
+1. **Resolve config** (Config Resolution Protocol in `llm-wiki/SKILL.md`): get `OBSIDIAN_VAULT_PATH`,
+   `OBSIDIAN_WIKI_REPO`, `OBSIDIAN_LINK_FORMAT`, the QMD vars, and:
+   - `SKILL_FACTORY_OUTPUT_DIR` — where generated skills land. Default:
+     `$OBSIDIAN_VAULT_PATH/_generated-skills` (a vault-level, underscore-prefixed *excluded* dir —
+     like `_raw`/`_staging`/`_sources`, NOT the `skills/` knowledge category). This co-locates
+     generated skills with the vault they were distilled from. Create it if missing.
+     Note: `_generated-skills/` holds runtime Agent-Skill bundles (`name` + `description` frontmatter),
+     **not** wiki pages — never write them into `skills/` (that category is for knowledge pages and
+     is graph-/lint-/index-tracked).
+   - `SKILL_FACTORY_MATURITY` — comma list of `lifecycle:` values that count as "mature".
+     Default: `reviewed,verified`. Pages with `tier: core` also qualify.
+2. Read `index.md` to understand what the vault holds.
+
+## Step 1: Choose the cluster
+
+Decide which pages become the skill. The user may name a topic, tag, or project; otherwise propose
+candidates.
+
+1. **Seed** from the user's intent (a topic, tag, project, or a named page).
+2. **Expand** the cluster:
+   - If QMD is configured (`QMD_WIKI_COLLECTION`), run `qmd query "<topic>" -c "$QMD_WIKI_COLLECTION" --files`
+     (or `vsearch`) to gather semantically related pages — this is the intended way to find the
+     full cluster, not just exact-tag matches.
+   - Otherwise `Grep`/`Glob` by tag and wikilink-neighbourhood (pages linked from the seed pages).
+3. **Filter by maturity:** keep pages whose `lifecycle:` is in `SKILL_FACTORY_MATURITY` **or**
+   whose `tier:` is `core`. Drop `draft` pages unless the user explicitly includes them.
+4. **Confirm the cluster with the user** (list page names + count) before generating. If fewer than
+   ~3 mature pages match, say so — a skill from one thin page isn't worth it; offer to proceed anyway
+   or widen the net.
+
+## Step 2: Design the skill
+
+From the cluster, decide:
+
+- **`name`** — kebab-case, derived from the cluster's subject (e.g. `french-theory-expert`,
+  `peptide-protocols`). Must not collide with an existing skill in `.skills/`.
+- **`description`** — the trigger. Write it "pushy" (per `skill-creator`): state **when** to use it
+  (all the phrasings a user might say) **and** what it does. This field is what makes the skill fire.
+- **Reasoning approach** — how an agent should *use* this knowledge: the questions it answers, the
+  method it applies, the caveats it respects. Distil this from the pages' synthesis, not a copy-paste.
+- **Depth material** — which page bodies become `references/` files.
+
+## Step 3: Write the skill to the review dir
+
+Create `$SKILL_FACTORY_OUTPUT_DIR/<name>/` with:
+
+```
+<name>/
+├── SKILL.md            # frontmatter (name + pushy description) + reasoning approach + key knowledge
+├── references/         # depth material distilled from the cluster
+│   ├── <topic>.md      # one per sub-theme; declarative knowledge, not chat
+│   └── sources.md      # provenance: which vault pages this was built from (+ their sources)
+└── SKILL_FACTORY.md    # provenance manifest (see below) — NOT part of the installed skill
+```
+
+**SKILL.md body** should be lean (the trigger logic + a compact reasoning guide), pushing depth into
+`references/`. Follow the structure of existing skills in this repo. Preserve `^[inferred]` /
+`^[ambiguous]` markers when carrying over uncertain claims — a generated skill must not launder
+synthesis into fact.
+
+**`references/sources.md`** lists every vault page used (by `[[wikilink]]`) and their upstream
+`sources:` — so the skill stays auditable back to the vault and original sources.
+
+**`SKILL_FACTORY.md`** (factory metadata, kept out of the installable skill) records: generation
+date, the cluster pages + their lifecycle/tier, the maturity filter used, and the vault commit/hash
+if available. This lets a regenerate-on-update workflow diff later.
+
+Optional, if the user asks: append/update a `marketplace.json` entry in the output dir (the OpenKB
+one-line-install convention) — still **not** an install, just a manifest.
+
+## Step 4: Optionally lean on skill-creator
+
+`skill-creator` ships reusable scripts. Their path differs between a pip/uv install and a source
+checkout, so check both layouts under `$OBSIDIAN_WIKI_REPO` and use the first that exists:
+
+- `$OBSIDIAN_WIKI_REPO/skills/skill-creator/scripts/` — packaged install (`OBSIDIAN_WIKI_REPO` points
+  at the bundled `_data/` dir, which ships the skills under `skills/`).
+- `$OBSIDIAN_WIKI_REPO/.skills/skill-creator/scripts/` — source checkout.
+
+Whichever resolves, it holds:
+
+- `improve_description.py` — tighten the generated `description` for better triggering.
+- `package_skill.py` — bundle the skill dir into a distributable archive.
+- `quick_validate.py` — sanity-check the skill's structure.
+
+Use them when the user wants a polished/validated artifact; don't reinvent them.
+
+## Step 5: Report — and stop
+
+Tell the user:
+- the path: `$SKILL_FACTORY_OUTPUT_DIR/<name>/`
+- the cluster it was built from (page count + names)
+- the trigger `description`
+- **How to install if they want it (their decision, project-local only):**
+  ```
+  ln -s ../../.skills/<name> <repo>/.claude/skills/<name>   # after copying <name>/ into .skills/, sans SKILL_FACTORY.md
+  ```
+  Note explicitly: review first; do not run `setup.sh` (it fans skills into global dirs); never global-install without explicit agreement.
+
+Do **not** install it yourself. Do not write to `.skills/`. Done.
+
+## Quality checklist
+
+- [ ] Output went to `$SKILL_FACTORY_OUTPUT_DIR`, never `.skills/` or a global dir
+- [ ] Cluster confirmed with the user; only mature pages (per `SKILL_FACTORY_MATURITY` / `tier: core`)
+- [ ] `description` is pushy and accurate (when + what)
+- [ ] SKILL.md body is lean; depth lives in `references/`
+- [ ] `^[inferred]`/`^[ambiguous]` markers preserved; no synthesis laundered into fact
+- [ ] `references/sources.md` traces back to vault pages + their sources
+- [ ] `SKILL_FACTORY.md` provenance manifest present (excluded from the installable skill)
+- [ ] Report names the path and the manual, project-local-only install step; nothing auto-installed

package/bundled-skills/video/SKILL.md

@@ -0,0 +1,346 @@
+---
+name: video
+description: "When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative."
+metadata:
+  version: 2.1.0
+---
+
+# Video
+
+You are an expert video producer who helps create marketing videos using AI generation models, AI avatars, and programmatic video frameworks. Your goal is to help users produce professional video content efficiently — from product demos and explainers to social clips and ads.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Video Goal
+- What type of video? (Product demo, explainer, testimonial, social clip, ad, tutorial)
+- What's the target platform? (YouTube, TikTok/Reels/Shorts, website, ads, sales deck)
+- What's the desired length?
+
+### 2. Production Approach
+- Do you need a human presenter? (AI avatar vs. voiceover vs. screen recording)
+- Do you have existing footage or assets? (Screenshots, logos, product UI)
+- Do you need generated footage? (AI-generated scenes, B-roll)
+- Is this a one-off or a template for repeated use?
+
+### 3. Technical Context
+- What's your tech stack? (Node.js, Python, etc.)
+- Do you have API keys for any video tools?
+- Budget constraints? (Some tools charge per minute of video)
+
+---
+
+## Choosing Your Approach
+
+Pick the right tool for the job:
+
+| Approach | Best For | Tools | When to Use |
+|----------|----------|-------|-------------|
+| **Programmatic** | Templated, data-driven, batch video | Remotion, Hyperframes | Product updates, personalized videos, recurring content |
+| **AI Generation** | Original footage from text/image prompts | Veo 3, Sora 2, Runway, Kling, Seedance | B-roll, hero shots, creative visuals you can't film |
+| **AI Avatars** | Talking-head presenter without filming | HeyGen, Synthesia | Explainers, tutorials, multilingual content |
+| **Editing/Repurposing** | Cutting long-form into short clips | Descript, Opus Clip, CapCut | Podcast/webinar → social clips |
+
+---
+
+## Programmatic Video
+
+Build videos with code. Best for repeatable, templated, or data-driven video at scale.
+
+### Hyperframes (HTML/CSS — recommended for agents)
+
+Open-source, Apache 2.0, from HeyGen. Uses plain HTML/CSS/JS — no framework DSL to learn. LLM-native: AI models generate better HTML than React components.
+
+```bash
+npm install hyperframes
+```
+
+**Key concept:** Each frame is an HTML document. Compose frames into a timeline, render to MP4.
+
+```typescript
+import { render } from "hyperframes";
+
+await render({
+  frames: [
+    { html: "<h1>Welcome to Acme</h1>", duration: 3 },
+    { html: "<h2>Here's what we built</h2>", duration: 3 },
+    { html: "<p>Try it free →</p>", duration: 2 },
+  ],
+  output: "intro.mp4",
+  width: 1080,
+  height: 1920, // 9:16 for vertical
+});
+```
+
+**Best for:** Product announcements, changelogs, data-driven reports, personalized outreach videos.
+
+**Why agents prefer it:** Plain HTML/CSS means any coding agent can generate frames without learning a framework. Deterministic rendering — same input always produces identical output.
+
+### Remotion (React)
+
+Mature open-source framework. More powerful than Hyperframes but requires React knowledge.
+
+```bash
+npx create-video@latest
+```
+
+**Key concept:** React components are frames. Props drive content. Render locally or via Remotion Lambda (AWS) for scale.
+
+```tsx
+export const ProductDemo: React.FC<{ title: string; features: string[] }> = ({
+  title, features
+}) => {
+  const frame = useCurrentFrame();
+  return (
+    <AbsoluteFill style={{ background: "#000", color: "#fff" }}>
+      <h1>{title}</h1>
+      {features.map((f, i) => (
+        <Sequence from={i * 30} key={i}>
+          <p>{f}</p>
+        </Sequence>
+      ))}
+    </AbsoluteFill>
+  );
+};
+```
+
+**Best for:** Complex animations, interactive previews, large-scale batch rendering (Lambda).
+
+### When to Pick Which
+
+| Factor | Hyperframes | Remotion |
+|--------|-------------|----------|
+| Agent compatibility | Better (plain HTML) | Good (React) |
+| Animation complexity | Basic (CSS transitions) | Advanced (Spring, interpolate) |
+| Batch rendering | Local | Lambda (AWS) for scale |
+| Learning curve | Minimal | Moderate (React + Remotion API) |
+| License | Apache 2.0 | Company license for commercial use |
+
+---
+
+## AI Video Generation
+
+Generate original footage from text or image prompts. Use for B-roll, hero visuals, and scenes you can't practically film.
+
+### Model Comparison
+
+| Model | Resolution | Max Duration | Best For | Cost |
+|-------|-----------|-------------|----------|------|
+| **Veo 3** (Google) | Up to 1080p (4K varies) | Variable | Top overall quality, synced audio | API-based |
+| **Sora 2** (OpenAI) | Up to 1080p | Up to ~20 sec | Cinematic + synced audio, ChatGPT/API integration | API + ChatGPT |
+| **Runway Gen-4** | Up to 4K | ~10 sec/gen | Motion control, temporal consistency, edit-style workflows | $12-76/mo |
+| **Kling 2.5/3.0** (Kuaishou) | Up to 1080p | Up to 2 min | Long-take generation, lower per-second cost | ~$0.03/sec |
+| **Seedance** (ByteDance) | Up to 1080p | Short clips | Fast generation, strong motion fidelity at low cost, batch-friendly | Per-credit |
+| **Hailuo / MiniMax** | Up to 1080p | Short clips | Character consistency across shots | Per-credit |
+| **Pika 2.x** | 1080p | Short clips | Quick effects, image-to-video, lower bar to entry | Per-credit |
+| **Hunyuan Video / Wan 2** | 720p–1080p | Variable | Open-source self-hosted; full control, no API fees | Free (GPU) |
+
+**Quick picks**:
+- **Highest quality + audio**: Veo 3 or Sora 2
+- **Batch / volume / cost**: Kling, Seedance
+- **Character consistency across multiple shots**: Hailuo
+- **Self-hosted, brand-controlled**: Hunyuan Video or Wan 2 (open weights)
+- **Storyboard → video workflow**: Runway, LTX Studio
+- **Image-to-video from a still you already have**: Kling, Pika, Runway
+
+### Prompting for Video Models
+
+Good video prompts specify: **subject + action + camera + style + mood**
+
+```
+A close-up shot of hands typing on a laptop keyboard,
+shallow depth of field, warm office lighting,
+camera slowly pulls back to reveal a modern workspace,
+cinematic color grading, 4K
+```
+
+**Common mistakes:**
+- Too vague ("a person working") — add specifics
+- Ignoring camera movement — specify dolly, pan, static
+- Forgetting style — "cinematic," "documentary," "commercial"
+- Requesting text in video — AI models struggle with readable text
+
+**For detailed prompting guides**: See [references/ai-video-prompting.md](references/ai-video-prompting.md)
+
+### When to Use AI Generation vs. Stock
+
+| Use Case | AI Generation | Stock Footage |
+|----------|:---:|:---:|
+| Exact scene you imagined | Yes | Rarely matches |
+| Consistent style across clips | Yes | Hard to match |
+| Recognizable real locations | No (hallucinations) | Yes |
+| Specific products/brands | No (use programmatic) | No |
+| Quick B-roll | Either works | Faster |
+
+---
+
+## AI Avatars
+
+Create talking-head videos without filming. An AI avatar delivers your script with realistic lip-sync, expressions, and gestures.
+
+### HeyGen (recommended — has MCP server)
+
+Best lip-sync and micro-expressions. 230+ avatars, 140+ languages.
+
+**Agent integration:** HeyGen has an official MCP server — AI agents can generate avatar videos directly.
+
+| Plan | Videos | Duration |
+|------|--------|----------|
+| Free | 3/mo | 3 min max |
+| Creator | Unlimited | 5 min |
+| Business | Unlimited | 20 min |
+
+Check [heygen.com/pricing](https://www.heygen.com/pricing) for current prices.
+
+**Best for:** Product explainers, feature announcements, personalized sales outreach, multilingual content.
+
+**Custom avatars:** Upload a 2-5 min video of yourself to create a digital twin. Looks and sounds like you, generates videos from text scripts.
+
+### Synthesia
+
+Full-body avatars with expressive body language. Built-in script generation from URLs/docs.
+
+**Best for:** Corporate training, compliance videos, enterprise presentations where professional tone > realism.
+
+### When to Use Avatars vs. Other Approaches
+
+| Scenario | Use Avatar | Use Instead |
+|----------|:---:|-------------|
+| Recurring content (weekly updates) | Yes | — |
+| Multilingual versions | Yes | — |
+| Personalized outreach at scale | Yes | — |
+| Authentic founder content | No | Film yourself |
+| Product UI walkthrough | No | Screen recording |
+| Creative/artistic video | No | AI generation |
+
+---
+
+## Editing & Repurposing Tools
+
+Turn existing content into multiple video formats.
+
+| Tool | What It Does | Best For |
+|------|-------------|----------|
+| **Descript** | Transcript-based editing — edit video by editing text | Cleaning up interviews, podcasts, webinars |
+| **Opus Clip** | Auto-clips long videos, scores virality potential | Long-form → short-form at scale |
+| **CapCut** | Visual effects, captions, platform-native styling | TikTok/Reels polish |
+| **Captions.ai** | Auto-captions, eye contact correction, AI dubbing | Solo talking-head content |
+
+### Repurposing Workflow
+
+```
+Long-form content (podcast, webinar, demo)
+    ↓
+Descript: Clean up, remove filler, polish
+    ↓
+Opus Clip: Auto-extract 5-10 best moments
+    ↓
+CapCut: Add captions, effects, platform styling
+    ↓
+Distribute: TikTok, Reels, Shorts, LinkedIn
+```
+
+### Reverse-Engineer a Viral Edit
+
+To replicate the *style* of a video edit you admire — the cut rhythm, caption treatment, punch-ins, on-screen text, sound design — decompose it into a reusable **edit spec** (a beat sheet) and apply it to your own footage. Pull the reference with **watch-video** (visual/multimodal mode extracts frames at the cut points) or **social-fetch**, extract the edit anatomy beat by beat, and output a per-beat table plus the 3–5 signature moves that make the edit recognizable. Review the beat sheet once before executing it (in Remotion/Hyperframes, CapCut, or an AI restyle tool). Copies the editing grammar, never the reference's footage/script/music. Full method: [references/edit-anatomy.md](references/edit-anatomy.md).
+
+---
+
+## Video Production Workflows
+
+### Product Demo Video
+
+1. **Script** the key features and value props (use copywriting skill)
+2. **Screen record** the product flow
+3. **Programmatic overlay** — use Hyperframes/Remotion for titles, callouts, transitions
+4. **AI B-roll** — generate establishing shots or lifestyle scenes with Veo/Runway
+5. **Voiceover** — record yourself or use AI avatar for narration
+6. **Export** at platform-appropriate specs
+
+### Explainer Video
+
+1. **Script** the problem → solution → CTA arc
+2. **Choose presenter** — AI avatar (HeyGen) or voiceover + visuals
+3. **Build visuals** — programmatic slides, screen recordings, AI-generated scenes
+4. **Add captions** — always, for accessibility and engagement
+5. **Export** — landscape for YouTube/website, vertical for social
+
+### Batch Social Clips
+
+1. **Create master template** in Hyperframes/Remotion
+2. **Feed data** — product features, testimonials, stats
+3. **Render batch** — one template, many variations
+4. **Add platform-specific captions** via CapCut or Captions.ai
+5. **Schedule** across platforms
+
+---
+
+## Agent-Native Video Pipeline
+
+The most powerful setup combines tools that agents can control directly:
+
+```
+Agent writes script (from product context)
+    ↓
+Hyperframes: Generate templated video (HTML → MP4)
+    and/or
+HeyGen MCP: Generate avatar video from script
+    and/or
+Veo/Runway API: Generate B-roll footage
+    ↓
+Agent assembles final cut
+    ↓
+Output: Ready-to-publish video
+```
+
+**What makes this agent-native:**
+- Hyperframes uses HTML — any coding agent can generate it
+- HeyGen MCP server — agents call it directly
+- Video model APIs — standard HTTP requests
+- No manual editing step required
+
+---
+
+## Common Mistakes
+
+1. **Starting with tools, not strategy** — decide what video you need before picking tools
+2. **AI-generated text in video** — models can't reliably render readable text; use programmatic overlays instead
+3. **Uncanny valley avatars** — if avatar quality matters, invest in HeyGen Creator+ tier
+4. **No captions** — 85% of social video is watched without sound
+5. **Wrong aspect ratio** — 9:16 for social, 16:9 for YouTube/website, 1:1 for feeds
+6. **Over-producing** — authentic often outperforms polished, especially on TikTok
+
+---
+
+## Task-Specific Questions
+
+1. What type of video do you need? (Demo, explainer, social clip, ad, tutorial)
+2. Do you need a human presenter or can it be voiceover/text?
+3. Is this a one-off or a repeatable template?
+4. What platform is it for? (This determines aspect ratio and length)
+5. Do you have existing assets to work with? (Screenshots, footage, scripts)
+6. What's your budget for video tools?
+
+---
+
+## Tool Integrations
+
+| Tool | Type | MCP | Guide |
+|------|------|:---:|-------|
+| **HeyGen** | AI avatars | Yes | [heygen.md](../../tools/integrations/heygen.md) |
+| **Hyperframes** | Programmatic video | - | [hyperframes.md](../../tools/integrations/hyperframes.md) |
+| **Remotion** | Programmatic video | - | [remotion.dev](https://www.remotion.dev/docs) |
+| **Runway** | AI generation | - | [runwayml.com/docs](https://docs.dev.runwayml.com) |
+
+---
+
+## Related Skills
+
+- **social**: For video content strategy, hooks, and what to post
+- **ad-creative**: For paid video ad creative and iteration
+- **copywriting**: For video scripts and messaging
+- **marketing-psychology**: For hooks and persuasion in video

package/bundled-skills/video/evals/evals.json

@@ -0,0 +1,103 @@
+{
+  "skill_name": "video",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We need a 2-minute product demo video for our SaaS homepage. What's the fastest way to produce it?",
+      "expected_output": "Should check for product-marketing.md first. Should walk through the Product Demo Video workflow: script the key features and value props (cross-reference copywriting skill), screen record the product flow, programmatic overlay with Hyperframes or Remotion for titles/callouts/transitions, optional AI B-roll with Veo/Runway for establishing shots, voiceover via recording or AI avatar (HeyGen) for narration, export at platform-appropriate specs (16:9 for homepage). Should recommend Hyperframes for agent-friendliness (plain HTML, no React DSL). Should remind: don't use AI for product UI screens (models hallucinate UI) — use real screen recording. Should mention captions are essential (85% of social video watched without sound — applies to homepage too).",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Walks through Product Demo workflow steps",
+        "Uses real screen recording, not AI generated UI",
+        "Recommends programmatic overlay tool",
+        "Mentions captions",
+        "Cross-references copywriting skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We want to make weekly product update videos. About 60 seconds each. Don't want to be on camera. Recommend a setup.",
+      "expected_output": "Should recommend an AI avatar workflow given recurring weekly cadence and no-camera preference. Should recommend HeyGen specifically: best lip-sync, has an MCP server (so agents can generate videos directly), 230+ avatars, 140+ languages, Creator plan supports unlimited 5-minute videos. Should explain custom avatars (upload 2-5 min of yourself for a digital twin) as an option for brand consistency. Should outline the recurring pipeline: script written from product context, HeyGen generates avatar video, optional programmatic overlay with Hyperframes for UI screenshots/callouts, export and distribute. Should mention this is exactly the case where AI avatars shine vs other approaches (recurring content, multilingual versions, personalized outreach at scale). Should warn: if authentic founder content matters more than scale, film yourself instead.",
+      "assertions": [
+        "Recommends AI avatar approach",
+        "Names HeyGen specifically",
+        "Mentions HeyGen MCP server for agents",
+        "Mentions custom avatars option",
+        "Identifies as a recurring use case",
+        "Warns about authenticity tradeoff"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "I want to generate a 10-second clip of a person typing on a laptop in a coffee shop for our landing page. Which AI tool?",
+      "expected_output": "Should apply the AI Video Generation model comparison. Should recommend Veo 3 for highest quality with synced audio, Runway Gen-4 for motion control and temporal consistency (~10 sec/gen sweet spot), or Kling 3.0 for lower-cost volume production. Should give a structured video prompt example following Subject + Action + Camera + Style + Mood pattern: 'A close-up shot of hands typing on a laptop keyboard in a cozy coffee shop, shallow depth of field, warm afternoon lighting through a window, camera holds steady, cinematic color grading, 4K.' Should warn about common mistakes: too vague, ignoring camera movement, forgetting style, requesting readable text. Should mention Sora has had limited availability — check current status.",
+      "assertions": [
+        "Compares Veo, Runway, and Kling",
+        "Provides structured video prompt example",
+        "Follows Subject + Action + Camera + Style + Mood pattern",
+        "Warns about common prompt mistakes",
+        "Notes Sora reliability caveats"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We just did a 60-minute webinar. How do we get short clips out of it for social?",
+      "expected_output": "Should apply the Repurposing Workflow: long-form content → Descript (clean up, remove filler, polish) → Opus Clip (auto-extract 5-10 best moments, scores virality potential) → CapCut (add captions, effects, platform styling) → distribute to TikTok, Reels, Shorts, LinkedIn. Should explain when to use each tool: Descript for transcript-based editing, Opus Clip for finding the best moments at scale, CapCut for platform-native polish, Captions.ai for auto-captions and eye-contact correction if needed. Should mention 85% of social video is watched without sound — captions are essential. Should mention aspect ratio matters: 9:16 for TikTok/Reels/Shorts, 1:1 or 9:16 for LinkedIn. Should recommend hooking in the first 3 seconds — cross-reference social skill.",
+      "assertions": [
+        "Applies repurposing workflow",
+        "Names Descript, Opus Clip, CapCut in sequence",
+        "Mentions captions essential",
+        "Specifies aspect ratios per platform",
+        "Mentions hooking in first 3 seconds",
+        "May cross-reference social skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We need to generate 50 personalized intro videos for sales outreach. Each one mentions a different company name and pain point.",
+      "expected_output": "Should recommend an agent-native pipeline combining HeyGen MCP (or API) for the avatar narration + Hyperframes for any visual overlays. Should explain: prepare a master script template with variables, run a loop generating 50 HeyGen videos each with a personalized script, optional programmatic overlays via Hyperframes for company logo or visual context. Should note HeyGen is well-suited to personalized outreach at scale and has an MCP server. Should warn about quality tradeoffs at volume and recommend testing the first 5 manually before generating all 50. Should mention reply tracking to measure ROI vs cold text emails — these are expensive to produce so should outperform email significantly to justify the effort. Should mention captions for the videos.",
+      "assertions": [
+        "Recommends HeyGen + Hyperframes pipeline",
+        "Names HeyGen MCP server",
+        "Suggests template + loop approach",
+        "Recommends testing 5 manually first",
+        "Mentions reply tracking / ROI",
+        "Mentions captions"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Should I use Hyperframes or Remotion for programmatic video?",
+      "expected_output": "Should compare the two based on the When to Pick Which table. Should recommend Hyperframes if: agent-driven (plain HTML/CSS, no React DSL — AI models generate better HTML than React components), minimal learning curve, basic animation needs, local rendering is fine, want Apache 2.0 license. Should recommend Remotion if: already a React shop, need complex animations (Spring, interpolate), need large-scale batch rendering via Lambda for AWS scale, can handle the React + Remotion API learning curve, comfortable with the company license for commercial use. Should note Hyperframes is from HeyGen and LLM-native by design. Should ask about the user's tech stack and animation complexity to recommend a final choice.",
+      "assertions": [
+        "Compares the two with the When to Pick Which table",
+        "Notes Hyperframes uses plain HTML/CSS",
+        "Notes Remotion supports Lambda for scale",
+        "Mentions Apache 2.0 vs company license",
+        "Recommends Hyperframes for agent-driven workflows",
+        "Asks about stack or animation needs"
+      ],
+      "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "There's a TikTok edit style I love — fast cuts, one-word captions that pop, a whoosh on every scene change. I have my own talking-head clip. Break down how that edit works so I can replicate the style. Here's the reference: [link]",
+      "expected_output": "Should apply references/edit-anatomy.md (reverse-engineer the edit into a reusable spec), not just describe it. Should pull the reference with watch-video (visual/multimodal to read frames + caption style + cut timing) or social-fetch — not qualify from the transcript alone. Should extract the edit anatomy beat by beat across the dimensions (shot/framing, cut rhythm/cuts-per-second, on-screen text content+placement+timing, caption style, motion/punch-ins, b-roll/overlays, sound design, the first-2s hook, pacing curve) and output BOTH a per-beat beat-sheet table AND a short style summary of the 3-5 signature moves. Should emphasize patterns over instance-logging. Should present the beat sheet for a review-once approval (does the on-screen text say what you want; do scene changes land where you want) before executing, and note the spec can be executed in Remotion/Hyperframes, CapCut, or an AI restyle tool. Should apply the originality guardrail: copy the editing grammar applied to the user's own footage/message, never the reference's footage, script, voiceover, or music.",
+      "assertions": [
+        "Applies the edit-anatomy reverse-engineering method, not a plain description",
+        "Pulls the reference with watch-video/social-fetch to read the actual frames, not just the transcript",
+        "Extracts the edit anatomy across the dimensions and expresses patterns (not a raw list of cut timestamps)",
+        "Outputs a per-beat beat sheet AND a style summary of the signature moves",
+        "Presents the beat sheet for a review-once approval before executing",
+        "Notes execution paths (Remotion/Hyperframes, CapCut, or AI restyle tool)",
+        "Applies the originality guardrail — copies editing grammar applied to the user's own footage, never the reference's footage/script/music"
+      ],
+      "files": []
+    }
+  ]
+}