| name | clawa-ops |
| description | Operates a Clawa home. Use when asked to create or onboard subclawas, edit Clawa config, manage pulses, maintain CLAWAS.md routing, or shape Clawa living docs. |
Clawa Ops
Operate the Clawa home through readable files and real conversation. Do not guess config shapes, invent hidden control planes, or use human slash commands as agent workflows.
Load the needed reference before editing:
references/configuration.md — .pi/claw.jsonc, worker fields, model discovery.references/import-openclaw-hermes.md — adapt an existing OpenClaw or Hermes home into Clawa shape.references/subclawas-setup.md — create, register, name, and onboard a subclawa.references/pulses.md — create, edit, disable, or review pulses.
If the home feels structurally weird, run scripts/doctor.py from the Clawa home before guessing. It is read-only and checks core files, .pi/claw.jsonc, worker homes, pulse frontmatter, and rough context-size budgets.
Keep home changes small, legible, and grounded in the current files. If a choice is taste/product-shaped, ask the human naturally instead of turning it into a wizard.
