refactor(skills): compress 8 SKILL.md descriptions per writing-skills spec

Two issues fixed across personal skills:

1. Five skills had frontmatter > 1024 chars (spec limit per agentskills.io):
   - client-handover: 1920 → 924
   - doc: 1390 → 734
   - seo: 1378 → 885
   - geo: 1189 → 734
   - validate: 1050 → 742
   All now compliant.

2. Three orchestrators had workflow-summary descriptions that create
   "shortcut" risk per writing-skills CSO (Claude may follow the
   description instead of reading the full skill body, skipping steps):
   - ship-feature: "design → plan → implement (TDD) → review → finish"
     → "Use when shipping a feature end-to-end — needs… (9-step pipeline)"
   - init-project: "interview → design → scaffold → implement (TDD)"
     → "Use when initializing a brand-new project from scratch — needs…"
   - onboard: "detect archetype, install claude-config, run full audit…"
     → "Use when bringing an existing repo into the framework — needs…"

Descriptions now follow "Use when [triggers]…" pattern. Workflow detail
preserved in skill body where it belongs. Triggers consolidated and
trimmed of duplicates.

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

skills/validate/SKILL.md

@@ -1,20 +1,14 @@
 ---
 name: validate
 description: |
-  Web standards audit — W3C HTML validity (validator.nu), W3C CSS
-  validity (jigsaw.w3.org/css-validator), WCAG 2.1 accessibility
-  (axe-core, pa11y, WAVE API). Dedicated to syntactic and
-  accessibility conformance. Produces .claude/audits/VALIDATE.md.
-  Dispatches the validator-analyzer agent with a STRICT scope
-  filter — no meta/OG/JSON-LD/CWV/security-header noise.
-  Trigger: "validate", "validation", "w3c", "html validity",
-  "css validity", "wcag", "accessibility", "a11y audit", "axe",
-  "pa11y", "wave", "validator.w3.org", "nu validator",
-  "validation html", "accessibilité", "audit a11y", "audit wcag",
-  "normes w3c", "conformité web", "validité html css".
-  For security hardening (CSP, HSTS, 404) → use /harden.
-  For SEO/indexability (meta, sitemap, JSON-LD) → use /seo.
-  For AI engines (llms.txt, QAPage, entity SEO) → use /geo.
+  Use when a web project needs W3C HTML/CSS validity check or WCAG 2.1
+  accessibility audit. Dispatches the validator-analyzer agent with a
+  STRICT scope filter (no meta/OG/JSON-LD/CWV/security-header noise).
+  Triggers: "validate", "validation", "w3c", "html validity",
+  "css validity", "wcag", "accessibility", "a11y audit", "axe", "pa11y",
+  "wave", "validator.w3.org", "nu validator", "accessibilité",
+  "audit a11y", "audit wcag", "normes w3c", "conformité web".
+  For CSP/HSTS/404 → /harden. For meta/sitemap → /seo. For AI engines → /geo.
 argument-hint: [URL] [--fix] [--local|--full] [--no-external]
 allowed-tools:
   - Read