Remove standalone skill-authoring workflow

.agents/skills/legibility--enhancer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: legibility--enhancer
-description: Collaboratively walks a human through creating high-quality AGENTS.md files throughout a codebase, implementing progressive disclosure architecture. Use when creating or updating AGENTS.md files, onboarding a repository to agent-first practices, or remediating findings from legibility--auditor. Do not use when evaluating existing documentation coverage (use legibility--auditor) or when creating agent skills (use meta--skill-creator).
+description: Collaboratively walks a human through creating high-quality AGENTS.md files throughout a codebase, implementing progressive disclosure architecture. Use when creating or updating AGENTS.md files, onboarding a repository to agent-first practices, or remediating findings from legibility--auditor. Do not use when evaluating existing documentation coverage (use legibility--auditor) or when creating agent skills (follow `docs/skill-development.md` instead).
 ---
 
 # Legibility Enhancer

.agents/skills/meta--onboarding/SKILL.md

@@ -388,7 +388,8 @@ Once the onboarding outcomes are proven, these ongoing skills become more useful
 | `autonomy--sre-agent` | When investigating production issues, errors, or incidents |
 | `legibility--auditor` | Quarterly, to audit documentation coverage as the codebase evolves |
 | `autonomy--test-readiness-auditor` | When test infrastructure changes or new modules are added |
-| `meta--skill-creator` | When you need to create new project-specific skills |
+
+If the team later needs project-specific skills, treat that as follow-on library maintenance rather than part of the six-outcome proof loop. Use `docs/skill-development.md` as the canonical guide for authoring or revising those skills.
 
 ### Recommended Cadence