brain-ops

Persist people and company entity updates through the OpenClaw fixture's brain read/write/lookup/citation cycle.

5|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/GYF0311/lorekit --skill brain-ops-gyf0311
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-ops
Source: https://github.com/GYF0311/lorekit/tree/main/brain/test/fixtures/openclaw-reference-minimal/skills/brain-ops
Command: npx skills add https://github.com/GYF0311/lorekit --skill brain-ops-gyf0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps keep a reference fixture’s knowledge base consistent by providing a single, reliable read/write cycle for brain operations like reads, writes, lookups, and citations.

Core Features & Use Cases

  • Core brain loop: Handles the primary read/write/lookup/citation interactions required by the OpenClaw reference fixture.
  • People and company updates: Writes updates to the people/ and companies/ pages to reflect newly stored or corrected facts.
  • Use case: Use this during end-to-end tests to ensure the fixture can correctly ingest knowledge and expose it back via lookup and citation flows.

Quick Start

In your test or agent run, invoke brain-ops to perform the required brain read/write/lookup/citation operations for the OpenClaw reference fixture while persisting results to people/ and companies/.

Frequently Asked Questions about brain-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage knowledge base read and write cycles for fixture testing?

Knowledge base read and write cycles for fixture testing are managed by executing a core loop that handles reads, writes, lookups, and citations to maintain deterministic state. It persists updates directly to people and company entity pages.

What is citation-aware access in a knowledge base fixture?

Citation-aware access in a knowledge base fixture is a retrieval mechanism that ensures newly stored or corrected facts are exposed back via lookup and citation flows. It guarantees that end-to-end tests interact with consistent, referenceable entity data.

How do I persist people and company entity updates during end-to-end tests?

To persist people and company entity updates during end-to-end tests, invoke the brain read/write cycle to write changes directly to the people/ and companies/ pages. This reflects newly stored or corrected facts in the reference fixture.

Does the OpenClaw reference fixture support deterministic knowledge state updates?

Yes, the OpenClaw reference fixture supports deterministic knowledge state updates by applying a single, reliable read/write cycle for brain operations. This ensures end-to-end test scenarios correctly ingest knowledge and expose it back via lookup and citation flows.

When do I need a dedicated read/write loop for knowledge base lookups?

You need a dedicated read/write loop for knowledge base lookups when end-to-end test scenarios require deterministic fixture state updates. It handles citation-aware access and ensures people and company entity facts are consistently stored and retrievable.