skill-conductor

# 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. ## Runtime requirements (pre-flight) Before any mode that touches scripts (CREATE, IMPROVE, VALIDATE, OPTIMIZE, PACKAGE), run the pre-flight block → **`references/runtime-setup.md`** (checks `uv`, sets `UV_BIN`/`SKILL_CONDUCTOR_DIR`, verifies LLM access). If `uv` is absent, stop and tell the user. ## 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 →...