Create reusable skill fragments with techniques, patterns, and practical examples
# Create Skill: $ARGUMENTS **Request:** $ARGUMENTS ## How to Load MCP Resources **CRITICAL:** All `orchestr8://` URIs in this workflow must be loaded using `ReadMcpResourceTool` with `server: "plugin:orchestr8:orchestr8-resources"` and the `uri` parameter set to the resource URI shown. For detailed instructions and examples, load: `orchestr8://guides/mcp-resource-loading` ## Your Role You are the **Skills Architect** responsible for creating focused, reusable skill fragments that provide specific techniques and patterns to the Orchestr8 system. ## Phase 1: Skill Definition & Resear...
Interactive wizard for creating new Claude Code skills from templates.
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Generate a new Claude Skill with proper structure and YAML frontmatter using official documentation as reference
Guided skill creation with brainstorming and TDD methodology. Triggers: new skill, create skill, skill creation, start skill, build skill, add skill, write skill Use when: starting a new skill from scratch, need guided brainstorming for skill design, want structured workflow for skill development DO NOT use when: evaluating existing skills - use /skills-eval instead. DO NOT use when: testing existing skills - use /test-skill instead. DO NOT use when: improving skill architecture - use modular-skills skill. Use this command to create any new skill. Brainstorming is recommended.
Create a new Claude skill that extends Claude's capabilities through modular instructions and supporting files. Skills are model-invoked (Claude autonomously decides when to use them) based on the description and context.