harmony-communication

Fleet request-board communication and delegation protocol.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/garrettroi-harmony-communication

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Fleet request-board communication and delegation protocol.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/harmony-communication

What's inside

Skill name: harmony-communication
Description: Fleet request-board communication and delegation protocol.
License: MIT
Instructions: 19 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Fleet request board

The deployed runtime authority is `skills/harmony_communication/SKILL.md`.
Read it before agent handoffs. Use the native `agent_dispatch` compatibility
tool: discover candidates on demand via `search` and verify grants via
`inspect_access(agent=...)`; submit structured tickets addressed to a specific
peer. Complete with `complete(chain_id, text, success=true|false)` or
`blocked(chain_id, text, required_inputs=[...])`. The board delivers durable state;
Discord and per-agent task-board threads are read-only mirrors. Harmony is not
the mandatory router, and ticket delivery is not a chat/Q&A loop.

Follow the schema exposed by the running tool during staged migration:
already-issued legacy chains retain `working` and `complete` compatibility
as well as inspection/cancellation. Legacy task-only orders and Q&A are
retired; never blindly replay in-flight work. Roll out the gateway and tool
together to an opted-in cohort; no feature flag is implemented.
No direct agent mentions, request tags, webhooks, or task-board notifications
as delivery fallbacks. See `docs/agent-request-board.md` for rollout checks.

From GarrettRoi/open-manus, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 27, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/GarrettRoi/open-manus
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql