全エージェント(家老・足軽1-7・軍師)の稼働状態を一覧表示するスキル。tmux pane状態(稼働中/待機中/不在)とタスクYAML状態(task_id, status)と未読inbox数を統合表示。「稼働確認」「エージェント状態」「布陣確認」「agent status」で起動。
94
92%
Does it follow best practices?
Impact
Pending
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 count), names the specific agents involved, and provides explicit trigger terms in both Japanese and English. The description is concise yet comprehensive, with strong distinctiveness due to its unique domain-specific terminology.
| 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 unique domain terminology and specific trigger terms make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise skill that clearly defines when to use it, what to run, and how to interpret results. The status interpretation matrix is particularly valuable for decision-making. The main weakness is the lack of example output or error handling guidance for the delegated script.
Suggestions
Add a brief example of the expected output format so Claude knows what to expect and can detect if the script is broken or missing.
Add a one-line fallback instruction for when `scripts/agent_status.sh` doesn't exist or fails (e.g., 'If script not found, check tmux list-panes manually').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what tmux is or how YAML works. The status interpretation table is dense and useful, not padded. The skill assumes Claude's competence throughout. | 3 / 3 |
Actionability | The core action is a single concrete command (`bash scripts/agent_status.sh`), which is copy-paste ready. However, the skill delegates entirely to an external script with no fallback, no example output shown, and no guidance on what to do if the script fails or is missing. | 2 / 3 |
Workflow Clarity | This is a single-action skill (run one command, read output). The workflow is unambiguous: run the script, then interpret the output using the provided table. The status interpretation section serves as a decision matrix for next steps, which is effectively a validation/triage checkpoint. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single purpose, the content is well-organized into clear sections (overview, when to use, instructions, output interpretation, status interpretation) without needing external references. Navigation is straightforward. | 3 / 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.
3dafe0a
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.