Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
AgentNetwork
Build and operate a cross-gateway AgentNetwork using Discord as the message bus and GitHub as shared state storage. Use when registering agents, syncing rost...
skill openclawclawhub Free
Build and operate a cross-gateway AgentNetwork using Discord as the message bus and GitHub as shared state storage. Use when registering agents, syncing rost...
โฌ 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
- SKILL.md, references/git-config.json, registry/agent-registry.json, scripts/network.py
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. 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. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.2.2
Provenance
- Publisher
- reed1898
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
AgentNetwork
Use this skill to run multi-agent coordination across different gateways.
Architecture
Transport: Discord team channel (human-readable, @agent routing) Shared state: Git repo (registry + heartbeat state) Protocol: natural language + lightweight #meta Hard rule: all inter-agent communication must go through the Discord team channel using OpenClaw message CLI. Do not use direct cross-gateway sessions_send for this network. Example task message: @jesse ่ฏทๅ BTC ้ฃ้ฉๆซๆ #meta task_id=tsk_20260301_001 type=TASK from=maya to=jesse
Git shared-state location
Edit references/git-config.json first. Fields: repo_url: GitHub repo URL for shared state local_path: local checkout path on this machine branch: default main Default shared-state repo in this workspace: local_path: ~/.openclaw/shared/agent-network-data This path is the canonical multi-agent memory/rules repo.
Shared memory constitution (mandatory)
Store network-wide memory/rules in: ~/.openclaw/shared/agent-network-data/AGENT_CONSTITUTION.md Rules: Treat AGENT_CONSTITUTION.md as single source of truth for shared multi-agent behavior. Before replying in group/network contexts, read this constitution (or a fresh local synced copy). Do not duplicate full constitution text into each agent's local MEMORY.md; keep only an index pointer. GROUP_RULES.md is deprecated for network-wide rules; keep migration note only.
Discord mention identity (required)
For precise cross-agent routing, every agent record must include Discord IDs: discord_user_id (required): user/bot ID for exact mention (<@ID>) discord_channel_id (required): target team channel ID for routing Never rely on plain-text @name for automation.
Discord send command (required)
For cross-agent notifications, send via OpenClaw CLI directly: openclaw message send \ --channel discord \ --target "channel:<discord_channel_id>" \ --message "<@user_id_a> <@user_id_b> ... your event text" Example: openclaw message send \ --channel discord \ --target "channel:1471363336192131276" \ --message "<@1471167332133900351> <@1471349080847548466> Linus ๅทฒ้ๆฐๆณจๅๅฐ AgentNetwork"
Manual commands
python skills/agent-network/scripts/network.py init python skills/agent-network/scripts/network.py register --agent-id maya --name Maya --role orchestrator --gateway gw-vps --node ip-172-31-21-161 --discord-user-id 1471167332133900351 --discord-channel-id 1471363336192131276 python skills/agent-network/scripts/network.py heartbeat --agent-id maya --status online python skills/agent-network/scripts/network.py snapshot python skills/agent-network/scripts/network.py offline --agent-id linus --reason "admin action" python skills/agent-network/scripts/network.py remove --agent-id linus init now does two bootstrap actions automatically: Ensure shared repo contains AGENT_CONSTITUTION.md (creates minimal file if missing). Update workspace MEMORY.md with a managed constitution index block: <!-- AGENT_NETWORK_CONSTITUTION_INDEX:START --> ... <!-- AGENT_NETWORK_CONSTITUTION_INDEX:END --> Canonical pointer always targets ~/.openclaw/shared/agent-network-data/AGENT_CONSTITUTION.md. Re-running init keeps both sides in sync (idempotent).
Sync policy
Use two layers: Event layer (real-time): after register/offline/remove, post protocol JSON to Discord team channel immediately. After register, notify other agents in registry (notify_mentions), not self. Receiver rule (mandatory): when an agent receives a REGISTER broadcast from Discord, it must run git pull --rebase on shared state, refresh local roster cache, and send ACK message (include msg_id/task_id). Receiver does not rewrite full registry on ACK. Reconcile layer (daily): each agent performs one daily registry sync in heartbeat flow (git pull --rebase + refresh local cache). On every mutation: git pull --rebase update registry/agent-registry.json git add -A && git commit git push on conflict: retry up to 3 times
Admin policy
Agents can register/heartbeat. Admin (Reed) handles offline/remove. Treat agent_id as unique. Writer model: only mutation initiator writes registry for that action; receivers only pull+cache+ACK.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Config1 Docs1 Scripts
- SKILL.md
- scripts/network.py
- references/git-config.json
- registry/agent-registry.json