claude/SKILL.md at 0fb634deca8dc465608265c73fb8c666719790a1

bastien 0fb634deca 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>

2026-05-11 16:09:21 +02:00

1.3 KiB

Raw Blame History

name

description

argument-hint

allowed-tools

geo

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.

optional keywords/scope, e.g. "SaaS B2B content GEO" or "audit llms.txt et entity SEO"

Read

Edit

Write

Bash

Grep

Glob

Agent

WebFetch

WebSearch

Load and follow strictly:

$HOME/.claude/agents/geo-analyzer.md

Execute the GEO-ANALYZER agent on the following target:

$ARGUMENTS

Note on integration

If .claude/audits/SEO.md already exists, the geo-analyzer will merge its findings into that file's §7 — Optimisation GEO / IA section (rather than writing a separate GEO.md). This keeps a single consolidated report when both /seo and /geo have been run.

If no .claude/audits/SEO.md exists, the agent writes .claude/audits/GEO.md (run mkdir -p .claude/audits first).

1.3 KiB Raw Blame History

Note on integration

1.3 KiB

Raw Blame History