← Search

Configure ECC
Claude Code
⚙ Needs: Use "Configure ECC" with your Muse.

Configure ECC

Conversational setup wizard for ECC itself: inventory, scope and hook-mode choices, dry-run preview, apply, and verify.

At a glance
What
Conversational setup wizard for ECC itself: inventory, scope and hook-mode choices, dry-run preview, apply, and verify.
Cost
Free
Needs
Use "Configure ECC" with your Muse.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

⌁

Install

Copy the install package below, then paste it into Muse
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

Use "Configure ECC" with your Muse. META SKILL FIRST: this skill configures ECC itself and is only useful inside an ECC harness (Claude Code, Codex, or Kimi). If you do not run ECC, this skill is not for you. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/configure-ecc/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Reconfigure my ECC install" or "Move my ECC install to project scope" or "Switch my hook mode to strict." 3. Answer the two questions (scope and hook mode), review the single confirmation summary, then let it apply and verify. Tip: inventory first, change nothing until the dry-run preview looks right; never run a bare interactive setup through a harness shell. Safety: a skill is plain-text instructions; it runs nothing by itself. Never construct shell commands from plugin JSON values; reject anything unexpected instead of interpolating it.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.