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>
This commit is contained in:
bastien 2026-05-11 16:09:21 +02:00
parent 7db8f01074
commit 0fb634deca
8 changed files with 46 additions and 88 deletions

View File

@ -1,28 +1,14 @@
---
name: client-handover
description: |
Final ship-and-handover orchestrator. End-to-end pipeline that hardens the
project, commits, pauses for deploy, validates the live site, and only then
generates the non-technical client deliverable as Markdown + branded HTML +
PDF (ZenQuality identity: green palette, Inter + Playfair Display fonts,
cover page with logo and tagline). The deliverable uses a 4-chapter
structure: §1 what was needed and why, §2 what was done (≤300 words, zero
jargon, no internal tool/skill names), §3 what the client must do (action
checklist), §4 technical details for the curious (scores, key choices,
glossary). Pipeline: (1) /seo (SEO+GEO) and /harden run in parallel with
auto-fix loops until each score ≥17/20, (2) /commit-change + push if
changes made, (3) pause to tell user what to deploy and wait for
confirmation, (4) /validate against the live site, (5) per-axis gate
≥17/20 — stop and analyze if any below, (6) write client doc + render
branded HTML/PDF. Reads git history + .claude/memory/ registries. For
local-business projects, appends manual SEO/GEO platform checklist (NAP
consistency across Google Business, Pages Jaunes, Yelp, Facebook,
Instagram, TikTok, Apple Maps, Bing Places, TripAdvisor, etc.). Asks
whether to include build/deploy chapter.
Trigger: "client handover", "compte rendu client", "livraison client",
"synthese projet", "rapport client", "deliverable", "summary for client",
"recap projet", "handover doc", "livrable", "ship and handover",
"finaliser et livrer".
Use when finalizing a project for non-technical client delivery — needs
final audits, deploy validation against live site, and a branded
deliverable (Markdown + HTML + PDF). Multi-agent orchestrator: dispatches
client-handover-writer which spawns parallel /seo + /harden subagents,
then /validate, then writes the deliverable.
Triggers: "client handover", "compte rendu client", "livraison client",
"rapport client", "deliverable", "summary for client", "handover doc",
"livrable", "ship and handover", "finaliser et livrer".
argument-hint: [optional: language fr|en, --include-deploy, --skip-deploy, --skip-seo, --skip-audits, --skip-fix-loop, --max-iterations N, --audit-max-age <duration>, --output <path>]
disable-model-invocation: false
allowed-tools:

View File

@ -1,22 +1,14 @@
---
name: doc
description: |
Full documentation audit and sync. Auto-detects what doc files the project
actually has — root docs (README, CLAUDE.md, INSTALL.md, CONFIGURE.md,
USAGE.md, DEPLOY.md, CONTRIBUTING.md, CHANGELOG.md), docs/**/*.md, project-state
files in .claude/{tasks,audits,memory}/, and inline comments (JSDoc, docstrings,
rustdoc, godoc). Stack-aware: detects framework + deploy complexity, proposes
DEPLOY.md only when non-trivial (Docker, fly.toml, k8s, multi-stage CI), skips
for trivial deploys (FTP push, single scp, plain static). Enforces README
presence with typical GitHub layout (title, quick start, links to existing
sub-docs). Cross-references git history for drift; detects added features
missing from docs and removed features still documented (feature delta
detection). Reports drift with commit refs, proposes fixes, patches approved
items.
Trigger: "doc", "sync docs", "audit docs", "update readme", "check documentation",
"are docs up to date", "documentation drift", "stale docs", "new feature not documented",
"removed feature still in docs", "create README", "should I have a DEPLOY doc".
Replaces the old /readme skill with broader scope.
Use when documentation may be out of sync with code — added features
missing from docs, removed features still documented, or README / INSTALL
/ DEPLOY / CHANGELOG drift detected. Stack-aware audit, cross-references
git history, patches approved items.
Triggers: "doc", "sync docs", "audit docs", "update readme", "check
documentation", "are docs up to date", "documentation drift", "stale docs",
"new feature not documented", "removed feature still in docs",
"create README", "should I have a DEPLOY doc".
argument-hint: [leave empty for full audit, or list specific files/docs to check]
disable-model-invocation: false
allowed-tools:

View File

@ -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

View File

@ -1,6 +1,6 @@
---
name: init-project
description: Full project init: interview → design → scaffold → implement (TDD). Two validation gates.
description: Use when initializing a brand-new project from scratch — needs interview, design, scaffold, and TDD implementation. Multi-agent orchestrator: plugin-advisor + interviewer + analyzer + scaffolder with two validation gates. Triggers: "init project", "new project", "start project from scratch", "scaffold project", "init-project".
argument-hint: <project idea or description>
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Grep, Glob

View File

@ -1,6 +1,6 @@
---
name: onboard
description: Onboard an existing repo — detect archetype, install claude-config, run full audit (debt/SEO/GEO/UI-UX/perf/security/a11y/docs), output prioritized improvement plan in .claude/audits/ + .claude/tasks/. Use on repos not created via /init-project.
description: Use when bringing an existing repo into the claude-config framework — needs archetype detection, config install, full multi-axis audit (debt/SEO/GEO/UI-UX/perf/security/a11y/docs), and prioritized backlog. Multi-agent orchestrator. Do NOT use for repos created via /init-project. Triggers: "onboard", "onboard project", "audit existing repo", "setup existing project".
argument-hint: [optional hints: "Python FastAPI" | "add gsd" | "Next.js monorepo" | "force-archetype:wordpress"]
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Glob, Grep

View File

@ -1,25 +1,16 @@
---
name: seo
description: |
Full SEO + GEO audit and optimization for any web project.
Runs the seo-analyzer (classical search — Google, Bing, DuckDuckGo)
and geo-analyzer (AI search — ChatGPT, Perplexity, Claude, Gemini,
Google AI Overviews, Copilot) IN PARALLEL, then consolidates their
output into a unified .claude/audits/SEO.md report.
Covers: meta, OG, JSON-LD (classical + GEO-optimised schemas),
sitemap, robots.txt (including AI crawlers), llms.txt, headings,
alt attrs, canonicals, hreflang, Core Web Vitals, entity SEO
(Wikidata, sameAs, Knowledge Panel), content shape for AI extraction,
AI visibility monitoring.
Trigger: "seo", "referencement", "optimize for search", "audit SEO",
"meta tags", "structured data", "JSON-LD", "sitemap", "robots.txt",
"Google ranking", "local SEO", "referencement local", "fiche Google",
"AI search", "GEO", "llms.txt", "ChatGPT visibility", "Perplexity",
"Google AI Overview".
For GEO-only audit → use /geo.
For W3C HTML/CSS validity + WCAG a11y → use /validate (syntactic conformance,
not ranking signals).
For code-only bugs → use /bugfix. For feature work → use /feat.
Use when a web project needs SEO + GEO audit or optimization — classical
search (Google, Bing, DuckDuckGo) AND AI search (ChatGPT, Perplexity,
Claude, Gemini, AI Overviews, Copilot). Parallel multi-agent orchestrator:
dispatches seo-analyzer + geo-analyzer concurrently, merges envelopes into
.claude/audits/SEO.md.
Triggers: "seo", "referencement", "audit SEO", "meta tags",
"structured data", "JSON-LD", "sitemap", "robots.txt", "Google ranking",
"local SEO", "AI search", "GEO", "llms.txt", "ChatGPT visibility",
"Perplexity", "Google AI Overview".
For GEO only → /geo. For W3C/a11y → /validate. For bugs → /bugfix.
argument-hint: optional keywords/scope, e.g. "local SEO plombier 91 94 77" or "SaaS B2B content strategy"
allowed-tools:
- Read

View File

@ -1,6 +1,6 @@
---
name: ship-feature
description: Ship feature end-to-end: design → plan → implement (TDD) → review → finish
description: Use when shipping a new feature end-to-end — needs design brainstorm, planning, TDD implementation with subagents, error recovery, code review, and finish. Multi-agent orchestrator (9-step pipeline). Triggers: "ship feature", "ship-feature", "build and merge", "feature end-to-end", "implement and ship".
argument-hint: <feature description>
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Grep, Glob

View File

@ -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