Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows configure-ecc

Configure 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.

12448 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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

When to use it

installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Configure Everything Claude Code; Route by the current harness; Claude Code: run the full conversational wizard; 1. Inventory without changing anything; 2. Collect exactly two choices; 3. Preview and confirm once.

File analysis

File analysis: besides SKILL.md, the body references scripts/setup.js, scripts/lib/terminal-welcome.js, scripts/lib/terminal-welcome, scripts/welcome.js. Those resources load on demand.

Configure Everything Claude CodeRoute by the current harnessClaude Code: run the full conversational wizard1. Inventory without changing anything2. Collect exactly two choices3. Preview and confirm once4. Apply the explicit choices5. Verify, then render the welcomeCodex: use the native plugin lifecycleKimi: install the project surface

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
  • scripts/setup.js
  • scripts/lib/terminal-welcome.js
  • scripts/lib/terminal-welcome
  • scripts/welcome.js

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "configure-ecc" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-c38746603bfdc852-Configure-Ecc.html
Save it as .cursor/skills/configure-ecc/SKILL.md or .claude/skills/configure-ecc/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/affaan-m/ecc instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/affaan-m/ecc' --list

npx skills add 'https://github.com/affaan-m/ecc' --skill 'configure-ecc'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- 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 Everything Claude Code 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 --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 --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 --hooks [--move-scope] --yes --json ``` Fallback: ```bash npx --yes --package ecc-universal ecc setup --mode claude-plugin \ --scope --hooks [--move-scope] --yes --json ``` ### 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 }));' "" "" ``` 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 ["/scripts/welcome.js", "--action", "configured", "--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.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…