configure-ecc

Configure ECC plugin installation, scope, and hooks across Claude Code, Codex, and Kimi harnesses.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill configure-ecc-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-ecc
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/configure-ecc
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill configure-ecc-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ecc-universal.

What problem does it solve? Installing or reconfiguring the ECC plugin differs across AI coding harnesses, and guessing at scopes, hook profiles, or install commands leads to broken or duplicated setups. This Skill runs a guided, non-interactive configuration flow that respects each harness's real capabilities. ## Core Features & Use Cases - Harness-aware routing: Detects whether you are in Claude Code, Codex, or Kimi and applies only the options that harness actually supports. - Claude Code wizard: Inventories existing installs, collects exactly one scope (user, project, local) and one hook mode (off, minimal, standard, strict), previews with a dry run, confirms once, applies, and verifies the result. - Codex and Kimi paths: Uses Codex's native plugin lifecycle with marketplace refresh, or installs the project surface under ./.kimi-code without claiming unsupported hook profiles. - Use Case: You already have ECC installed at user scope in Claude Code and want to migrate it to project scope with strict hooks. The Skill detects the existing install, plans a scope migration with --move-scope, confirms once, applies, and verifies exactly one enabled ecc@ecc entry. ## Quick Start Ask the assistant to configure or update the ECC plugin for the current harness, choosing an install scope and hook mode if you are in Claude Code.

Frequently Asked Questions about configure-ecc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the ECC plugin inside Claude Code?

Run an inventory with claude plugin list --json, then choose one scope (user, project, or local) and one hook mode (off, minimal, standard, strict). Preview with a dry run, confirm once, apply with --yes --json, and verify exactly one enabled ecc@ecc entry exists.

How do I migrate an existing ECC install to a different scope?

If a single existing ecc@ecc install is detected and you pick a different scope, the setup is treated as a scope migration. The configuration commands include the --move-scope flag so the plugin moves from the source scope to the selected destination scope.

Does ECC support hook profiles in Codex or Kimi?

No. Claude's off, minimal, standard, and strict hook profiles apply only to Claude Code. Codex uses its own native plugin trust model for hooks, and Kimi does not support ECC lifecycle hooks at all, so those questions are skipped in those harnesses.

What happens if multiple ECC installs or a broken state is detected?

The Skill stops and reports the recovery guidance returned by the setup tooling. It never guesses which installation to delete when it finds multiple scopes, legacy manual installs, malformed settings, or marketplace collisions.

Why should I not run bare interactive ecc setup inside a harness?

Harness shell tools are commonly non-TTY, so an interactive wizard cannot collect answers. The Skill instead uses explicit non-interactive commands with --scope, --hooks, --yes, and --json flags so results can be verified deterministically.