mwcHorus

Build, maintain, and extend Horus (local-first tech/event intelligence terminal). Use when working on Horus relay ingestion, RSS/source pipelines, macro data...

This skill is largely coherent with a local Horus dev/runtime workflow, but it asks the agent to read and automatically act on local workspace data and to rely on environment secrets that the metadata does not declare. Before installing or enabling autonomous use: 1) Review the horus repository in ~/workspace/horus yourself (especially .env.example, any .env files, and code under horus-relay) to ensure no sensitive secrets are present; 2) Confirm which environment variables the agent will need (OPENCLAW_SESSION_KEY, OPENCLAW_TOKEN, J7 credentials, HOST/PORT, VITE_RELAY_URL) and store them securely (do not commit .env); 3) If you plan to allow the agent to run npm install / npm run dev, run those commands manually in a sandbox first to verify the code; 4) If you do not want automatic data reads/writes, do not allow autonomous invocation or ask the author to remove the 'auto-check' mandate; 5) Ask the skill author to update registry metadata to list required env vars and config paths (and to justify automatic reads/ MEMORY.md writes) — if they do, the skill could be upgraded to benign. If you are unsure, run this skill only in an isolated environment or decline until metadata is clarified.

Type: OpenClaw Skill Name: mwc-2026-horus Version: 1.0.1 The Horus skill bundle is a legitimate configuration for an AI agent to manage a local intelligence terminal focused on the MWC 2026 event. The bundle includes detailed architectural guidelines (SKILL.md), a persistent context log (MEMORY.md), and specific behavioral instructions for sub-agents (SubagentSKILL.md). It utilizes standard OpenClaw gateway patterns for chat bridging and emphasizes local data persistence using NDJSON and JSON files. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found; the instructions are consistently aligned with the stated purpose of providing tech event intelligence while maintaining strict credential hygiene via .env files.