How this skill is triggered — by the user, by Claude, or both
Slash command
/helixlab:setupThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<essential_principles>
<essential_principles> The setup skill checks that HelixLab's system dependencies are installed and guides the user through installation if anything is missing. It also detects the user's AI coding agent and provides tailored integration instructions.
Core dependencies (required for vision-replay): ffmpeg, ffprobe, bc Optional dependencies (required for record-browser): Node.js 22+, Chrome for Testing
This skill is idempotent — safe to run at any time. </essential_principles>
Step 1: Run the setup script
Check what flags the user passed (available as $ARGUMENTS):
--check was passed, run in check-only modebash ${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh $ARGUMENTS
Step 2: Interpret results
Review the script output:
install-browser.shStep 3: Verify with tests
After installation (or if all deps were already present), confirm everything works:
bash ${CLAUDE_PLUGIN_ROOT}/tests/test-scripts.sh --check-ffmpeg
Step 4: Report status
Summarize for the user:
/plugin → Marketplaces tab → select the helixlab marketplace → Enable auto-update (third-party marketplaces have auto-update disabled by default)npx claudepluginhub mrrobertkent/helixlab-plugin --plugin helixlabInitializes and repairs Harness project configuration: CLAUDE.md, Plans.md, hooks, sync, CI/CD, Codex CLI, memory setup, agent config, and mirror sync.
Prepares local development environment for Claude Code usage: detects OS, installs Git and GitHub CLI, and guides through optional installation phases for design and development workflows.
First-run configuration of Citadel harness on a new project: installs hooks, detects stack, writes harness.json, scaffolds .planning/, and runs a live demo. Supports three modes from guided (tour) to fully automated express.