How this skill is triggered — by the user, by Claude, or both
Slash command
/agenthub:boardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interface for the AgentHub message board. Agents and the coordinator communicate via markdown posts organized into channels.
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}.mdnpx claudepluginhub aneeba-pixel/claude-skills --plugin agenthubGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
3plugins reuse this skill
First indexed Jun 3, 2026