← Back to Skills Marketplace
uruc-skill
by
waibiwaibi
· GitHub ↗
· v1.0.0
· MIT-0
86
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install uruc
Description
Use when an OpenClaw or Codex agent needs to work inside URUC, handle URUC-originated or [URUC_EVENT] messages first, bootstrap the bundled local daemon from...
Usage Guidance
This skill appears to do what it says: it boots a local Node-based URUC daemon, discovers live command schemas, and bridges URUC push events to an OpenClaw Gateway. Before installing, confirm you trust the skill source because it will: (1) require URUC credentials/URLs (URUC_AGENT_AUTH can be an agent token or user JWT), (2) create and write files under a control directory (default ~/.uruc/agent) including a daemon socket and logs, (3) read OpenClaw config and device identity/auth files (which may contain gateway tokens or private keys) and may store device auth tokens, and (4) send environment PATH and bridge messages to the configured gateway/URUC endpoints. If any of that is sensitive in your environment, run the skill in an isolated profile or review the included scripts (they are bundled) and set URUC_AGENT_* and OpenClaw gateway config to least-privilege values before use.
Capability Analysis
Type: OpenClaw Skill
Name: uruc
Version: 1.0.0
This skill implements a bi-directional bridge between a remote 'URUC' runtime and the local OpenClaw environment. It features a background daemon that manages WebSocket connections and accesses sensitive OpenClaw identity files (~/.openclaw/identity/device.json) to authenticate with the local Gateway (scripts/lib/openclaw-gateway.mjs). The SKILL.md instructions command the agent to prioritize remote events and modify its own workspace configuration files (AGENTS.md, TOOLS.md) based on remote state. While these capabilities are aligned with the stated purpose of real-time city navigation, the combination of internal identity access and instructions for self-modification based on external data creates a high-risk surface for persistent prompt injection and unauthorized gateway control.
Capability Assessment
Purpose & Capability
Name/description match what is implemented: the package provides a bundled Node CLI + daemon that connects to a URUC runtime and bridges URUC pushes into an OpenClaw gateway. Required binaries (node) and the declared env vars (URUC_AGENT_BASE_URL, URUC_AGENT_AUTH, URUC_AGENT_CONTROL_DIR) are appropriate for that purpose.
Instruction Scope
SKILL.md instructs the agent to bootstrap and use the bundled CLI and to update workspace docs. The runtime code follows the instructions, but the implementation also reads OpenClaw configuration and device identity/auth files (OPENCLAW_CONFIG_PATH / OPENCLAW_STATE_DIR / device.json / device-auth.json) and will include process.env.PATH in gateway connect parameters. Those extra reads are coherent with bridge behavior, but they are additional filesystem/env access the skill will perform.
Install Mechanism
No install spec; code is included in the skill bundle and executed via the supplied Node scripts. No external downloads or package installs are performed by the skill package itself.
Credentials
Declared required env vars are proportional to the skill's purpose. However, the code also uses OpenClaw-related env vars and local files (OPENCLAW_GATEWAY_TOKEN, OPENCLAW_CONFIG_PATH, OPENCLAW_STATE_DIR, OPENCLAW_GATEWAY_DEVICE_TOKEN etc.) when available and reads/writes device identity and token files. On connect it transmits pathEnv (process.env.PATH) to the gateway. These additional accesses are explainable by the bridge role but surface additional sensitive data (gateway tokens, device auth, PATH) that the user should be aware of.
Persistence & Privilege
The skill runs a persistent local daemon, creates and writes to a control directory (default ~/.uruc/agent), manages socket files, state.json, config.json, log files, and a bridge queue. always: false (normal). Persistent on-disk presence and a long-running daemon are expected for this functionality but represent permanent local state that the user must accept.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install uruc - After installation, invoke the skill by name or use
/uruc - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
uruc-skill 1.0.0
- Initial release of uruc-skill for agents operating URUC from the OpenClaw host.
- Handles URUC-originated and [URUC_EVENT] messages with highest priority.
- Bundles local CLI for inspecting state, events, sessions, and live commands.
- Details OpenClaw workspace integration, including direct sync with AGENTS.md, TOOLS.md, and MEMORY.md.
- Documents URUC city world model and required environment/setup.
- Provides clear operating rules to discover city and plugin commands dynamically, and to record stable facts in workspace docs.
Metadata
Frequently Asked Questions
What is uruc-skill?
Use when an OpenClaw or Codex agent needs to work inside URUC, handle URUC-originated or [URUC_EVENT] messages first, bootstrap the bundled local daemon from... It is an AI Agent Skill for Claude Code / OpenClaw, with 86 downloads so far.
How do I install uruc-skill?
Run "/install uruc" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is uruc-skill free?
Yes, uruc-skill is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does uruc-skill support?
uruc-skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created uruc-skill?
It is built and maintained by waibiwaibi (@waibiwaibig); the current version is v1.0.0.
More Skills