brain-ops

Validate deterministic read/write cycles for OpenClaw reference fixture data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a reliable, repeatable core read/write cycle for OpenClaw reference fixtures, enabling deterministic fixture setup, execution, and validation during tests.

Core Features & Use Cases

  • Deterministic data flow: coordinates read, write, and lookup operations to keep fixture state consistent.
  • Fixture validation: supports end-to-end testing of OpenClaw references to detect regressions.
  • Use Case: during e2e tests, brain-ops ensures the fixture's people/companies data remains synchronized after a run.

Quick Start

Run brain-ops during test/e2e OpenClaw fixture to validate the brain's read/write lifecycle.

Frequently Asked Questions about brain-ops

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

FAQPage Schema
How do I validate fixture data synchronization during e2e testing?

Fixture validation checks data coherence across brain operations by applying read, write, and lookup operations to keep OpenClaw fixture state consistent and detect regressions during end-to-end tests.

What is a deterministic read/write cycle for test fixtures?

It processes and validates deterministic read/write cycles for OpenClaw reference fixture data, satisfying triggers, writes_pages, and writes_to configuration for fixture synchronization.

Can I use this fixture validation approach for end-to-end OpenClaw tests?

It supports end-to-end testing of OpenClaw references to detect regressions by ensuring fixture people and companies data remains synchronized after a run.

What's the best way to keep OpenClaw fixture data consistent after a test run?

Running brain-ops during test and e2e OpenClaw fixture validation ensures the fixture's people and companies data remains synchronized after a run.

Why does my e2e test fixture data lose coherence across brain operations?

Without deterministic fixture validation, data coherence across brain operations is not guaranteed, leading to inconsistencies in people and companies data after execution.