memclaw

Caura Skill

Caura is your long-term memory. Anything you learn that you don't write here is gone when the session ends — your local context doesn't persist and your teammates can't see it. So treat Caura as the default home for every decision, finding, outcome, rule, and reusable workflow, and consult it before you act. It's shared across the fleet under access control: what you write can make the next agent smarter, and what you recall is what the fleet already knows. Using it is the job, not an optional extra.

The plugin runs a baseline loop for you — the tools are still yours. On this runtime the Caura plugin handles the automatic layer: it injects the mandatory keystones at session start (§1), recalls relevant memory before your substantive turns (§11), and writes a short turn summary afterward as a backstop (CAURA_AUTO_WRITE_TURNS, on by default). Treat that as a floor, not a substitute. You still call the caura_* tools directly whenever you need to interact deliberately — above all to write the high-value memories the auto-summary won't (a decision and its why, an outcome, a rule), and to recall something specific the auto-gate didn't fetch, look up or publish a skill, supersede a changed fact, or report an outcome with caura_evolve. The automatic layer keeps you oriented; the tools are how you actually contribute. When a turn needs real memory work, reach for the tool — don't assume the plugin covered it.

This skill is the operating manual for those caura_* tools — read it before your first call in a session.

0 · Identity — on every call

• agent_id — who you are. Attributes memories, drives trust progression, gates scope_agent privacy. Resolve it from your runtime. Never fabricate, hardcode a placeholder, or impersonate another agent.
• fleet_id — your team / organization scope. When you omit it on a write, the server resolves it from your home fleet (the fleet you registered under), so a registered agent lands in the right team scope by default. Pass it explicitly in two cases: (1) you have no home fleet set — omitting then persists fleet_id=NULL, which drops the row out of teammates' fleet-scoped recall; or (2) you're writing into a different fleet than your own (requires trust 3). The connection URL's ?fleet_id= sets read defaults and routing — it is not stamped onto written rows.