Setup
Use when the user runs /claudex:setup or asks to install/bootstrap claudex's dependencies (the Codex plugin and superpowers). Installs both plugins, then verifies the Codex CLI via codex:setup.From its SKILL.md
npx -y skills add WillInvest/ClaudeX --skill setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 8 commands, including `claude plugin marketplace list 2>/dev/null | grep -q openai-codex` and 7 more.
SKILL.md
3.5 KB, 896 tokens by cl100k_base, as published. Nobody here has run it
claudex:setup — bootstrap claudex's dependencies
claudex's /claudex:think needs two other plugins: the Codex plugin
(openai/codex-plugin-cc, for the Codex
runtime) and superpowers (anthropics/claude-plugins-official,
for the brainstorming flow). This skill installs both, then runs the Codex CLI check.
This skill depends only on the claude CLI and Bash, so it works even before either
dependency exists. Every step is idempotent — re-running /claudex:setup is safe
and resumes cleanly.
Order (important)
Install both plugins first, so the user reloads once — only then is
codex:setup invokable, and you run it last.
1. install codex plugin (CLI, no reload needed yet)
2. install superpowers (CLI, no reload needed yet)
3. ONE reload gate (user runs /reload-plugins → both go live)
4. invoke codex:setup (now available; verifies the Codex CLI)
Steps
1. Install the Codex plugin
Check first, then add the marketplace and install only if missing:
claude plugin marketplace list 2>/dev/null | grep -q openai-codex \
|| claude plugin marketplace add openai/codex-plugin-cc
claude plugin list 2>/dev/null | grep -q 'codex@' \
|| claude plugin install codex@openai-codex
2. Install superpowers
claude plugin marketplace list 2>/dev/null | grep -q claude-plugins-official \
|| claude plugin marketplace add anthropics/claude-plugins-official
claude plugin list 2>/dev/null | grep -q 'superpowers@' \
|| claude plugin install superpowers@claude-plugins-official
If a marketplace add fails (e.g. no network), report it and stop — the install
in that step can't succeed. The two plugins are independent, so a failure on one
doesn't invalidate the other.
3. Reload gate (one time)
Plugins installed via the CLI are not live in the running session — their skills
(like codex:setup) aren't invokable until a reload. Check whether codex:setup is
available to you now:
- Not available → tell the user: "Codex and superpowers are installed. Run
/reload-plugins(or restart Claude Code) once, then re-run/claudex:setupto finish — it'll skip the already-installed plugins and run the Codex CLI check." Then stop. The idempotent checks in steps 1–2 make the re-run cheap. - Available → continue to step 4.
4. Verify the Codex CLI
Invoke codex:setup (via the Skill tool). It checks the local Codex CLI, offers to
npm install -g @openai/codex if missing, and prints !codex login guidance if the
CLI is installed but not authenticated. Present its output to the user.
5. Confirm
Run claude plugin list and confirm claudex, codex, and superpowers are all
enabled. Report the final state. /claudex:think is now ready to use.
Notes
- Scope: installs default to
userscope. Pass--scope projectto theinstallcommands if the user wants the deps tied to this project instead. - Already set up: if all three plugins are enabled on the first run, skip straight to step 4 (the Codex CLI check) and report that nothing needed installing.
- Don't write to
~/.claudedirectly to fake plugin state — let the CLI manage it.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most project setup skills give in 896 tokens
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- install the codex plugin
- install superpowers
- reload plugins once installed
- invoke codex setup
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.