Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

ECC Guide · affaan-m | DecimalAI

Ecc Guide

SkillScore55Maintained

ecc-guide

Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.

agent-toolingby affaan-m

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

AI Engineer pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/ecc-guide/SKILL.md

decimalai skills pull ecc-guide --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/ecc-guide/SKILL.md https://app.decimal.ai/s/ecc-guide/SKILL.md

Raw file: /s/ecc-guide/SKILL.md ↗ · machine-readable summary at /s/ecc-guide.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 55d ago

—+13% tokens0% turns55% of whole cases pass with skill (12/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-21	✗→✓	▲ Improved	—	—
case-09	✗→✓	▲ Improved	—	—
case-22	✗→✓	▲ Improved	—	—
case-17	✗→✓	▲ Improved	—	—
case-13	✗→✓	▲ Improved	—	—

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/30/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

affaan-m / ECC

skills/ecc-guide/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

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:

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/, and agents/.
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:

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:

detect the stack from project files
resolve a dry-run install plan
inspect existing CLAUDE.md and 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:

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

Illustrative Want to see what ecc-guide would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

7/27/2026, 16:35 UTC · 22 cases

Measured on 15 comparable cases — below the 22 needed to publish a lift, so this result is shown here but not on the registry card or leaderboard.

Lift

+55%

55% vs 0%

Agent turns

1.0 vs 1.0

Tokens

+13%

2,052.93 vs 1,810.13

fail → pass · 12fail → fail · 10

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I am looking for a workflow inside Everything Claude Code to help with database migrations and schema validation. Could you give me a short recommendation that highlights the best component for this, explains why it fits my task, references the canonical file and verification command, and tells me what single action to take next?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-19 I need a short recommendation for refactoring code using Everything Claude Code. Please structure your response following the standard short recommendation format.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-21 I am having trouble with conflicting hook safety behaviors across harness directories. Which configuration file defines the hook safety gates?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-05 I ran into a git merge conflict while rebasing my feature branch onto main. How do I resolve git rebase conflicts step by step?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-09 I want to generate a dry-run install plan for the minimal profile targeting Claude Code. What command script should I invoke?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-22 I want to create a new skill based on my local git commit history. Which slash command or surface handles this?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-03 I am trying to find security auditing and configuration scanning tools within Everything Claude Code. Could you search the catalog and present the results by showing the best matching paths with a quick explanation for each, followed by a primary recommendation on which workflow to try first and why?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-06 My Node.js project has vulnerable dependencies reported by npm audit. How do I upgrade semantic version ranges safely in package.json?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-17 I need to programmatically output the entire current component catalog as JSON from the repository scripts. Which script should I execute?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-08 I want to add code review automation to my Claude environment. Should I use a slash command shim or a skill workflow, and how should I verify what exists?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-13 My Claude harness environment seems misconfigured. What npm command checks repo harness health deterministically?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-04 I am writing a custom Bash pre-commit script for my repository to enforce commit message formats. Can you write the full Bash script code to parse conventional commits?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-12 I want to configure an existing repository using /project-init. What initial steps should be taken before writing configuration changes to disk?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-18 What command lists all available installation profiles supported by the managed installer?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-20 What components does Everything Claude Code offer? Please give me a quick overview without listing every single component in the repo.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-16 Which directory contains the selective install manifests for target support and profiles?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-02 I need help setting up an install plan for Everything Claude Code on a TypeScript project using Claude Code. Can you summarize the setup path for me? Please provide an install plan summary listing the stack evidence detected, target platform, planned components, the exact dry-run command, expected path modifications, and whether explicit confirmation is needed before writing changes.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-07 I just cloned Everything Claude Code for the first time and feel overwhelmed. Can you give me a quick menu of options to get started?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-10 I only want to install one specific skill into my harness without running a full profile installer. What is the managed CLI invocation?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-11 Can I install Everything Claude Code as a plugin and also copy all profiles manually into my project at the same time?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-14 How do I verify if my environment's observability setup is ready?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-15 Where in the Everything Claude Code repository is the exported gitagent surface and command list stored?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 15 counted toward the lift figure. The other 7 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +55 percentage points is the difference between those two pass rates over the 15 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 0%
Pass rate with the skill: 54.6%
Cases attempted: 22
Cases counted toward lift: 15
Cases that regressed: 2
Skill version measured: v1
Run completed: 7/27/2026, 16:35 UTC

The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run55

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 55 days ago

Other measured skills in the registry, with their headline benchmark lift.