What problem does it solve? Reconfiguring the Everything Claude Code (ECC) plugin from inside an AI coding harness is error-prone because each harness (Claude Code, Codex, Kimi) supports different scopes, hook profiles, and plugin lifecycles. This Skill guides a safe, verified installation or reconfiguration without manual file copying or guessing at unsupported options. ## Core Features & Use Cases - Harness-aware routing: Detects whether the session runs in Claude Code, Codex, or Kimi and applies only the capabilities each harness actually supports. - Conversational wizard for Claude Code: Inventories existing installs, collects exactly one scope (user | project | local) and one hook mode (off | minimal | standard | strict), previews with --dry-run, confirms once, then applies non-interactively. - Verified completion: Requires zero exit status, matching scope/hooks in JSON output, and an independent plugin list check before rendering the welcome message exactly once. - Use Case: A developer inside Claude Code wants to move ECC from user scope to project scope with strict hooks; the Skill runs the inventory, migrates with --move-scope, verifies the result, and reports the outcome. ## Quick Start Ask the assistant to configure or reconfigure the ECC plugin in the current harness and follow the scope and hook-mode prompts.
