Ecc Guide
Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Ecc Guide when an AI agent needs a reusable SKILL.md workflow for this job: Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.
When not to use it
Skip Ecc Guide when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ecc-guide # Save SKILL.md to ~/.claude/skills/ecc-guide/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ecc-guide/SKILL.md. For a shared project, commit the folder at .claude/skills/ecc-guide/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ecc Guide skill for this task: asks what ECC includes. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiinferred
The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# ECC Guide
Use this skill when a user needs help understanding, navigating, installing, or choosing parts of ECC.
## 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 duplicate surfaces.
### Project Onboarding
Use `/project-init` when the user wants ECC configured for a target repo. The expected sequence is:
1. detect the stack from project files 2. resolve a dry-run install plan 3. inspect existing `CLAUDE.md` and settings files 4. ask before applying changes 5. keep generated guidance minimal and repo-specific
### Troubleshooting
Ask for the target harness and install path first, then inspect:
- plugin install metadata - `.claude/`, `.cursor/`, `.codex/`, `.gemini/`, `.opencode/`, `.codebuddy/`, `.joycode/`, or `.qwen/` - `hooks/hooks.json` - install-state files - relevant command/skill files
For repo health, suggest:
```bash npm run harness:audit -- --format text npm run observability:ready npm test ```
## Output Templates
### Short Recommendation
```text Use <skill-or-command>. It fits because <reason>.
Canonical file: <path> Verify with: <command> Next: <one concrete action> ```
### Search Results
```text Best matches: - <path>: <why it matters> - <path>: <why it matters>
Recommendation: <which one to use first and why> ```
### Install Plan Summary
```text Detected: <stack evidence> Target: <harness> Plan: <profile/modules/skills> Dry run: <command> Would change: <paths> Needs approval before apply: <yes/no> ```
## Related Surfaces
- `/project-init`: stack-aware onboarding plan for a target repo - `/harness-audit`: deterministic readiness scorecard - `/skill-health`: skill quality review - `/skill-create`: generate a new skill from local git history - `/security-scan`: inspect Claude/OpenCode configuration security
Intended uses
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.