brain-ops

Orchestrate OpenClaw brain read/write cycles for fixture-based testing.

Updated May 16, 2026
One-click install
npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill brain-ops-morris-utrust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-ops
Source: https://github.com/Morris-UTRUST/GBrain-knowledge/tree/main/test/fixtures/openclaw-reference-minimal/skills/brain-ops
Command: npx skills add https://github.com/Morris-UTRUST/GBrain-knowledge --skill brain-ops-morris-utrust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The brain-ops skill defines and orchestrates the core read/write cycle used by the OpenClaw reference fixture, enabling deterministic fixture-based testing of brain interactions.

Core Features & Use Cases

  • Defines triggers such as brain read/write/lookup/citation to drive deterministic tests.
  • Specifies that the fixture writes pages to people/ and companies/ to validate persistence and linking.
  • Supports end-to-end testing by exercising the brain's read/write operations against the OpenClaw fixture.

Quick Start

Run the OpenClaw reference end-to-end test to exercise the brain-ops fixture.

Frequently Asked Questions about brain-ops

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

FAQPage Schema
How do I test brain read-write cycles for fixture-based validation?

Brain read-write cycles are tested by orchestrating deterministic triggers like read, write, lookup, and citation against a reference fixture, validating data persistence to people/ and companies/ output paths.

What is the best way to validate data integrity in OpenClaw test scenarios?

Validating data integrity in OpenClaw scenarios involves exercising brain interactions through deterministic task orchestration, ensuring that fixture writes only occur within defined writes_to paths like people/ and companies/.

Can I use fixture-based testing to exercise brain lookup and citation operations?

Yes, fixture-based testing defines triggers for brain read, write, lookup, and citation operations, allowing you to exercise these interactions end-to-end against the OpenClaw reference fixture.

Does brain-ops require external dependencies to run end-to-end tests?

No, brain-ops operates with zero external dependencies, relying entirely on the internal OpenClaw reference fixture to drive deterministic validation and core read-write orchestration.

How do I run end-to-end tests for OpenClaw brain interactions?

You run end-to-end tests by applying the brain-ops skill to the OpenClaw reference fixture, which exercises brain interactions and writes validated output pages to people/ and companies/ directories.