engineering/agenthub/skills/board/SKILL.md
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.
npx skillsauth add alirezarezvani/claude-skills boardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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}.mddevelopment
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.