refactor: enforce layer responsibilities across all skills

Rewrote docs/standard.md as the single source of truth for skill
structure (menu/tools/recipes/manual analogy). Trimmed all SKILL.md
files to pure routers, moved recruitment workflow out of SKILL.md
into workflows/recruitment.md, removed duplicated standards from
workflow files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

claw-skills/workflows/improve-skills.md

@@ -1,24 +1,13 @@
-# improve-skills
+# Improve Skills
 
-Used when a skill or workflow has one of these problems:
+When a skill has misleading descriptions, missing coverage, or suboptimal behavior.
 
-- Misleading or ambiguous
-- Missing coverage for your use case
-- Suboptimal or confusing behavior
+> See `{baseDir}/docs/standard.md` for skill structure and layer responsibilities.
 
 ## Principle
 
 Improvement is better than workaround. Fix problems when you find them, so others don't hit the same pitfall.
 
-## Requirement
-
-**All skill-related documentation must be written in English.** This applies to:
-- Creating new skills or workflows
-- Improving or correcting existing skills
-- Any other documentation within skills
-
-> See `{baseDir}/docs/standard.md` for skill structure and writing requirements.
-
 ## Process
 
 ### 1. Identify the Problem
@@ -29,24 +18,25 @@ Improvement is better than workaround. Fix problems when you find them, so other
 
 ### 2. Assess Impact
 
-- How many people will this affect?
+- How many agents will this affect?
 - Is it a design issue or a documentation issue?
 - What's the complexity of the fix?
 
 ### 3. Design the Fix
 
-- **Documentation issue** → update SKILL.md or related descriptions
-- **Logic flaw** → modify the script or skill logic
+- **Documentation issue** → update SKILL.md or docs/
+- **Logic flaw** → modify the script
 - **Missing coverage** → add a new workflow or script
 - **Process issue** → redesign the workflow
 
 ### 4. Implement
 
-- Make changes locally or on a branch
+- Make changes locally
 - Update SKILL.md if behavior changed
 - Test if the change is significant
 
 ### 5. Submit
 
-- Call `{baseDir}/scripts/promote-improvements` to push to your branch.
-- Commit message should describe what was changed and why
+Call `{baseDir}/scripts/promote-improvements` to push to your branch.
+
+Commit message should describe what was changed and why.