skill-conductorlisted

# Skill Conductor Full lifecycle management for agent skills: **draft → test → review → improve → repeat**. One skill to rule them all — from architecture to packaging. The core loop is always the same: write something, test it, see what fails, fix it, test again. ## How to communicate Read context cues. If the user is a skill author iterating on their own work, be direct and technical. If they're new to skills, explain the *why* behind each step — not just what to do, but why it matters. Default to conversational, not robotic. - Explain trade-offs when there's a real choice to make - Use concrete examples over abstract rules - When something fails, explain the root cause, not just the fix - Imperative voice in instructions: "Extract the data", not "You should extract" ## Modes Detect mode from context. If ambiguous, ask. | Mode | When | What happens | |------|------|-------------| | 1. CREATE | "build a skill", "new skill for..." | Full lifecycle: intent → architecture → scaffold → write → test | | 2. IMPROVE | "fix this skill", "it doesn't trigger" | Diagnose → eval loop → blind comparison → iterate | | 3. VALIDATE | "test this skill", "run evals" | Structural checks + trigger testing + 5-axis scoring | | 4. REVIEW | "review this skill", third-party assessment | 11-point quality gate, quick and focused | | 5. OPTIMIZE | "improve triggering", "description optimization" | Automated description optimization with train/test split | | 6. PACKAGE | "package for distributi