Agent SkillsAgent Skills
samhvw8

claude-ecosystem

@samhvw8/claude-ecosystem
samhvw8
12
3 forks
Updated 4/7/2026
View on GitHub

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.

Installation

$npx agent-skills-cli install @samhvw8/claude-ecosystem
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathdot_ccp/hub/skills/0-claude/SKILL.md
Branchmaster
Scoped Name@samhvw8/claude-ecosystem

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

npx agent-skills-cli list

Skill Instructions


name: claude-ecosystem description: "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."

Claude Ecosystem

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

Module Selection

NeedModuleReference
Setup/ConfigurationCLIreferences/getting-started.md, references/configuration.md
Slash CommandsCLIreferences/slash-commands.md
MCP ServersCLIreferences/mcp-integration.md
Hooks & PluginsCLIreferences/hooks-and-plugins.md
Create AgentsExtensibilityreferences/agent-development.md
Create SkillsExtensibilityreferences/skill-development.md
Output StylesExtensibilityreferences/skill-development.md
Init CLAUDE.mdArchitecturereferences/initialization-workflow.md
Optimize CLAUDE.mdArchitecturereferences/optimization-patterns.md
Enterprise/CI-CDCLIreferences/enterprise-features.md, references/cicd-integration.md
TroubleshootingCLIreferences/troubleshooting.md

Quick Reference

Extension Types

TypeInvocationPurposeLocation
AgentsTask toolSpecialized sub-processes.claude/agents/
SkillsModel-invokedDomain knowledge.claude/skills/{name}/
Output Styles/output-styleModify main agent.claude/output-styles/

Model Selection (Agents)

ModelUse WhenTarget Time
haikuFast tasks, exploration< 3s
sonnetBalanced, most use cases< 10s
opusComplex reasoning< 30s

CLAUDE.md Token Budget

ComplexityTarget Tokens
Simple100-200
Medium200-400
Complex400-800
Maximum1000

Extensibility Principles

Core Truths

TruthMeaning
Expertise TransferMake Claude think like expert, not follow steps
Flow, Not FrictionProduce output, not intermediate work
Voice Matches DomainSound like practitioner, not documentation
Focused Beats ComprehensiveConstrain ruthlessly

Decision Heuristics

RuleGuidance
3-File Rule3+ files → agent. Enhances YOUR work → skill.
Delegation TestRuns independently? Agent. Guides you? Skill.
Activation BreadthTrigger on 80% of relevant requests
Tool ConstraintStart 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

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

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

PatternProblemFix
Kitchen Sink Agent10+ tools, handles "everything"Constrain to 3-5 tools
Echo SkillRestates docs without insightAdd expert layer
Invisible TriggerDescription uses only formal termsInclude user language
Procedure ManualStep 1, 2, 3...Teach patterns, not steps
Over-DocumentationCLAUDE.md > 400 linesDocument 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:

More by samhvw8

View all
3d-graphics
12

3D web graphics with Three.js (WebGL/WebGPU). Capabilities: scenes, cameras, geometries, materials, lights, animations, model loading (GLTF/FBX), PBR materials, shadows, post-processing (bloom, SSAO, SSR), custom shaders, instancing, LOD, physics, VR/XR. Actions: create, build, animate, render 3D scenes/models. Keywords: Three.js, WebGL, WebGPU, 3D graphics, scene, camera, geometry, material, light, animation, GLTF, FBX, OrbitControls, PBR, shadow mapping, post-processing, bloom, SSAO, shader, instancing, LOD, WebXR, VR, AR, product configurator, data visualization, architectural walkthrough, interactive 3D, canvas. Use when: creating 3D visualizations, building WebGL/WebGPU apps, loading 3D models, adding animations, implementing VR/XR, creating interactive graphics, building product configurators.

github-search
12

Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.

design-principles
12

UI/UX design system for dashboards, admin panels, SaaS interfaces, and web apps. Stack: React, Tailwind, CSS, styled-components. Capabilities: spacing systems (4px grid), color palettes, typography hierarchy, shadows/elevation, card layouts, dark mode, component styling. Actions: design, style, beautify, fix, improve, refactor UI components. Keywords: ugly, inconsistent, cluttered, unprofessional, spacing, padding, margin, colors, fonts, shadows, cards, buttons, forms, navigation, sidebar, layout. Use when: building new UI, fixing ugly interfaces, making things look professional/modern/clean, implementing design systems, styling components, choosing colors/fonts/spacing.

git-workflow
12

Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.