全エージェント(家老・足軽1-7・軍師)の稼働状態を一覧表示するスキル。tmux pane状態(稼働中/待機中/不在)とタスクYAML状態(task_id, status)と未読inbox数を統合表示。「稼働確認」「エージェント状態」「布陣確認」「agent status」で起動。
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly specifies what it does (unified display of agent operational status combining tmux pane state, task YAML state, and unread inbox counts), names the specific agents involved, and explicitly lists trigger phrases in both Japanese and English. The description is concise yet comprehensive, with strong distinctiveness due to its highly specific domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: displays all agents' operational status, integrates tmux pane state (running/standby/absent), task YAML state (task_id, status), and unread inbox count into a unified display. | 3 / 3 |
Completeness | Clearly answers both 'what' (displays all agents' status integrating tmux pane state, task YAML state, and unread inbox count) and 'when' (explicitly lists trigger phrases: '稼働確認', 'エージェント状態', '布陣確認', 'agent status'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms in both Japanese and English that users would actually say: '稼働確認', 'エージェント状態', '布陣確認', 'agent status'. These cover multiple natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: monitoring a specific multi-agent system (家老・足軽1-7・軍師) via tmux panes and task YAML. The domain-specific terminology and explicit trigger terms make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that clearly defines a single action (running a status script) and provides excellent interpretive guidance for the output. The state combination table is particularly valuable as domain-specific knowledge. The only minor weakness is the lack of references to supporting materials or the script itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what tmux is, what YAML is, or how bash scripts work. Every section earns its place—the status interpretation table is genuinely useful domain-specific knowledge Claude wouldn't have. | 3 / 3 |
Actionability | The core action is a single executable command (`bash scripts/agent_status.sh`), which is concrete and copy-paste ready. The output interpretation table provides specific, actionable guidance for each state combination. | 3 / 3 |
Workflow Clarity | This is a single-command skill (read-only status check) with no multi-step process or destructive operations. The workflow is unambiguous: run the script, read the output. The state interpretation section serves as a clear decision guide for what to do next. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but there are no references to the underlying script or further documentation. For a simple skill this is mostly fine, but a link to the script source or a troubleshooting guide (e.g., what to do when Pane=不在) would improve navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
bb19915
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.