New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Configure Ecc

by affaan-m in affaan-m/ECC

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's…

MITAuto-check passed

Install Configure Ecc

skills CLI
$ npx skills add affaan-m/ECC --skill configure-ecc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC configure-ecc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/configure-ecc .claude/skills/configure-ecc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
configure-ecc
GitHub stars
276k
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
839 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's…

  • Works in 5 steps: Inventory without changing anything → Collect exactly two choices → Preview and confirm once → …
  • Repairing an ECC installation
  • SKILL.md covers Route by the current harness, Claude Code: run the full…, Codex: use the native plugin… and Kimi: install the project…
  • Calls npx, codex and claude

What it does

Configure Ecc is an agent skill from affaan-m/ECC. Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Kimi. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • Repairing an ECC installation
  • Changing hook profiles
  • Moving ECC between install scopes

Example prompts

  • “/configure-ecc”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Inventory without changing anything
  2. Collect exactly two choices
  3. Preview and confirm once
  4. Apply the explicit choices
  5. Verify, then render the welcome

What it can do on your machine

Read from SKILL.md and the folder at commit 4eb71d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • codex
    • claude
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Configure Ecc loads about 2k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 839 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 4eb71d9, republished under its MIT licence (© affaan-m). 839 words, ~1,995 tokens.

Download SKILL.mdSave it as .claude/skills/configure-ecc/SKILL.md (or your agent's skills folder).
name
configure-ecc
description
Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.
metadata.origin
ECC

Configure ECC

Run a conversational wizard inside the current harness. Inventory first, collect only supported choices, preview, confirm once, apply non-interactively, verify, and show the welcome only after success. Never clone ECC into a temporary directory or copy plugin components by hand.

For a human-operated terminal, the canonical entry points are ecc setup and npx ecc-universal setup. Inside a harness, use the explicit non-interactive commands below instead.

Route by the current harness

  • In Claude Code, use the full scope-and-hook wizard below.
  • In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or map ECC's four Claude hook profiles onto Codex.
  • In Kimi, install the project surface under ./.kimi-code. Kimi does not provide ECC's Claude lifecycle-hook profiles.
  • If the harness is uncertain, state the detected evidence and ask which harness to configure before running a mutating command.

This skill is a post-install reconfiguration path. It cannot intercept or replace a provider's built-in first-install UI.

Claude Code: run the full conversational wizard

1. Inventory without changing anything

Run both commands and summarize the installed ECC scope, enabled state, and marketplace source:

bash
claude plugin list --json
claude plugin marketplace list --json

Treat a single existing ecc@ecc installation as a reconfiguration. Do not interpret Claude's provider-owned "Open home page" control as installation evidence. Stop and report the recovery returned by setup for multiple ECC scopes, a legacy/manual install, malformed settings, or a marketplace collision; never guess which state to delete.

2. Collect exactly two choices

Ask exactly one scope question and require one value:

  • user | project | local
  • user is global for this user.
  • project is shared through repository settings.
  • local is private to the current project.

Visually mark only the selected scope as selected or installing. If the user chooses a different scope from a single existing install, describe it as a scope migration and include --move-scope in the commands below.

Ask exactly one hook-mode question and require one value:

  • off | minimal | standard | strict
  • off keeps skills and commands but disables ECC hook automation.
  • minimal enables the lightest lifecycle and safety automation.
  • standard balances quality and safety automation.
  • strict enables the strongest checks and reminders.

Hook preference is personal Claude plugin configuration; it does not follow the selected install scope.

3. Preview and confirm once

Prefer the plugin-bundled setup script. Substitute the two selected values and include --move-scope only for a scope migration:

bash
node "$CLAUDE_PLUGIN_ROOT/scripts/setup.js" --mode claude-plugin \
  --scope <scope> --hooks <hooks> [--move-scope] --dry-run --json

If $CLAUDE_PLUGIN_ROOT is unavailable, use the published npm package:

bash
npx --yes --package ecc-universal ecc setup --mode claude-plugin \
  --scope <scope> --hooks <hooks> [--move-scope] --dry-run --json

Show exactly one confirmation summary containing the planned action, one scope, one hook mode, marketplace action, and any source-to-destination migration. Ask one yes/no question. Do not run a bare interactive ecc setup through a harness shell tool because that shell is commonly non-TTY.

4. Apply the explicit choices

After confirmation, rerun the same route without --dry-run. Keep every choice explicit and request JSON so success can be checked deterministically:

bash
node "$CLAUDE_PLUGIN_ROOT/scripts/setup.js" --mode claude-plugin \
  --scope <scope> --hooks <hooks> [--move-scope] --yes --json

Fallback:

bash
npx --yes --package ecc-universal ecc setup --mode claude-plugin \
  --scope <scope> --hooks <hooks> [--move-scope] --yes --json
Show full SKILL.md (378 more words)Show less
5. Verify, then render the welcome

Require a zero exit status and a setup result whose scope and hooks equal the selected values. Then independently run:

bash
claude plugin list --json

Continue only when exactly one enabled ecc@ecc entry exists at the selected scope. When $CLAUDE_PLUGIN_ROOT is available, pass the successful setup action (installed, updated, migrated, resumed, or already-migrated) to the bundled renderer:

Before invoking it, require the provider-reported version to match ECC_VERSION_PATTERN from scripts/lib/terminal-welcome.js. Reject unexpected version text instead of interpolating it into a shell command.

bash
node -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + "/scripts/lib/terminal-welcome"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' "<action>" "<installed-version>"

Render the welcome exactly once. On failure, dry-run, cancellation, a scope or hook mismatch, or unverifiable state, do not render it; report the error and recovery instead. After verified changes, tell the user to run /reload-plugins or restart Claude Code.

Codex: use the native plugin lifecycle

Inventory with codex plugin marketplace list --json and codex plugin list --available --json. Codex's native plugin command has no Claude-style user | project | local selector. Codex native plugins do support provider-specific hooks, but Codex requires explicit trust for them. Let Codex show that trust decision; do not ask the Claude four-profile hook question or claim those profiles map to Codex.

If the ECC marketplace is missing, add it. Otherwise refresh its snapshot:

bash
codex plugin marketplace add affaan-m/ECC
codex plugin marketplace upgrade ecc --json

Ask for one confirmation, then install or idempotently refresh the installed cache and verify it:

bash
codex plugin add ecc@ecc --json
codex plugin list --json

Continue only when the JSON reports ECC installed and provides its installedPath. Then render the verified bundle's welcome:

Use only the exact absolute installedPath returned by Codex JSON. Reject control characters and require the installed version to match ECC_VERSION_PATTERN. Invoke node directly with this argument array; this is a tool API invocation, not a shell command:

text
["<installedPath>/scripts/welcome.js", "--action", "configured", "--version", "<installed-version>"]

If the current harness cannot invoke an executable with a separate argument array, skip the welcome. Never construct a shell command from Codex JSON values.

Never claim that Claude's off | minimal | standard | strict profiles were applied to Codex.

Kimi: install the project surface

State the capability summary before confirmation: destination ./.kimi-code; hooks=unsupported for ECC lifecycle hooks. Do not ask the Claude scope or hook-mode questions. Preview first:

bash
npx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run

Show one confirmation for that project destination, then apply the identical command without --dry-run. Verify with:

bash
npx --yes --package ecc-universal ecc doctor --target kimi

Only after doctor succeeds and the installed instructions and skills remain inside ./.kimi-code, render:

bash
npx --yes --package ecc-universal ecc welcome --action configured

Do not claim that Kimi installed or configured ECC lifecycle hooks.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/configure-ecc of affaan-m/ECC.

Open the folder on GitHubat commit 4eb71d9

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 9, 2026.

Compare with similar skills

Configure Ecc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Configure Ecc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Configure Ecc this skillaffaan-m/ECC276k1 repos~2kAutomated safety check: PassMIT
CCS Task Delegationkaitranntt/ccs2.9k—~1.8kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT
Kimi WebbridgeMoonshotAI/kimi-code7.8k—~3.6kAutomated safety check: PassMIT
Open Kimi Pptjinwyp/open-ppt-skill1612 repos~5.1kAutomated safety check: PassMIT
Helmor Bump Vendorsdohooo/helmor1.3k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • CCS Task Delegation

    kaitranntt/ccs

    Hands simple, deterministic tasks such as typo fixes, tests and small refactors to cheaper models through the ccs CLI, choosing a profile from your config.

    2.9k GitHub stars~1.8k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed

  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Kimi Webbridge

    MoonshotAI/kimi-code

    Kimi Browser Extension（Kimi 浏览器扩展，原 Kimi WebBridge）lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login…

    7.8k GitHub stars~3.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Open Kimi Ppt

    jinwyp/open-ppt-skill

    Create, edit, replicate, read, and export presentations. An agent skill from jinwyp/open-ppt-skill.

    161 GitHub starsUsed in 2 repos~5.1k tokens
    Documents & OfficeAuto-check passed

  • Helmor Bump Vendors

    dohooo/helmor

    Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…

    1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Gen Changesets

    MoonshotAI/kimi-code

    A skill your agent uses when generating changesets in the kimi-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.

    7.8k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from affaan-m/ECC

All 683 skills in this repo

  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    276k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed

  • VideoDB Video Search and Editing

    affaan-m/ECC

    Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    276k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes

  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    276k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    276k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    276k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Skill Compliance Checker

    affaan-m/ECC

    Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    276k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed

Works with

Questions about Configure Ecc

What does Configure Ecc do?

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's…. Configure Ecc is an agent skill from affaan-m/ECC.kimi-code, then preview, apply, and verify.

When should I use Configure Ecc?

Configure Ecc fits situations like: repairing an ECC installation; changing hook profiles; moving ECC between install scopes.

How do I install Configure Ecc in Claude Code?

Run `npx skills add affaan-m/ECC --skill configure-ecc -a claude-code`. Or copy the skill folder (skills/configure-ecc in affaan-m/ECC) into .claude/skills/configure-ecc in your project. Claude Code loads it when a task matches its description.

How do I install Configure Ecc in Codex?

Run `npx skills add affaan-m/ECC --skill configure-ecc -a codex`. Or copy the skill folder (skills/configure-ecc in affaan-m/ECC) into .agents/skills/configure-ecc in your project. Codex loads it when a task matches its description.

Can I use Configure Ecc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill configure-ecc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configure-ecc, .gemini/skills/configure-ecc, .github/skills/configure-ecc and .opencode/skills/configure-ecc in your project.

What does Configure Ecc need to run?

Going by SKILL.md and its folder, Configure Ecc needs the command-line tools its instructions call (npx, codex, claude and node). Our summary lists: Node.js.

Does Configure Ecc access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Configure Ecc safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Configure Ecc use?

Configure Ecc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Configure Ecc use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Configure Ecc?

Skills that share tags, products or a category with Configure Ecc: CCS Task Delegation (kaitranntt/ccs, 2.9k stars), Ccmanager Config (kbwo/ccmanager, 1.3k stars), Kimi Webbridge (MoonshotAI/kimi-code, 7.8k stars) and Open Kimi Ppt (jinwyp/open-ppt-skill, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Configure Ecc?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,111 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 10, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.