Update to Wandeo

{
  "description": "Create science, mechanism and how-it-works videos with the original Anatomy workflow, detailed reusable objects, consistent motion and readouts, focused explanatory shots and actual frame review. Prefer this for educational explainers; respect an explicitly requested visual method.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 290
    },
    {
      "relative_path": "references/authored-figure.md",
      "size_in_bytes": 10602
    }
  ],
  "name": "anatomy-explainer",
  "skill_md_contents": "---\nname: anatomy-explainer\ndescription: Create science, mechanism and how-it-works videos with the original Anatomy workflow, detailed reusable objects, consistent motion and readouts, focused explanatory shots and actual frame review. Prefer this for educational explainers; respect an explicitly requested visual method.\n---\n\nCLI file references are relative to the explicit `--project` directory. Resolve returned video, frame, screenshot, subtitle and workspace paths against that directory before reading files or passing them as `--input`; do not resolve them against the plugin directory. `[external file]` means the original input is outside the project; use the input path already supplied for that task. Normal results omit raw media tags, account/cache paths, process details and environment variables. Read only the source content and diagnostics needed for the user’s task.\n\nUse this workflow first for science education, internal structures, mechanisms and physical/process explanations. Anatomy can create precise isometric SVG/HTML objects directly from code; a downloaded GLB is optional. Preserve the user's explicit visual choices and use simple 2D charts or real footage when they better explain a particular claim.\n\nResolve the plugin root as `../..` from this skill directory. Use its `scripts/wandeo.sh` or `scripts/wandeo.ps1`. Keep authored source, research, figure files and production media in the user's project directory. The plugin's `third_party/anatomy/` is a pinned reference, not an output directory.\n\nBefore geometry, read the bundled [original Anatomy Skill](../../third_party/anatomy/SKILL.md), [craft guidance](../../third_party/anatomy/references/craft.md), and the closest relevant upstream example's build source. Read [kit](../../third_party/anatomy/references/kit.md), [motion](../../third_party/anatomy/references/motion.md) and [verification](../../third_party/anatomy/references/verify.md) as their work begins; read [WebGL](../../third_party/anatomy/references/webgl.md) or [3D](../../third_party/anatomy/references/3d.md) when using those optional modes. Adapt the original workflow for video with the steps below and [the authored figure contract](references/authored-figure.md). The upstream React, print and gallery-publishing routes apply only to requests for those deliverables.\n\n1. **Research the mechanism and observable explanation.** Record sources, units, relationships, assumptions and deliberate simplifications. Write the question the viewer should be able to answer after the film. Establish a small deterministic `stateAt(time)` model for quantities that affect movement or readouts. Separate an illustrative timing choice from a validated physical result.\n2. **Author one complete object.** Plan the functional assemblies, supports, interfaces and meaningful construction details before drawing. Use the original kit's solids, lathe/tube helpers, materials and depth ordering. Build the subject required by the brief, rather than substituting an unrelated bundled example. Keep sufficient detail to recognize the object and understand its mechanism at both full view and close-up. Upstream part counts describe scale; do not add decorative parts to meet a quota. If no suitable asset exists, author the explanatory object using the kit and document unresolved assumptions; do not require the user to find a GLB first.\n3. **Make the model and drawing agree.** Build static geometry once and give useful assemblies stable IDs. Drive geometry, visible values and event timing from the same state; reset all mutable visual state on every seek. Model connections explicitly enough to explain the cause and result. Follow the upstream audits and inspect failures; use complete figures, not a few isolated generic primitives. Package the finished object as a self-contained `figure.anatomy.json` and import it with `anatomy import`.\n4. **Compose shots around that object.** Store it once in `project.anatomyFigures` and reuse its `figureId`. Establish the whole, then frame the relevant assembly, fade surrounding parts while retaining context, and show the causal result. Use `anatomy.view` for framing, focus and model-time continuity. Choose the sequence and duration from the narration and action. Keep captions and long text in the film's 2D layers. Do not add a horizontal timeline progress bar.\n5. **Inspect the object and the film.** Run relevant upstream geometry/line checks; inspect full view, 4× crops of important contacts and moving parts, and 390 px-wide frames. Check before/action/result states and reverse seeks. Then use `project validate`, a short `render preview`, and `review` from [auto-edit](../auto-edit/SKILL.md). Verify figure identity/source hashes, actual framing, focus, Chinese glyphs, reading time and agreement between motion and readouts. Record observed defects and correct them before final export. An installed backend, part count or passing unit test is not visual approval.\n\nContinue with [auto-edit](../auto-edit/SKILL.md) for narration timing, source audio, captions, mixed footage, MP4 export and delivery. An explanation need not be all 3D. Preserve the editable object source and its evidence alongside the project so later changes can improve the same figure.\n"
}