Claude Code ecosystem expertise. Modules: CLI tool (setup, slash commands, MCP servers, hooks, plugins, CI/CD), extensibility (agents, skills, output styles creation), CLAUDE.md (project instructions, optimization). Actions: configure, troubleshoot, create, deploy, integrate, optimize Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, agent, skill, output-style, SKILL.md, subagent, Task tool, project instructions, token optimization. Use when: learning Claude Code features, configuring settings, creating skills/agents/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, initializing or optimizing CLAUDE.md files.
87
83%
Does it follow best practices?
Impact
91%
1.71xAverage score across 3 eval scenarios
Passed
No findings from the security scan
The canonical home for this skill is claude-ecosystem in majiayu000/claude-skill-registry
Comprehensive guide for Claude Code CLI tool, extensibility (agents/skills/output styles), and CLAUDE.md architecture.
| Need | Module | Reference |
|---|---|---|
| Setup/Configuration | CLI | references/getting-started.md, references/configuration.md |
| Slash Commands | CLI | references/slash-commands.md |
| MCP Servers | CLI | references/mcp-integration.md |
| Hooks & Plugins | CLI | references/hooks-and-plugins.md |
| Create Agents | Extensibility | references/agent-development.md |
| Create Skills | Extensibility | references/skill-development.md |
| Output Styles | Extensibility | references/skill-development.md |
| Init CLAUDE.md | Architecture | references/initialization-workflow.md |
| Optimize CLAUDE.md | Architecture | references/optimization-patterns.md |
| Enterprise/CI-CD | CLI | references/enterprise-features.md, references/cicd-integration.md |
| Troubleshooting | CLI | references/troubleshooting.md |
| Type | Invocation | Purpose | Location |
|---|---|---|---|
| Agents | Task tool | Specialized sub-processes | .claude/agents/ |
| Skills | Model-invoked | Domain knowledge | .claude/skills/{name}/ |
| Output Styles | /output-style | Modify main agent | .claude/output-styles/ |
| Model | Use When | Target Time |
|---|---|---|
haiku | Fast tasks, exploration | < 3s |
sonnet | Balanced, most use cases | < 10s |
opus | Complex reasoning | < 30s |
| Complexity | Target Tokens |
|---|---|
| Simple | 100-200 |
| Medium | 200-400 |
| Complex | 400-800 |
| Maximum | 1000 |
| Truth | Meaning |
|---|---|
| Expertise Transfer | Make Claude think like expert, not follow steps |
| Flow, Not Friction | Produce output, not intermediate work |
| Voice Matches Domain | Sound like practitioner, not documentation |
| Focused Beats Comprehensive | Constrain ruthlessly |
| Rule | Guidance |
|---|---|
| 3-File Rule | 3+ files → agent. Enhances YOUR work → skill. |
| Delegation Test | Runs independently? Agent. Guides you? Skill. |
| Activation Breadth | Trigger on 80% of relevant requests |
| Tool Constraint | Start with 2-3 essential tools |
The description field is your activation gate. Include:
---
name: agent-name
description: "Use when [use case]. PROACTIVELY for [triggers].\n\nExamples:\n<example>\nContext: [situation]\nuser: [request]\nassistant: [response]\n</example>"
tools: Grep, Glob, Read, Bash
model: haiku
---
# Agent Name
Mission statement.
## Strategy
[Approach]
## Does NOT Do
- [boundary] (use X instead)---
name: skill-name
description: "[Core purpose]. [Technologies]. Capabilities: [list].
Actions: [verbs]. Keywords: [triggers]. Use when: [scenarios]."
allowed-tools: Read, Grep, Glob
---
# Skill Name
## Patterns
### [Pattern Name]
**When you see:** [Observable trigger]
**This indicates:** [Expert insight]
**Therefore:** [Action]
**Watch out:** [Pitfall]Detailed: references/initialization-workflow.md
Detailed: references/optimization-patterns.md
| Pattern | Problem | Fix |
|---|---|---|
| Kitchen Sink Agent | 10+ tools, handles "everything" | Constrain to 3-5 tools |
| Echo Skill | Restates docs without insight | Add expert layer |
| Invisible Trigger | Description uses only formal terms | Include user language |
| Procedure Manual | Step 1, 2, 3... | Teach patterns, not steps |
| Over-Documentation | CLAUDE.md > 400 lines | Document project-specific only |
50% reference tables or field definitions
references/getting-started.md - Installation, setup, authreferences/slash-commands.md - Complete command catalogreferences/mcp-integration.md - MCP server configurationreferences/hooks-and-plugins.md - Hook types, plugin structurereferences/configuration.md - Settings hierarchyreferences/enterprise-features.md - IAM, SSO, sandboxingreferences/cicd-integration.md - GitHub Actions, GitLab CIreferences/ide-integration.md - VS Code, JetBrainsreferences/advanced-features.md - Extended thinking, cachingreferences/troubleshooting.md - Common issuesreferences/api-reference.md - Admin, Messages, Skills APIsreferences/best-practices.md - Project organization, securityreferences/agent-skills.md - Creating skills via CLIreferences/agent-development.md - Full YAML structure, system promptsreferences/skill-development.md - Structure, triggers, hooksreferences/initialization-workflow.md - Creating new CLAUDE.mdreferences/optimization-patterns.md - Token reduction techniquesreferences/integration-strategies.md - Global config, MCP toolsreferences/output-templates.md - Standard output formatsIMPORTANT: When creating/editing prompts, use prompt-architect skill.
Skill("prompt-architect") → Create/enhance skill/agent prompt contentDocumentation:
a1e9f44
Canonical home
since Feb 24, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.