← ClaudeAtlas

mxsetuplisted

This skill should be used when a developer sets up mxLore on a new PC, runs a fresh Claude Code install, updates the global mx-rules block in ~/.claude/CLAUDE.md, refreshes skills/hooks from GitHub, or reinstalls the mxMCPProxy. Triggers "neuer PC", "fresh install", "onboard me", "/mxSetup", "update mx-rules", "mx-rules block veraltet", "reinstall proxy", "skills aktualisieren".
MicrotronX/mxLore · ★ 25 · AI & Automation · score 78
Install: claude install-skill MicrotronX/mxLore
# /mxSetup — Developer Onboarding (~30 seconds) > AI-Steno: !=forbidden →=use ⚡=critical ?=ask > ⚡ **!Python !jq !sed for file operations.** Only Write/Read/Edit tools + Bash for `claude mcp` and `curl`. > ⚡ **Bash: Single-line.** !Multi-line !Heredocs !Newlines in commands. ## When to trigger this skill - `claude mcp list` returns empty or lacks `mxai-knowledge` - `mxMCPProxy.exe` missing or version mismatch vs server - mx-rules marker block in `~/.claude/CLAUDE.md` outdated or missing - New PC / fresh Claude Code install - User says "/mxSetup", "onboard me", or "neuer PC" - Skills folder out of date (upstream updates in `MicrotronX/mxLore-skills`) ## Prerequisites - **Required CLI tools:** `curl`, `unzip`, `claude` (Claude Code CLI). Git-Bash on Windows includes curl+unzip. - **Node.js** — Recommended. Required for 5 of 8 hooks (Orchestrate, Recall-Gate, Recall-Outcome). Without Node.js the session runs with limited functionality (no state tracking, no Recall-Gate). Installation: https://nodejs.org/ ## First Installation (with API key) ### Phase 1: MCP Connection 1. Check `claude mcp list` → already has `mxai-knowledge`? → "Use `--update`" 2. ?user: "Server URL? (e.g. http://localhost:8080/mcp)" - URL must end with `/mcp` 3. Register MCP: ```bash claude mcp add -s user --transport http mxai-knowledge "<SERVER-URL>" --header "Authorization: Bearer <API-KEY>" ``` 4. `mx_ping()` → Success? Note admin_port. Error? → Abort. ### Phase 2: Install Skills from GitHub (~5 s