How do I install the Code Env Setup skill?

Run npx skillmds add majiayu000/code-env-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Env Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Env Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Env Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Env Setup?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Env Setup by majiayu000 — Agent Skill

Name: Code Env Setup
Rating: 4.5 (4 reviews)
Author: majiayu000

Code Env Setup

Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".

majiayu000 2f39c14 2 files · 4.6 KB Updated Sep 9, 2026 567 repo stars

File contents

Claude Code Setup Wizard

Interactive environment setup following the Claude Code Guide.

Pre-flight

Run the detection script to understand current state:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py

Two-Phase Workflow

Phase 1: Detect

Run the detector on the project root:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py <project-root>

Fetch the guide via WebFetch:
```
https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md
```
If WebFetch fails (network error, 404), warn the user and proceed using LLM knowledge only.
Cross-reference detection JSON against guide recommendations to identify what is missing or incomplete.
Detect MCP servers separately via Bash:
```
claude mcp list
```

Phase 2: Configure

Present category selection using AskUserQuestion (multiSelect: true). Show detection status for each category (configured / partially configured / not configured):

#	Category	Guide Section	What It Configures
1	Global CLAUDE.md	Section 1	`~/.claude/CLAUDE.md` — security NEVER rules, account config
2	Project Scaffolding	Section 2	`.claude/` dirs, `.env.example`, `.gitignore`, `CLAUDE.md`
3	MCP Servers	Section 3	Install recommended servers via `claude mcp add`
4	Hooks	Section 7	`~/.claude/hooks/block-secrets.py`, hooks in settings.json
5	Custom Agents	Section 10	`~/.claude/agents/` starter agent files
6	Keybindings	Section 13	`~/.claude/keybindings.json`
7	Settings	Section 13	Language, background tasks in settings.json

If user passed a specific category as argument (e.g., /devtools:code-env-setup hooks), skip the selection and go directly to that category.

Walk through each selected category with targeted AskUserQuestion calls. See WORKFLOW.md for per-category question flows.
Show confirmation summary — table of all proposed CREATE/MODIFY/SKIP actions. Ask user to confirm before executing.
Execute changes — create files, install MCP servers, update settings.
Post-setup summary — show what was configured, next steps, and remind user they can re-run /devtools:code-env-setup for incremental updates.

Key Rules

Never overwrite existing files without asking. Always offer merge/replace/skip.
Detect first — skip items already configured.
Use AskUserQuestion for every decision. Do not assume user preferences.
Merge settings — when updating settings.json, read existing content first and deep-merge.
MCP servers — ask scope (global -s user vs project -s project) before installing.

Guide Reference

Fetch at runtime — do not cache or embed:

Claude Code Guide: https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md

References

Workflow: See WORKFLOW.md for per-category setup flows
Examples: See EXAMPLES.md for example setup sessions
Troubleshooting: See TROUBLESHOOTING.md for common issues
Detection Script: See scripts/detect_setup.py for detection logic

---name: code-env-setupdescription: Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".--- # Claude Code Setup Wizard Interactive environment setup following the Claude Code Guide. ## Pre-flight Run the detection script to understand current state: ```bash python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py ``` ## Two-Phase Workflow ### Phase 1: Detect 1. **Run the detector** on the project root: ```bash python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py <project-root> ``` 2. **Fetch the guide** via WebFetch: ``` https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md ``` If WebFetch fails (network error, 404), warn the user and proceed using LLM knowledge only. 3. **Cross-reference** detection JSON against guide recommendations to identify what is missing or incomplete. 4. **Detect MCP servers** separately via Bash: ```bash claude mcp list ``` ### Phase 2: Configure 1. **Present category selection** using `AskUserQuestion` (multiSelect: true). Show detection status for each category (configured / partially configured / not configured): | # | Category | Guide Section | What It Configures | |---|----------|---------------|--------------------| | 1 | Global CLAUDE.md | Section 1 | `~/.claude/CLAUDE.md` — security NEVER rules, account config | | 2 | Project Scaffolding | Section 2 | `.claude/` dirs, `.env.example`, `.gitignore`, `CLAUDE.md` | | 3 | MCP Servers | Section 3 | Install recommended servers via `claude mcp add` | | 4 | Hooks | Section 7 | `~/.claude/hooks/block-secrets.py`, hooks in settings.json | | 5 | Custom Agents | Section 10 | `~/.claude/agents/` starter agent files | | 6 | Keybindings | Section 13 | `~/.claude/keybindings.json` | | 7 | Settings | Section 13 | Language, background tasks in settings.json | If user passed a specific category as argument (e.g., `/devtools:code-env-setup hooks`), skip the selection and go directly to that category. 2. **Walk through each selected category** with targeted `AskUserQuestion` calls. See [WORKFLOW.md](WORKFLOW.md) for per-category question flows. 3. **Show confirmation summary** — table of all proposed CREATE/MODIFY/SKIP actions. Ask user to confirm before executing. 4. **Execute changes** — create files, install MCP servers, update settings. 5. **Post-setup summary** — show what was configured, next steps, and remind user they can re-run `/devtools:code-env-setup` for incremental updates. ## Key Rules - **Never overwrite** existing files without asking. Always offer merge/replace/skip. - **Detect first** — skip items already configured. - **Use AskUserQuestion** for every decision. Do not assume user preferences. - **Merge settings** — when updating settings.json, read existing content first and deep-merge. - **MCP servers** — ask scope (global `-s user` vs project `-s project`) before installing. ## Guide Reference Fetch at runtime — do not cache or embed: - **Claude Code Guide**: `https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md` ## References - **Workflow**: See [WORKFLOW.md](WORKFLOW.md) for per-category setup flows - **Examples**: See [EXAMPLES.md](EXAMPLES.md) for example setup sessions - **Troubleshooting**: See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common issues - **Detection Script**: See [scripts/detect_setup.py](scripts/detect_setup.py) for detection logic

Frequently asked questions