aptitudepi/dotfiles/ecc-guide
Claude Code and agent skill by aptitudepi/dotfiles
- community
Checking that the SKILL.md file is still in the repository.
Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.
Install
npx vskill@latest install aptitudepi/dotfiles/ecc-guideSKILL.md
The same SKILL.md was published earlier as affaan-m/everything-claude-code/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:
Use the smallest set of reads needed for the user's question.
Repository Map
README.md: install paths, uninstall/reset guidance, public positioning, FAQsAGENTS.md: contributor guidance and project structureagent.yaml: exported gitagent surface and command listcommands/: maintained slash-command compatibility shimsskills/*/SKILL.md: reusable workflows and domain playbooksagents/*.md: delegated subagent role promptsrules/: language and harness ruleshooks/README.md,hooks/hooks.json,scripts/hooks/: hook behavior and safety gatesmanifests/install-*.json: selective install modules, components, profiles, and target supportdocs/: 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:
- what to use
- why it fits
- exact file or command to inspect
- 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?":
- Search
skills/,commands/, andagents/. - Prefer skills as the primary workflow surface.
- Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.
- Mention agents when delegation is useful.
Useful searches:
Install Guidance
Use managed install paths:
For specific skill installs:
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:
- detect the stack from project files
- resolve a dry-run install plan
- inspect existing
CLAUDE.mdand settings files - ask before applying changes
- 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:
Output Templates
Short Recommendation
Search Results
Install Plan Summary
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
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking.config/opencode/skills/ecc-guide/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/aptitudepi/dotfiles/ecc-guide)