claude/skills/doc/SKILL.md
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

891 B

name description argument-hint disable-model-invocation allowed-tools
doc 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".
leave empty for full audit
or list specific files/docs to check
false
Read
Edit
Write
Bash
Grep
Glob

Load and follow strictly:

  • $HOME/.claude/agents/doc-syncer.md

Execute the DOC SYNCER on this project.

Context from the user (if any): $ARGUMENTS