skill-workflow-packaginglisted

# Skill Workflow Packaging ## Overview Treat a skill as a controlled workflow package, not just a markdown document. It must be discoverable, triggerable, budgeted for listing, isolatable when needed, and clearly represented in the transcript. ## Source Anchors - `src/tools/SkillTool/SkillTool.ts` - `src/tools/SkillTool/prompt.ts` ## Workflow 1. Define the command identity first: name, description, `whenToUse`, aliases, and whether users can invoke it directly. 2. Put hard limits on listing text so skill discovery remains cheap enough to keep in the main prompt. 3. Make skill invocation a blocking requirement when the request clearly matches a skill. 4. Merge local skills and MCP skills carefully, but filter out plain MCP prompts that are not actually skills. 5. Choose between inline and forked execution based on isolation, token budget, and workflow complexity. 6. For forked skills, prepare context explicitly, stream progress, and record results back into the transcript. 7. Track usage, discovery source, and execution context so ranking and recommendation can improve later. 8. Prevent duplicate invocation when the skill is already loaded or already running. ## Design Rules - Write `whenToUse` as high-signal trigger language, not as generic marketing copy. - Prefer short listing descriptions that preserve match quality over long descriptions that waste turn-zero budget. - Keep invocation semantics explicit so the model does not mention a skill without calling it. - Gi