Set up or configure Claude Code for a project or machine — scaffold CLAUDE.md, wire up settings.json (permissions, env, hooks), add MCP servers, configure the status line, and create personal or project skills. Use when the user wants to set up, configure, initialize, or onboard Claude Code, or asks how to add hooks, permissions, MCP servers, or skills.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Help the user set up or configure Claude Code. Work incrementally: confirm scope, inspect what already exists, make the smallest change, then explain it. Route to the specialized skills below whenever one fits — this skill is the entry point that ties them together.
Ask (or infer from the request) whether the change is:
.claude/ in the repo, committed and shared with the team (.claude/settings.json, .mcp.json, CLAUDE.md, .claude/skills/).~/.claude/, applies to every project on this machine (~/.claude/settings.json, ~/.claude/skills/)..claude/settings.local.json for machine-specific project settings that must not be committed.CLAUDE.md) — run the built-in /init to scaffold codebase docs, or edit an existing CLAUDE.md. Keep it tight: build/test commands, conventions, and gotchas — not everything.settings.json) — permissions, env vars, model, hooks. Prefer the update-config skill; it knows the schema and file precedence.fewer-permission-prompts skill mines your transcripts for good allowlist candidates.settings.json and are executed by the harness, not by Claude — so they're the right tool for durable automation. Configure via update-config..mcp.json (project) or user config; each server needs a command/URL and any auth.statusline-setup agent to configure statusLine in ~/.claude/settings.json.~/.claude/skills/<name>/SKILL.md; project skills in .claude/skills/<name>/SKILL.md. Each is a folder with a SKILL.md whose frontmatter has name + description. Use the skill-creator skill to author, test, and optimize new ones.keybindings-help skill to edit ~/.claude/keybindings.json.settings.json, CLAUDE.md, and .mcp.json so you extend rather than clobber.settings.local.json or environment variables and tell the user.Interactive terminal panels (/permissions, /config, /agents, /hooks) may not be available in every client — when they aren't, edit the underlying files directly instead of telling the user to run those commands.
BigSimmo/PsychSift
0d5a97a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.