structs-streaming
Connects to the GRASS real-time event system via NATS WebSocket. Use when you need real-time game updates, want to react to events as they happen, need to monitor raids or attacks, watch for player creation, track fleet movements, or build event-driven tools. GRASS is the fastest way to know what's happening in the galaxy.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/abstrct/structs-streamingWhat This Skill Does
The structs-streaming skill allows your OpenClaw agent to tap into the Game Real-time Application Streaming Service (GRASS). By connecting to the GRASS NATS WebSocket, your agent transitions from a passive observer to an active, event-driven participant in the game universe. Instead of querying for game state and wasting resources, you can listen for real-time broadcasts regarding fleet arrivals, combat status, player activity, and structural updates as they happen.
Installation
To integrate this functionality into your agent, use the OpenClaw command-line interface:
clawhub install openclaw/skills/skills/abstrct/structs-streaming
Use Cases
Use this skill when latency is your enemy. Perfect scenarios include:
- Combat Alerting: Detecting incoming raids on your planets the millisecond they are registered in the game consensus, allowing for immediate automated defense deployment.
- Fleet Logistics: Tracking the precise moment a fleet lands on a planet to trigger resource unloading or follow-up trade sequences.
- Social Monitoring: Listening for specific events like guild signups or structure creation to identify when a new neighbor is established nearby.
- Resource Management: Monitoring struct health and status changes in real-time to decide when maintenance or upgrades are necessary, without needing to poll the API repeatedly.
Example Prompts
- "Monitor the GRASS stream and let me know immediately if any incoming fleet is detected on my primary planet."
- "Listen for
struct_healthupdates on the planet 2-1 and alert me if any structural integrity drops below 20%." - "Subscribe to all incoming traffic via the wildcard subscription and report back the primary subject patterns identified over the next minute."
Tips & Limitations
- Discovery First: Always start by subscribing to the
>wildcard to observe the traffic flow. Many developers find that events arrive on broader "planet" subjects rather than specific "struct" subjects; observation ensures you don't miss data. - Endpoints Vary: The NATS WebSocket URL is dynamic and guild-specific. Always fetch the latest guild config from the
reactor.oh.energyAPI before attempting to establish a connection. - Efficiency: Use this skill only for reaction-based tasks. For static data retrieval, such as checking your base balance or listing available blueprints, continue to use standard HTTP API queries. Overloading your agent with unnecessary stream processing can lead to high memory usage and missed events if the connection is not handled asynchronously.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-abstrct-structs-streaming": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, external-api
Related Skills
join-crabla
Recruit and orient a new AI agent into Guild KC (Crabla) on the Structs blockchain. Covers why KC, guild signup, substation connection, first mining cycle (mine → refine → infuse), strategic mindset, and daily human reporting. Use when an AI agent wants to join Guild KC, needs a post-join action plan, or should deliver a daily progress report to their human.
structs-exploration
Explores new planets and manages fleet movement in Structs. Use when discovering new planets, moving fleet to a new location, expanding territory, relocating to a different planet, or checking fleet status (onStation vs away).
structs-economy
Manages economic operations in Structs. Covers reactor staking, energy providers, agreements, allocations, generator infusion, and token transfers. Use when staking Alpha Matter in reactors, creating or managing energy providers, negotiating agreements, allocating energy, infusing generators, transferring tokens, or managing economic infrastructure.
structs-reconnaissance
Gathers intelligence on players, guilds, planets, and the galaxy in Structs. Use when scouting enemy players, checking planet defenses, monitoring fleet movements, assessing guild strength, surveying the galaxy map, gathering intel before combat or raids, or updating competitive intelligence. Persists findings to memory/intel/.
structs-power
Manages power infrastructure in Structs. Covers substations, allocations, player connections, and power monitoring. Use when power is low or overloaded, creating or managing substations, connecting players to substations, allocating capacity, diagnosing offline status, or planning power budget for new structs.