agent-board
starsforks
How to install agent-board?
rlaope/oh-my-hermes/agent-board
$npx -y skills add rlaope/oh-my-hermes --skill agent-board[omh] Hermes agent board workflow: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states.
SKILL.md
| 1 | # Agent Board |
| 2 | |
| 3 | This is a Hermes-native `agent-board` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `agent-board` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: agent-board coordinate PM, CTO, QA, and release agents on this launch checklist. |
| 20 | - Expected behavior: Produce `prepare_agent_board_card` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: agent-board mark the other agent complete without an observed heartbeat or result. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 32 | - Report which outputs are prepared, observed, blocked, or missing. |
| 33 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 38 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when multiple Hermes profiles, agents, or targets need a board-shaped status contract for collaborative work. |
| 55 | |
| 56 | Strong routing signals: `agent-board`, `agent board`, `kanban`, `multi-agent`, `multi agent`, `multi agent board`, `multiple hermes agents`, `multiple hermes profiles`, `hermes profiles`, `subagent`, `subagents`, `sub agent`, `sub agents`, `agent coordination`, `agent task board`, `task board`, `roles and board`, `role board`, `heartbeat`, `blocker`, `agent blocker`, `agent heartbeat`, `agent handoff`, `handoff board`, `interviewer reviewer builder`, `reviewer builder`, `칸반`, `멀티 에이전트`, `서브에이전트`, `서브 에이전트`, `여러 에이전트`, `Hermes agent 여러 명`, `여러 명이 같이 일`, `에이전트 보드`, `작업 배분`, `역할 배분`, `작업 보드`, `역할과 보드`, `역할 보드` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `agent-coordination` |
| 61 | Phase: `board-status` |
| 62 | Hermes role: `tracker` |
| 63 | Quality tier: `workflow-surface-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 68 | - Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence. |
| 69 | - Expose missing tools, credentials, targets, or observations as user-visible gaps. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - user request |
| 78 | - target context |
| 79 | - delivery or |
People who liked this also viewed
6 picksType
- lark-openapi-explorer飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。SkillsJul 2026
- lark-skill-maker创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill（包装原子 API 或编排多步流程）时使用。SkillsJul 2026
- azure-cost-optimizationOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
- vercel-react-native-skillsVercel's official collection of agent skillsSkillsJul 2026
- mcp-builderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate externaSkillsJul 2026
- gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.SkillsJul 2026
