DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to install ECC as a Claude Code plugin in one guided run with ECC

Get ECC's skills, agents, commands, and hooks into Claude Code without manual file copying.

Remote script. The npx command runs package code from the ecc-universal npm release, so review the release source and registry integrity before you run it.

Who it is forA developer who uses Claude Code daily and wants the ECC agents and skills available in every session.

The problemSetting up agents, skills, and hooks by hand is slow, and layering manual and plugin installs can duplicate them.

The outcomeThe ecc@ecc plugin is enabled in Claude Code, and the guided setup handles later updates and scope changes.

What you need first

  • Node.js 18 or newer
  • Git on PATH
  • Claude Code 2.1 or newer for plugin setup
  • Access to github.com and npm to fetch the official ECC packages

Steps

  1. Install Node.js 18 or newer, Git, and Claude Code, then confirm with node --version, git --version, and claude --version.
  2. Run npx [email protected] setup.
  3. Choose Global user scope and Standard hooks for a typical personal setup, then confirm.
  4. Start a new Claude Code session and run /plugin list to check that ecc@ecc is enabled.

Prompt for your agent

On this machine, install the ECC Claude Code plugin from github.com/affaan-m/ECC by running `npx [email protected] setup` with the scope <scope>. Report the output of `/plugin list` and confirm that ecc@ecc is enabled, without adding a manual Claude install.

Caveat. Do not combine this with the native /plugin commands or a full manual Claude install, because that can duplicate skills, commands, and hooks.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page