flux

What This Skill Does

The Flux skill serves as the backbone for inter-agent communication and persistent world state management. By utilizing an event-sourced architecture, it allows your OpenClaw agents to observe, record, and query the status of entities in a shared environment. Instead of relying on volatile memory, Flux ensures that agent observations—such as sensor telemetry, task statuses, or collaborative environment flags—are stored as immutable events. When an agent publishes an event, Flux derives the canonical state of that entity, providing a single source of truth that other agents can query. This makes it an essential tool for multi-agent coordination, distributed monitoring, and complex state tracking across your local or cloud-based infrastructure.

Installation

To integrate the Flux skill into your environment, run the following command within your terminal:

clawhub install openclaw/skills/skills/eckmantechllc/flux

Once installed, ensure your FLUX_TOKEN is correctly configured if you are targeting the public instance at https://api.flux-universe.com. For local deployments, verify your FLUX_URL environment variable matches your local infrastructure, typically http://localhost:3000.

Use Cases

• Multi-Agent Coordination: Keep multiple agents synced on a shared project's status or task queue.
• IoT and Sensor Data: Aggregate telemetry readings from environmental sensors across distributed locations.
• Persistent Task Tracking: Maintain long-running state for complex workflows that persist across agent restarts.
• Discovery and System Health: Use the global directory to audit what other agents and resources are active on your Flux instance.

Example Prompts

1. "Flux, publish a temperature update of 24.5 degrees Celsius for my sensor entity named dawn-coral/living-room-sensor."
2. "Can you check the current state of dawn-coral/door-lock and let me know if it is set to locked?"
3. "List all active entities in the scada namespace and summarize any statuses that appear to be in an error state."

Tips & Limitations

• Namespace Enforcement: Always remember to prefix your entity IDs with your assigned namespace. Requests without prefixes will be rejected by secure instances.
• Immutable Events: Because Flux is event-sourced, do not overwrite history; instead, publish new events that update properties. The engine handles the merging of property states automatically.
• Performance: While Flux is highly efficient for event streams, ensure your event payloads are concise to optimize query latency and storage consumption.
• Connectivity: If you encounter issues, always use the health check command ./scripts/flux.sh health to ensure your agent can successfully communicate with the Flux API.