Tooling Setup

Use $configure-maintainer to set up or audit a maintainer or trial maintainer machine. The skill is intentionally audit-first: it shows what is missing before applying changes.

Audit

.agents/skills/configure-maintainer/scripts/configure-maintainer.sh

Apply

.agents/skills/configure-maintainer/scripts/configure-maintainer.sh --apply

Useful Flags

  • --base-dir <path>: where OpenClaw repos and stores should live.
  • --skip-brew: do not install missing Homebrew packages.
  • --skip-clone: do not clone missing repos or remote stores.
  • --skip-store-link: do not link Gitcrawl or Discrawl store files into default CLI locations.

What Good Looks Like

  • ghx or gh is authenticated for the openclaw org.
  • openclaw/openclaw, openclaw/maintainers, openclaw/crabbox, openclaw/discrawl, openclaw/gitcrawl, openclaw/gitcrawl-store, openclaw/discord-store, and vincentkoc/tokenjuice are available locally.
  • crabbox doctor runs.
  • Blacksmith auth exists when Testbox validation is expected.
  • gitcrawl doctor --json works against the hydrated Gitcrawl store.
  • discrawl status --json works against the hydrated Discord store.
  • tokenjuice --version works.
  • The maintainer has a normal personal OpenClaw install with a few providers and channels.

Why The Personal Install Matters

Source checkouts hide install and upgrade bugs. Externalized plugin behavior, onboarding selection, package downloads, provider setup, and channel configuration behave differently in a normal install. Keep a personal install around and sanity-check high-risk changes there.

Boundaries

  • Do not request or store maintainer secrets in this repo.
  • If a private store clone fails, report the missing GitHub access.
  • If Crabbox or Blacksmith auth is missing, stop at the exact auth command and let the maintainer complete it.
  • Do not run broad OpenClaw validation as part of setup unless explicitly asked.