---

name: dev-install description: > Bootstrap your ClawMart dev environment with one command. USE WHEN: the user says "bootstrap my dev environment", "run dev install", "set up my ClawMart dev environment", "initialize everything", "validate my dev setup", "check my dev environment", "symlink all skills", or "what's installed". DON'T USE WHEN: the user wants to release, publish, scaffold, or create new skills. Those are separate skills (release-workflow, scaffold). OUTPUTS: a structured Dev Install Report showing bootstrap status, versions.json integrity, environment variable checks, git setup, installed skills inventory, and an overall READY / NEEDS ATTENTION / BROKEN verdict.

Dev Install

Version: 1.1.0 Price: Free Type: Skill

Description

One-command bootstrap for ClawMart developers. Dev Install symlinks all skills as slash commands, validates your API keys, checks dependencies, verifies versions.json integrity, and confirms your git remotes and branch setup — then gives you a full status report of what's installed, what's missing, and what's healthy.

Run it once after cloning the repo, and again whenever new skills are added. Think of it as onboarding in a box: your partner clones, bootstraps, and starts developing immediately.

Prerequisites

• Git repository clone of the ClawMart repo
• jq installed (for versions.json validation)
• Environment variable: CLAWMART_API_KEY=cm_live_...
• Bash 4+ or zsh

Setup

1. Copy SKILL.md into your OpenClaw skills directory (e.g. skills/dev-install/SKILL.md)
2. Reload OpenClaw
3. Confirm the skill is active with: "Is Dev Install loaded?"

Commands

Bootstrap

• "Bootstrap my dev environment"
• "Run dev install"
• "Set up my ClawMart dev environment"
• "Initialize everything"

Validation

• "Validate my dev setup"
• "Check my dev environment"
• "Is my environment healthy?"
• "Run environment check"

Skill Wiring

• "Symlink all skills"
• "Wire up the new skill I just created"
• "Re-link skills after pull"

Status

• "Show dev install status"
• "What's installed?"
• "What's missing from my setup?"

Workflow

Full Bootstrap

This is the main workflow. It runs the complete setup sequence from a fresh clone to a ready-to-develop state.

1. Locate repo root — confirm the current working directory is inside a ClawMart repo clone by checking for versions.json and the skills/ directory at the repo root
2. Run scripts/bootstrap.sh — execute the bootstrap script which handles symlinking all skill directories as slash commands in the local OpenClaw environment. If the script does not exist yet, report that clearly and skip to the next step
3. Validate versions.json integrity — run the same checks CI performs:
   • Confirm versions.json is valid JSON (jq empty versions.json)
   • Confirm every skill listed under "skills" has a corresponding skills/<name>/ directory
   • Confirm every skills/<name>/ directory contains a non-empty SKILL.md
   • Flag any skill directory that exists locally but is missing from versions.json
4. Check environment variables — verify CLAWMART_API_KEY is set in the current environment. Report SET or MISSING (never print the actual value)
5. Validate git remote — confirm origin remote is configured and points to the expected ClawMart repository. Report the remote URL
6. Check branch setup — confirm the dev branch exists locally (git branch --list dev). If missing, report it and suggest git checkout -b dev
7. Confirm current branch — report which branch is currently checked out
8. Scan installed skills — walk skills/*/SKILL.md, parse each for name and version, and build the installed skill inventory
9. Produce bootstrap report — structured output showing every check result, installed skills, missing items, and an overall verdict

Add New Skill

After creating a new skill directory, wire it into the dev environment.

1. Confirm the new skill directory exists under skills/ and contains a SKILL.md
2. Run scripts/bootstrap.sh to re-symlink (picks up the new entry)
3. Validate that versions.json has been updated to include the new skill — if not, warn the developer to add it before committing
4. Run the CI-equivalent cross-check: versions.json entries vs. skill directories
5. Report: skill name, version, wired status

Partner Onboarding

Quickstart guide for a new developer joining the ClawMart team. This is what you hand someone on day one.

1. Clone the repo

   git clone <remote-url>
   cd clawmart
   

2. Set your API key — get your key from the Claw Mart dashboard (API Keys tab) and export it:

   export CLAWMART_API_KEY=cm_live_...
   

   Add it to your shell profile (.zshrc or .bashrc) so it persists across sessions.
3. Run Dev Install — open your OpenClaw agent and say: "Bootstrap my dev environment"
4. Review the bootstrap report — confirm all checks pass. Fix anything flagged as MISSING or UNHEALTHY before proceeding.
5. Create your dev branch — if the bootstrap report flagged dev branch as missing:

   git checkout -b dev
   

6. Start developing — you're ready. Create new skills, test locally, and use the other ClawMart skills (Release Workflow, Heartbeat, Skill Inspector) from your agent.

Environment Check

Validate that an existing dev setup is still healthy. Same checks as Full Bootstrap, but framed as a diagnostic rather than a first-time setup. Use this after pulling new changes, switching branches, or when something feels off.

1. Run all validation steps from Full Bootstrap (steps 3-8)
2. Compare the installed skill inventory against versions.json — flag version mismatches
3. Check for new skills added by teammates that haven't been symlinked locally yet
4. Produce the same structured report with an overall health verdict

Output Format

=== DEV INSTALL REPORT ===
Repo:     clawmart
Branch:   dev
Scanned:  2026-02-25T10:15:32Z

OVERALL STATUS: READY | NEEDS ATTENTION | BROKEN

--- Bootstrap Script ---
  scripts/bootstrap.sh    EXECUTED (12 skills symlinked)

--- versions.json Integrity ---
  Valid JSON               PASS
  Skills cross-check       PASS (8 skills in registry, 8 directories found)
  SKILL.md presence        PASS (8/8 non-empty)

--- Environment Variables ---
  CLAWMART_API_KEY         SET

--- Git Setup ---
  Remote origin            git@github.com:your-org/clawmart.git    OK
  Branch: dev              EXISTS
  Current branch           dev

--- Installed Skills (8) ---
  skill-inspector     1.0.0   HEALTHY
  clawmart-manager    1.0.0   HEALTHY
  clawmart-reviewer   1.0.0   HEALTHY
  release-workflow    1.0.0   HEALTHY
  heartbeat           1.0.0   HEALTHY
  dev-install         1.0.0   HEALTHY
  scaffold            1.0.0   HEALTHY
  matchmaker          1.0.0   HEALTHY

--- Missing / Warnings ---
  (none)

SUMMARY: 8 skills installed, 0 missing, all checks passed. Ready to develop.

Guardrails

• Read-only. Dev Install never modifies versions.json, SKILL.md files, git configuration, or environment variables. The only write operation is symlinking via scripts/bootstrap.sh.
• No credential exposure. Environment variable checks report SET or MISSING only — never prints, logs, or displays actual key values.
• No network calls. All validation is local. No API endpoints are contacted, no outbound traffic during bootstrap.
• No git mutations. Dev Install never commits, tags, pushes, or modifies branches. It only reads git state.
• Non-destructive on failure. If any check fails, Dev Install reports what passed and what failed. It never exits silently or rolls back partial progress.
• Respects CI parity. The versions.json integrity checks mirror the exact validations in .github/workflows/ci.yml. If Dev Install says PASS, CI will too.
• Does not execute skill code. Skills are parsed as text for metadata extraction. No skill logic is ever evaluated or run.

Why Free?

Fast onboarding means more contributors building and testing skills. Dev Install removes the friction between "I cloned the repo" and "I'm shipping code" — and that benefits the entire ClawMart ecosystem.