skill-creator
Create new Agent Skills interactively or from templates. Use when user wants to create, generate, scaffold, or build a new skill, or mentions creating skills, writing skills, skill templates, skill development.
Create new Agent Skills interactively or from templates. Use when user wants to create, generate, scaffold, or build a new skill, or mentions creating skills, writing skills, skill templates, skill development.
Helper agent to scaffold new Gemini CLI skills. Use this when the user wants to "make a new skill", "add a skill", or "teach you a new capability" via the skill system.
Amazon Bedrock Runtime API for model inference including Claude, Nova, Titan, and third-party models. Covers invoke-model, converse API, streaming responses, token counting, async invocation, and guardrails. Use when invoking foundation models, building conversational AI, streaming model responses, optimizing token usage, or implementing runtime guardrails.
Deploying fine-tuned models for production inference using native kernel optimization, vLLM, or SGLang. Triggers: inference, serving, vllm, sglang, for_inference, model merging, openai api.
Entry point for Codex-discoverable skills used by the Run-Smart AI coach.
Debug and troubleshoot claude-threads, orchestrator, and agent issues
Use when user asks where to put configuration, skills, or learnings, or discusses sharing config across projects. Provides decision criteria for the three-tier architecture (global ~/.claude, plugin, project-local .claude) to prevent duplication and ensure reusability. Invoke before creating new skills or configuration to determine the correct tier and location.
Analyze LangGraph application architecture, identify bottlenecks, and propose multiple improvement strategies
Create skill groups (multiple related skills packaged as a plugin). Use when creating plugins, organizing multiple related skills, building skill families, packaging tools together, or when user mentions "plugin", "multiple skills", "related skills", "skill group", "skill family", "organize skills", "cross-reference", "package skills", "shared agents". ALWAYS consider this pattern when someone asks to "create a skill" - they often need a skill GROUP packaged as a plugin.
Generate Claude Skills using Cortex Architecture pattern. Factors skills into Orchestrator (manifest), Protocols (logic), and Standards (presentation) for attention isolation and modularity. Use when creating new Claude Skills or refactoring monolithic skill.md files.
Use when integrating LLMs (OpenAI, Qwen, Claude), extracting structured data from text, building prompts, parsing AI responses, handling JSON output, or implementing multi-step AI workflows
Audit and improve Claude Code configuration. Use when user asks to 'check settings', 'audit config', 'fix settings', 'update claude config', or mentions settings.json issues.
Create event-driven hooks for Claude Code plugins (PreToolUse, PostToolUse, Stop, SessionStart, etc.). WHEN: MUST use when creating Claude Code hooks. Invoke with "/claude-hook-development" or "create a hook", "new PreToolUse hook", "write PostToolUse handler". WHEN NOT: Creating agents (use claude-agent-creator), writing hookify rules (use claude-hookify-rules).
This skill should be used when the user asks "should I use multi-agent", "MAS vs single agent", "when to use multiple agents", "do I need multi-agent", "single agent or multi-agent", "simplicity test", "agent necessary", "could this be a script", or is deciding whether a task requires multiple agents. Provides evidence-based decision criteria including simplicity testing.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Transformer architecture fundamentals. Covers self-attention mechanism, multi-head attention, feed-forward networks, layer normalization, and residual connections. Essential concepts for understanding LLMs.
Expert in load balancing and dynamic task allocation for multi-agent systems. Specializes in optimal routing based on agent capability, availability, and cost (Token Economics).