Ecc Guide
Get accurate, up-to-date answers about Everything Claude Code—skills, commands, agents, hooks, rules, and install profiles—by reading the live repo instead of stale memory.
Overview
ECC Guide is a journey-wide agent skill that maps the live Everything Claude Code repository—so a solo builder can choose skills, commands, agents, hooks, rules, and install profiles from current files before committing
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill ecc-guideWhat is this skill?
- Answers from current files via `catalog.js --json`, sorted `SKILL.md` / command / agent listings, and `install-plan.js`
- Covers what ECC includes, selective install, duplicate installs, reset/uninstall, and how commands, skills, agents, hook
- Guided onboarding for new ECC users choosing profiles and components that fit a specific project shape.
- Core principle: never hard-code catalog counts or install steps—ECC changes quickly and live inspection prevents stale a
- Inspect commands include `node scripts/ci/catalog.js --json` and `node scripts/install-plan.js --list-profiles`.
Adoption & trust: 1.2k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are new to Everything Claude Code or lost in overlapping install paths and do not know which skill, hook, or profile actually exists today.
Who is it for?
Builders onboarding to ECC or debugging confusing installs who need live catalog reads instead of outdated README guesses.
Skip if: Projects not using Everything Claude Code, or when you already know the exact skill slug and only need to invoke that skill directly.
When should I use this skill?
User asks what ECC includes, needs a skill/command/agent/hook/rule/profile, is new to the repo, asks how do I do X with ECC, or is confused by install/uninstall paths.
What do I get? / Deliverables
You get a repo-grounded map of ECC components and install choices so you can selectively enable the right agents, skills, and hooks for your project.
- Repo-grounded explanation of relevant ECC components
- Concrete file paths and install-profile recommendations
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
List ECC research-oriented skills from live `skills/` before picking a competitor-analysis workflow.
Compare install profiles via `install-plan.js` to scope which ECC commands you need for a prototype repo.
Run `catalog.js --json` to see which agents and hooks match your backend integration task.
Locate ECC review rules and hooks from sorted `find` output before enabling PR checks.
Clarify reset/uninstall paths when duplicate ECC installs break hook loading during iteration.
How it compares
Use instead of asking the model to recall ECC from training data—it is a live-repo navigator, not a static cheat sheet.
Common Questions / FAQ
Who is ecc-guide for?
Solo and indie developers adopting or extending Everything Claude Code who need help finding skills, commands, agents, hooks, rules, and install profiles without stale counts.
When should I use ecc-guide?
Use it journey-wide whenever you ask what ECC includes, how do I do X with ECC, which profile fits my repo, or how reset/uninstall works—in Build agent-tooling, Ship launch prep for review hooks, or Operate iterate when you adjust automation.
Is ecc-guide safe to install?
It mainly reads repository files and runs documented Node scripts; confirm trust in the ECC repo and review Security Audits on this Prism page before installing any ECC bundle.
SKILL.md
READMESKILL.md - Ecc Guide
# ECC Guide Use this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code. ## When To Use Use this skill when the user: - asks what ECC includes - wants help finding a skill, command, agent, hook, rule, or install profile - is new to the repository and needs a guided path - asks "how do I do X with ECC?" - asks which ECC components fit a project - needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate - is confused by install paths, duplicate installs, reset/uninstall, or selective install options ## Core Principle Answer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale. When the ECC repository is available, inspect the relevant files before giving a concrete answer: ```bash node scripts/ci/catalog.js --json find skills -maxdepth 2 -name SKILL.md | sort find commands -maxdepth 1 -name '*.md' | sort find agents -maxdepth 1 -name '*.md' | sort node scripts/install-plan.js --list-profiles node scripts/install-plan.js --list-components --json ``` Use the smallest set of reads needed for the user's question. ## Repository Map - `README.md`: install paths, uninstall/reset guidance, public positioning, FAQs - `AGENTS.md`: contributor guidance and project structure - `agent.yaml`: exported gitagent surface and command list - `commands/`: maintained slash-command compatibility shims - `skills/*/SKILL.md`: reusable workflows and domain playbooks - `agents/*.md`: delegated subagent role prompts - `rules/`: language and harness rules - `hooks/README.md`, `hooks/hooks.json`, `scripts/hooks/`: hook behavior and safety gates - `manifests/install-*.json`: selective install modules, components, profiles, and target support - `docs/`: harness guides, architecture notes, translated docs, release docs ## Response Style Lead with the answer, then give the next action. Most users do not need a full catalog dump. Good first response shape: 1. what to use 2. why it fits 3. exact file or command to inspect 4. one next command or question Avoid: - listing every skill or command by default - repeating large README sections - recommending retired command shims when a skill-first path exists - claiming a component exists without checking the filesystem - replacing install guidance with manual copy commands when the managed installer supports the target ## Common Tasks ### New User Onboarding Give a short menu: - install or reset ECC - pick skills for a project - understand commands vs skills - inspect hooks and safety behavior - run a harness audit - find a specific workflow Point to `README.md` for install/reset and `/project-init` for project-specific onboarding. ### Feature Discovery For "what should I use for X?": 1. Search `skills/`, `commands/`, and `agents/`. 2. Prefer skills as the primary workflow surface. 3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior. 4. Mention agents when delegation is useful. Useful searches: ```bash rg -n "<query>" skills commands agents docs find skills -maxdepth 2 -name SKILL.md | sort ``` ### Install Guidance Use managed install paths: ```bash node scripts/install-plan.js --list-profiles node scripts/install-plan.js --profile minimal --target claude --json node scripts/install-apply.js --profile minimal --target claude --dry-run ``` For specific skill installs: ```bash node scripts/install-plan.js --skills <skill-id> --target claude --json node scripts/install-apply.js --skills <skill-id> --target claude --dry-run ``` Warn users not to stack plugin installs and full manual/profile installs unless they intentionally want dup