chore: consolidate the skill packages under .agents/

The repository had two skill directories. `skills/` held the four written
for this project; `.agents/skills/` held the ones the agent context refers
to. Nothing said which an agent should read, and `.agents/ORCHESTRATOR.md`
only ever pointed at the second.

Move the first four into `.agents/skills/` so there is one location, and
add the vendored packages this chapter work used: `animation-vocabulary`
and `improve-animations` (emilkowalski/skills), `teach` (mattpocock/skills),
plus a local `translation` skill and `audit-translations.mjs` for the EN/PT
pairs.

`skills-lock.json` pins the vendored three by source and content hash, so a
later re-vendor is a diff rather than a guess. `.claude/skills/` is
symlinks into `.agents/skills/`, which is what makes them loadable here
without a second copy on disk.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.agents/skills/teach/RESOURCES-FORMAT.md

@@ -0,0 +1,46 @@
+# RESOURCES.md Format
+
+`RESOURCES.md` is the curated set of trusted sources for this topic. Knowledge
+for explainers should be drawn from here, not from parametric guesses. Wisdom
+comes from the communities listed here.
+
+## Structure
+
+```md
+# {Topic} Resources
+
+## Knowledge
+
+- [Book: _The Science and Practice of Strength Training_ by Zatsiorsky & Kraemer](https://example.com)
+  Foundational text on programming and adaptation. Use for: anything to do with
+  periodisation, recovery, intensity zones.
+- [Article: "How Much Should I Train?" by Greg Nuckols (Stronger By Science)](https://example.com)
+  Evidence-based review of volume landmarks. Use for: weekly set targets per
+  muscle group.
+
+## Wisdom (Communities)
+
+- [r/weightroom](https://reddit.com/r/weightroom) High-signal subreddit,
+  moderated against bro-science. Use for: programme critique, plateau
+  troubleshooting.
+- Local: Tuesday strength class at {gym name} Use for: real-time coaching
+  feedback on lifts.
+```
+
+## Rules
+
+- **High-trust only.** Prefer primary sources, recognised experts, peer-reviewed
+  work, and communities with strong moderation. If a resource is marketing
+  dressed as education, leave it out.
+- **Annotate every entry.** A bare link is useless in three months. Add one
+  line: what it covers and when to reach for it.
+- **Group by Knowledge / Wisdom.** Mirrors the philosophy in
+  [SKILL.md](./SKILL.md). It is fine for a resource to appear in only one group.
+- **Surface gaps explicitly.** If no good resource exists for an area the
+  mission needs, write a `## Gaps` section listing what is missing. This drives
+  future search.
+- **Prune ruthlessly.** A resource that turned out to be wrong, shallow, or
+  off-mission should be removed, not buried. Better five sharp sources than
+  thirty mediocre ones.
+- **Record community preferences.** If the user has opted out of joining
+  communities, note it here so future sessions don't keep proposing them.