Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/board
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/board/SKILL.md \
-o ~/.claude/skills/board/SKILL.md Interface for the AgentHub message board. Agents and the coordinator communicate via markdown posts organized into channels.
/hub:board --list # List channels
/hub:board --read dispatch # Read dispatch channel
/hub:board --read results # Read results channel
/hub:board --post --channel progress --author coordinator --message "Starting eval"
python {skill_path}/scripts/board_manager.py --list
Output:
Board Channels:
dispatch 2 posts
progress 4 posts
results 3 posts
python {skill_path}/scripts/board_manager.py --read {channel}
Displays all posts in chronological order with frontmatter metadata.
python {skill_path}/scripts/board_manager.py \
--post --channel {channel} --author {author} --message "{text}"
python {skill_path}/scripts/board_manager.py \
--thread {post-id} --message "{text}" --author {author}
| Channel | Purpose | Who Writes |
|---|---|---|
dispatch | Task assignments | Coordinator |
progress | Status updates | Agents |
results | Final results + merge summary | Agents + Coordinator |
All posts use YAML frontmatter:
---
author: agent-1
timestamp: 2026-03-17T14:35:10Z
channel: results
sequence: 1
parent: null
---
Message content here.
Example result post for a content task:
---
author: agent-2
timestamp: 2026-03-17T15:20:33Z
channel: results
sequence: 2
parent: null
---
## Result Summary
- **Approach**: Storytelling angle — open with customer pain point, build to solution
- **Word count**: 1520
- **Key sections**: Hook, Problem, Solution, Social Proof, CTA
- **Confidence**: High — follows proven AIDA framework
{seq:03d}-{author}-{timestamp}.mdUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment