claude-ecosystem

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.

16 stars

Best use case

claude-ecosystem is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using claude-ecosystem should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/claude-ecosystem/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/tools/claude-ecosystem/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/claude-ecosystem/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How claude-ecosystem Compares

Feature / Agentclaude-ecosystemStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Claude Ecosystem

Comprehensive guide for Claude Code CLI tool, extensibility (agents/skills/output styles), and CLAUDE.md architecture.

## Module Selection

| 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` |

---

## Quick Reference

### Extension Types

| 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 Selection (Agents)

| Model | Use When | Target Time |
|-------|----------|-------------|
| `haiku` | Fast tasks, exploration | < 3s |
| `sonnet` | Balanced, most use cases | < 10s |
| `opus` | Complex reasoning | < 30s |

### CLAUDE.md Token Budget

| Complexity | Target Tokens |
|-----------|---------------|
| Simple | 100-200 |
| Medium | 200-400 |
| Complex | 400-800 |
| Maximum | 1000 |

---

## Extensibility Principles

### Core Truths

| 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 |

### Decision Heuristics

| 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 |

### Activation Keywords

**The description field is your activation gate.** Include:
1. Task verbs: create, build, debug, fix, deploy
2. Problem descriptions: slow, broken, failing
3. Artifact types: component, API, database
4. Casual synonyms: "make it faster" → optimize

---

## Common Workflows

### Create Agent

```yaml
---
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)
```

### Create Skill

```yaml
---
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]
```

### Initialize CLAUDE.md

1. Analyze codebase (language, framework, structure)
2. Extract code style, commands, patterns
3. Generate with template, customize
4. Validate commands, check token count
5. Target <400 lines, prefer <250

**Detailed:** `references/initialization-workflow.md`

### Optimize CLAUDE.md

1. Evaluate token efficiency
2. Find redundancy, outdated info
3. Apply token reduction techniques
4. Target 40%+ reduction
5. Verify critical info retained

**Detailed:** `references/optimization-patterns.md`

---

## Anti-Patterns

| 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 |

---

## Quality Signals

### Good Signs
- Frontmatter reads like "when to use" guide
- First 10 lines provide actionable guidance
- Expert would nod "yes, that's how I think"
- Explicit constraints on what it does NOT handle

### Warning Signs
- >50% reference tables or field definitions
- No mention of "when NOT to use"
- Generic language for any domain
- Body exceeds 600 lines

---

## References

### CLI Tool
- `references/getting-started.md` - Installation, setup, auth
- `references/slash-commands.md` - Complete command catalog
- `references/mcp-integration.md` - MCP server configuration
- `references/hooks-and-plugins.md` - Hook types, plugin structure
- `references/configuration.md` - Settings hierarchy
- `references/enterprise-features.md` - IAM, SSO, sandboxing
- `references/cicd-integration.md` - GitHub Actions, GitLab CI
- `references/ide-integration.md` - VS Code, JetBrains
- `references/advanced-features.md` - Extended thinking, caching
- `references/troubleshooting.md` - Common issues
- `references/api-reference.md` - Admin, Messages, Skills APIs
- `references/best-practices.md` - Project organization, security
- `references/agent-skills.md` - Creating skills via CLI

### Extensibility
- `references/agent-development.md` - Full YAML structure, system prompts
- `references/skill-development.md` - Structure, triggers, hooks

### CLAUDE.md
- `references/initialization-workflow.md` - Creating new CLAUDE.md
- `references/optimization-patterns.md` - Token reduction techniques
- `references/integration-strategies.md` - Global config, MCP tools
- `references/output-templates.md` - Standard output formats

---

## Related Skills

**IMPORTANT:** When creating/editing prompts, use `prompt-architect` skill.

```
Skill("prompt-architect") → Create/enhance skill/agent prompt content
```

---

**Documentation:**
- llms.txt: https://context7.com/websites/claude_en_claude-code/llms.txt?tokens=10000
- Main docs: https://docs.claude.com/en/docs/claude-code/
- GitHub: https://github.com/anthropics/claude-code

Related Skills

developing-claude-code-plugins

16
from diegosouzapw/awesome-omni-skill

Build, test, and distribute Claude Code plugins with slash commands, agents, skills, hooks, MCP servers, and LSP servers. MUST be loaded when creating, reviewing, debugging, or distributing plugins. Use PROACTIVELY when user mentions plugins, extensions, marketplaces, or wants to add custom commands/agents to Claude Code.

claude-skill-creator

16
from diegosouzapw/awesome-omni-skill

Guide for creating effective Claude Code skills with proper YAML frontmatter, directory structure, and best practices. Use when creating new skills, updating existing skills, or learning about skill development.

claude-settings-audit

16
from diegosouzapw/awesome-omni-skill

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

claude-plan

16
from diegosouzapw/awesome-omni-skill

Anthropic 風格的專業計畫管理 Skill - 自然語言驅動、預設並行、全自動 GitHub 整合

claude-md-editor

16
from diegosouzapw/awesome-omni-skill

Edit and maintain CLAUDE.md and project documentation files. Use when modifying documentation, asking about best practices, or performing documentation maintenance tasks.

claude-improve-config

16
from diegosouzapw/awesome-omni-skill

Self-reflect on the current session to identify mistakes and propose improvements to .claude configuration (CLAUDE.md, hooks, skills).

claude-hooks-reference-2026

16
from diegosouzapw/awesome-omni-skill

Complete reference for Claude Code hooks system (January 2026). Use when creating hooks, understanding hook events, matchers, exit codes, JSON output control, environment variables, plugin hooks, or implementing hook scripts.

claude-code

16
from diegosouzapw/awesome-omni-skill

Claude Code CLI and development environment. Use for Claude Code features, tools, workflows, MCP integration, configuration, and AI-assisted development.

claude-code-slash-commands

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "create a command", "write a slash command", "build a plugin command", or wants to add custom commands to Claude Code.

claude-code-meta

16
from diegosouzapw/awesome-omni-skill

Build Claude Code extensions - skills, agents, hooks, plugins, marketplaces, slash commands. Use when creating Claude Code components, building new skills, writing agents, creating hooks, making plugins, setting up marketplaces, writing slash commands, fixing extension configurations, or troubleshooting Claude Code extensions. Includes builder agents for autonomous creation. Not for looking up docs - use claude-code-docs-reference for that.

claude-code-analyzer

16
from diegosouzapw/awesome-omni-skill

Analyzes Claude Code usage patterns and provides comprehensive recommendations. Runs usage analysis, discovers GitHub community resources, suggests CLAUDE.md improvements, and fetches latest docs on-demand. Use when user wants to optimize their Claude Code workflow, create configurations (agents/skills/commands), or set up project documentation.

agentsmd-claudemd-generator

16
from diegosouzapw/awesome-omni-skill

Generate AGENTS.md and CLAUDE.md files for a repository. AGENTS.md provides cross-tool agent instructions (supported by Claude Code, Cursor, Windsurf, Zed, Codex, and others). CLAUDE.md adds Claude-specific configuration and references AGENTS.md via @import. Use when a repo needs agent onboarding or when starting a new project.