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/geo/SKILL.md

@@ -1,20 +1,15 @@
 ---
 name: geo
 description: |
-  Standalone GEO (Generative Engine Optimization) audit for AI search
-  engines: ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews,
-  Microsoft Copilot, Brave AI, DuckAssist, You.com, Apple Intelligence.
-  Audits AI crawler directives, llms.txt / llms-full.txt, Schema.org
-  types optimised for AI extraction (QAPage, Speakable, Person+Article,
-  HowTo, Organization graph), entity SEO (Wikidata, sameAs, @id,
-  Knowledge Panel), content shape for LLM extraction (Definition Lead,
-  TL;DR, Q→A structure, citable stats, freshness), and live AI
-  visibility monitoring.
-  For full SEO + GEO combined audit → use /seo (runs seo + geo in parallel).
-  For classical SEO only → use /seo and skip the GEO section.
-  Trigger: "geo", "AI search", "ChatGPT visibility", "Perplexity optimisation",
-  "llms.txt", "AI crawlers", "Google AI Overview", "entity SEO", "Wikidata",
-  "generative engine optimization", "référencement IA", "optimisation IA".
+  Use when a web project needs AI-search visibility audit — ChatGPT,
+  Perplexity, Claude, Gemini, AI Overviews, Copilot, Brave AI, DuckAssist,
+  You.com, Apple Intelligence. Standalone GEO; dispatches the geo-analyzer
+  agent.
+  Triggers: "geo", "AI search", "ChatGPT visibility", "Perplexity
+  optimisation", "llms.txt", "AI crawlers", "Google AI Overview",
+  "entity SEO", "Wikidata", "generative engine optimization",
+  "référencement IA", "optimisation IA".
+  For combined SEO+GEO → /seo.
 argument-hint: optional keywords/scope, e.g. "SaaS B2B content GEO" or "audit llms.txt et entity SEO"
 allowed-tools:
   - Read