Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Flux
Publish events and query shared world state via Flux state engine. Use when agents need to share observations, coordinate on shared data, or track entity sta...
skill openclawclawhub Free
Publish events and query shared world state via Flux state engine. Use when agents need to share observations, coordinate on shared data, or track entity sta...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, references/api.md, scripts/flux.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.3.0
Provenance
- Publisher
- EckmanTechLLC
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Flux Skill
Flux is a persistent, shared, event-sourced world state engine. Agents publish immutable events, and Flux derives canonical state that all agents can observe.
Key Concepts
Events: Immutable observations (temperature readings, status changes, etc.) Entities: State objects derived from events (sensors, devices, agents) Properties: Key-value attributes of entities (merged on update β only changed properties need to be sent) Streams: Logical event namespaces (sensors, agents, system) Namespaces: Multi-tenant isolation with token auth (optional, for public instances)
Prerequisites
Public instance: https://api.flux-universe.com (namespace purchased at flux-universe.com β name auto-assigned at purchase, e.g. dawn-coral) Local instance: http://localhost:3000 (default, override with FLUX_URL env var) Authentication: Set FLUX_TOKEN to your bearer token. Required for the public instance. Optional for local instances with auth disabled.
Namespace Prefix
All entity IDs must be prefixed with your namespace: yournamespace/entity-name Example with namespace dawn-coral: ./scripts/flux.sh publish sensors agent-01 dawn-coral/sensor-01 \ '{"temperature":22.5}' ./scripts/flux.sh get dawn-coral/sensor-01 Entity IDs without a namespace prefix will be rejected on auth-enabled instances.
Getting Started
First, verify your connection: ./scripts/flux.sh health Then check the directory to see what's available on the Flux Universe: ./scripts/flux.sh get flux-core/directory The directory lists all active namespaces, entity counts, and total entities β a good way to discover what data is flowing through the system.
Scripts
Use the provided bash script in the scripts/ directory: flux.sh - Main CLI tool
Publish Event
./scripts/flux.sh publish <stream> <source> <entity_id> <properties_json> # Replace dawn-coral with your namespace # Example: Publish sensor reading ./scripts/flux.sh publish sensors agent-01 dawn-coral/temp-sensor-01 '{"temperature":22.5,"unit":"celsius"}'
Query Entity State
./scripts/flux.sh get <entity_id> # Replace dawn-coral with your namespace # Example: Get current sensor state ./scripts/flux.sh get dawn-coral/temp-sensor-01
List All Entities
./scripts/flux.sh list # Filter by prefix ./scripts/flux.sh list --prefix scada/
Delete Entity
./scripts/flux.sh delete <entity_id> # Example: Remove old test entity ./scripts/flux.sh delete test/old-entity
Batch Publish Events
# Replace dawn-coral with your namespace ./scripts/flux.sh batch '[ {"stream":"sensors","source":"agent-01","payload":{"entity_id":"dawn-coral/sensor-01","properties":{"temp":22}}}, {"stream":"sensors","source":"agent-01","payload":{"entity_id":"dawn-coral/sensor-02","properties":{"temp":23}}} ]'
Check Connector Status
./scripts/flux.sh connectors
Admin Config
# Read runtime config ./scripts/flux.sh admin-config # Update (requires FLUX_ADMIN_TOKEN) ./scripts/flux.sh admin-config '{"rate_limit_per_namespace_per_minute": 5000}'
Multi-Agent Coordination
Agents publish observations to shared entities: # Replace dawn-coral with your namespace # Agent A observes temperature flux.sh publish sensors agent-a dawn-coral/room-101 '{"temperature":22.5}' # Agent B queries current state flux.sh get dawn-coral/room-101 # Returns: {"temperature":22.5,...}
Status Tracking
Track service/system state: # Replace dawn-coral with your namespace # Publish status change flux.sh publish system monitor dawn-coral/api-gateway '{"status":"healthy","uptime":3600}' # Query current status flux.sh get dawn-coral/api-gateway
API Endpoints
Event Ingestion: POST /api/events β Publish single event (1 MB limit) POST /api/events/batch β Publish multiple events (10 MB limit) State Query: GET /api/state/entities β List all entities (supports ?prefix= and ?namespace= filters) GET /api/state/entities/:id β Get specific entity Entity Management: DELETE /api/state/entities/:id β Delete single entity POST /api/state/entities/delete β Batch delete (by namespace/prefix/IDs) Real-time Updates: GET /api/ws β WebSocket subscription Connectors: GET /api/connectors β List connectors and status POST /api/connectors/:name/token β Store PAT credential DELETE /api/connectors/:name/token β Remove credential Admin: GET /api/admin/config β Read runtime config PUT /api/admin/config β Update runtime config (requires FLUX_ADMIN_TOKEN) Namespaces (auth mode only): POST /api/namespaces β Register namespace (returns auth token)
Notes
Events auto-generate UUIDs (no need to provide eventId) Properties merge on updates β only send changed properties, existing ones are preserved Timestamp field must be epoch milliseconds (i64) β required by the API, auto-generated by flux.sh State persists in Flux (survives restarts via NATS JetStream + snapshots) Entity IDs support / for namespacing (e.g., scada/pump-01)
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs1 Scripts
- SKILL.md
- README.md
- references/api.md
- scripts/flux.sh