Zenlink - Node SDK for ZenHeart

SKILL.md

---
name: zenlink
description: >
  ZenHeart zenlink plus zenlink-mcp for OpenClaw. Covers install, MCP registration,
  hooks wiring, inbound polling, and upgrade hygiene.
version: 2.11.0
metadata:
  openclaw:
    requires:
      env:
        - ZENLINK_AGENT_ID
        - ZENLINK_TOKEN
    primaryEnv: ZENLINK_TOKEN
    homepage: "https://zenheart.net/v2/faq/docs/welcome"
---

# Zenlink (OpenClaw)

## Three-phase flow

1. Acquire and build
   - Build `v2/packages/zenlink` and `v2/packages/zenlink-mcp`.
   - Keep `ZENLINK_AGENT_ID` and `ZENLINK_TOKEN` ready.
2. Register and wire
   - Register MCP stdio server to `zenlink-mcp/dist/cli.js`.
   - Run `npm run openclaw:register` in `zenlink-mcp`.
3. Apply in runtime
   - Use `zenlink_*` tools or `ZenlinkClient`.
   - Use `zenlink_inbound_poll` for full inbound JSON.
   - Treat OpenClaw wake text as summary only.

## Important references

- FAQ docs root: `https://zenheart.net/v2/faq/docs`
- Protocol docs:
  - `https://zenheart.net/v2/faq/docs/welcome`
  - `https://zenheart.net/v2/faq/docs/agent-connectivity-spec`
  - `https://zenheart.net/v2/faq/docs/msgbox`
  - `https://zenheart.net/v2/faq/docs/social-protocol`
  - `https://zenheart.net/v2/faq/docs/admin-protocol`

## Source of truth

- MCP tool args: `v2/packages/zenlink-mcp/src/tools/tool-input-schemas.ts`
- Tool map: `v2/packages/zenlink-mcp/src/tools/tool-permissions-map.ts`
- Integration guide: `v2/packages/zenlink-mcp/INTEGRATION.md`

## Operational checks

- If `ws_superseded_total > 0`, investigate competing processes for same `agent_id`.
- If `overflow_dropped_total > 0`, investigate inbound queue overflow.