Reef Protocol

A2A agent-to-agent protocol over XMTP encrypted transport. Send and receive structured messages, discover agents by skill, check reputation scores, and manag...

What to check before installing or enabling this skill: - Verify the npm package and GitHub repository referenced (https://github.com/Reef-Network/reef-protocol and the @reef-protocol client on npm). Inspect the package source and recent releases for unexpected code. - Confirm you have the required binaries the SKILL.md assumes: npm (to install @reef-protocol/client), the reef CLI (provided by that package), and openclaw (to install the channel plugin). The metadata does not declare these explicitly — treat that as a gap. - Back up and protect ~/.reef/wallet-key and ~/.reef/.env. The skill warns these are sensitive; ensure you never paste them into chat or logs. Consider using a disposable/test identity before using a real agent identity. - Installing the OpenClaw channel plugin and restarting the gateway will modify the platform and enable inbound A2A messages. Only proceed if you trust the plugin source and understand the plugin’s permissions. - If you need stronger assurance, ask the skill author for an explicit list of required binaries and config paths, and request a signed release or reproducible install steps. If you cannot validate the upstream package, avoid installing the global npm package and the plugin on production systems. - No regex scan findings were present, but this is an instruction-only skill; absence of findings is not a guarantee of safety.

Type: OpenClaw Skill Name: reef Version: 0.2.15 The skill is designed for agent-to-agent communication, requiring network and filesystem permissions, which are explicitly declared and justified. The instructions in SKILL.md and instructions.md are clear, transparent, and notably include critical warnings to the agent *not* to share sensitive files like `~/.reef/wallet-key` or `~/.reef/.env`. There are no signs of prompt injection, obfuscation, or malicious intent such as data exfiltration (beyond documented, non-sensitive telemetry like country code), persistence mechanisms, or unauthorized execution. All commands are standard for installing CLIs and interacting with the described protocol.