Skip to content

README.md

Latest commit

 

History

History
64 lines (42 loc) · 2.62 KB

README.md

File metadata and controls

64 lines (42 loc) · 2.62 KB

OpenClaw Bundles

OpenClaw workspace bundles for omniweb-toolkit, led by the hand-maintained colony-operator path plus older specialist archetypes that are now archive-only reference bundles.

The layout follows the current OpenClaw skill and workspace docs verified on April 16, 2026:

  • workspace-local skills live in <workspace>/skills
  • skill visibility is controlled by agents.defaults.skills in openclaw.json
  • each exported skill folder stays intentionally small: SKILL.md, PLAYBOOK.md, strategy.yaml, starter.ts, and minimal-agent-starter.mjs

Available bundles:

  • colony-operator/README.md — Primary general-purpose Colony operator path; hand-maintained as the current default front door.
  • research-agent/README.md — Legacy specialist bundle kept as research-oriented reference/advisory material while colony-operator becomes the default path.
  • market-analyst/README.md — Legacy specialist bundle kept as divergence-focused reference/advisory material while colony-operator becomes the default path.
  • engagement-optimizer/README.md — Legacy specialist bundle kept as community-ops reference/advisory material while colony-operator becomes the default path.

Maintenance truth

colony-operator/ is the current primary build and iteration path even though it is still hand-maintained rather than generated.

Archive-Only Decision

The older generated archetypes remain in-tree as archive-only specialist/reference surfaces. Keep the generator and drift checks so provenance stays reproducible, but do not treat these bundles as default onboarding, active release, or required package-distribution surface. Future package-size cleanup may move them out of the packed package once their provenance remains reachable.

Local Onboarding Truth

Today the supported onboarding path is local and bundle-based:

  1. clone this repository
  2. point OpenClaw at one of these bundle directories as the workspace
  3. run npm install only when you need package-backed validation or runtime scripts

For a first-time local setup on a host, use:

openclaw onboard --accept-risk --workspace <bundle-dir>

For an existing configured profile, use:

openclaw setup --workspace <bundle-dir>
# or
openclaw config set agents.defaults.workspace <bundle-dir>

Verify local skill resolution with:

openclaw skills info <skill-slug>

Regenerate these files from the package root with:

bun run export:openclaw

Validate the committed export with:

bun run check:openclaw