setup
Initialize and configure the embark-claude-index plugin. Opens a web-based setup GUI where all prerequisites and configuration are managed.
Best use case
setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Initialize and configure the embark-claude-index plugin. Opens a web-based setup GUI where all prerequisites and configuration are managed.
Teams using setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How setup Compares
| Feature / Agent | setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Initialize and configure the embark-claude-index plugin. Opens a web-based setup GUI where all prerequisites and configuration are managed.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# embark-claude-index Setup First-time setup for the Unreal Engine code index plugin. **CRITICAL SHELL INFO**: Claude Code runs in **Git Bash (MINGW)** on Windows. All commands below use bash syntax. Do NOT use PowerShell (`$env:`, `Get-ChildItem`) or cmd.exe (`dir /s`) syntax. ## When to Use Trigger this skill when: - User just installed the plugin and needs to set it up - User says "setup", "configure", or "initialize" the index - User wants to reconfigure project paths or re-run setup - The MCP tools return "service not running" errors and no config exists ## Prerequisites The only hard prerequisite to launch the dashboard is **Node.js 20.18+**. Everything else (WSL, Docker, environment variables) is installed from within the dashboard GUI. **You MUST check and auto-install missing prerequisites — do NOT just tell the user to install them.** ### Check Node.js ```bash node --version 2>/dev/null || echo "NOT_INSTALLED" ``` If Node.js is missing or the version is below 20.18, **install it automatically**: ```bash powershell.exe -Command "Start-Process powershell -ArgumentList '-Command','winget install -e --id OpenJS.NodeJS.LTS --accept-source-agreements --accept-package-agreements' -Verb RunAs" -Wait ``` After installation, verify it succeeded by checking again in a fresh shell: ```bash "/c/Program Files/nodejs/node.exe" --version ``` If the install succeeded but `node` is not on PATH yet, tell the user to **restart their terminal** so the PATH update takes effect, then re-run this skill. ### Check npm ```bash npm --version 2>/dev/null || echo "NOT_INSTALLED" ``` npm ships with Node.js. If npm is missing but Node.js was just installed, the user needs to restart their terminal for PATH changes. If npm is still missing after restart, install it: ```bash "/c/Program Files/nodejs/node.exe" "/c/Program Files/nodejs/node_modules/npm/bin/npm-cli.js" --version ``` ## Setup Steps ### Step 1: Clone or update the repo ```bash if [ -d "$USERPROFILE/.claude/repos/embark-claude-index/.git" ]; then cd "$USERPROFILE/.claude/repos/embark-claude-index" && git pull --ff-only && echo "Repo updated" else git clone https://github.com/EmbarkStudios/UnrealClaudeFileHelper.git "$USERPROFILE/.claude/repos/embark-claude-index" && echo "Repo cloned" fi ``` ### Step 2: Install dependencies ```bash cd "$USERPROFILE/.claude/repos/embark-claude-index" && npm install --ignore-scripts --omit=dev ``` If `npm` is not found, use the full path: ```bash cd "$USERPROFILE/.claude/repos/embark-claude-index" && "/c/Program Files/nodejs/npm" install --ignore-scripts --omit=dev ``` ### Step 3: Launch the setup GUI ```bash cd "$USERPROFILE/.claude/repos/embark-claude-index" && node src/setup-gui.js ``` This opens a web-based dashboard at **http://localhost:3846**. ### Step 4: Tell the user to complete setup in the dashboard The dashboard handles everything else: - **Prerequisites panel**: Shows status of WSL, Docker, Node.js, and UNREAL_INDEX_DIR with one-click install buttons for each - **Workspace management**: Add workspaces, configure project paths, build Docker images, start containers and watchers - **MCP config**: Provides the config snippet to add to Claude Code settings - **Auto-start**: Optionally enable dashboard auto-start at logon Tell the user to follow the prerequisites checklist in the dashboard, then add a workspace. After setup, **restart their terminal and Claude Code** to pick up the environment variable and MCP tools.
Related Skills
VibeCollab — Setup Instructions for AI Assistants
You are helping a user set up VibeCollab in their project.
deft-directive-setup
Set up a new project with Deft Directive framework standards. Use when the user wants to bootstrap user preferences, configure a project, or generate a project specification. Walks through setup conversationally — no separate CLI needed.
setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
quick-setup
Detect project type and generate .pi/ configuration. Use when setting up pi for a new project or when user asks to initialize pi config.
memory-palace-setup
Use this skill when the user wants to install, configure, connect, or troubleshoot first-run setup for the Memory Palace project itself. Distinguish the onboarding `memory-palace-setup` skill from the main repo's canonical `memory-palace` skill; prefer skills plus MCP over MCP-only; treat this setup repo as temporary guidance that can be used by URL or direct doc reads without persistent installation; prioritize the main repo's runtime `memory-palace` skill when recommending something to install persistently; keep the existing MCP logic unchanged; route Windows to `backend/mcp_wrapper.py` and POSIX hosts to `scripts/run_memory_palace_mcp_stdio.sh`; and guide setup for Claude Code, Codex CLI, Gemini CLI, OpenCode, Cursor, Windsurf, VSCode-host, and Antigravity. Chinese trigger hints: 安装配置这个项目, 首次接通, skills+mcp, github地址, 仓库地址, 不安装也能看, 临时安装引导.
SVK-setup
SVK Setup: Guided onboarding skill that interviews users about their experience and project scope, recommends tools from a tiered catalog (MCPs, plugins, skills), walks through installation of third-party tools and SVK core skills (SOS, GL, DB, BOK), and generates a personalized reference document. The first thing a new SVK user runs. Run /SVK-setup for the full guided flow, or /SVK-setup:interview to begin.
move-setup
Move package setup (Move.toml, edition, dependencies), building, testing, and common pitfalls from other Move dialects.
setup
Run Wayfinder Paths setup - install dependencies, create wallets, configure API key
setup
Activate on first use or when user says "setup", "configure", "connect my notes", "link my drive", "how do I connect", or on first session with no prior configuration. Also reads curiosity-stack.local.md if it exists — skip steps already answered there.
Skill: setup-standalone
## Description
Skill: setup-embedded
## Description
Skill: setup-claude-sub-proxy
## Description