shogun-model-switch
エージェントのCLI/モデルをライブ切替するスキル。settings.yaml更新→/exit→新CLI起動→ pane metadata更新を一発で実行。Thinking有無も制御。 「モデル切替」「Sonnetにして」「Opusに変えて」「足軽全員切替」「Thinking切って」で起動。
84
82%
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 strong skill description that concisely communicates a specific, well-defined capability: live-switching agent CLI models through a multi-step automated pipeline. It excels at providing natural trigger terms in Japanese that users would actually say, and clearly delineates both what the skill does and when it should be activated. The description is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: settings.yaml更新, /exit, 新CLI起動, pane metadata更新, and Thinking有無制御. These are clearly defined steps in a pipeline. | 3 / 3 |
Completeness | Clearly answers both 'what' (live-switch agent CLI/model via settings.yaml update, exit, restart, pane metadata update, thinking control) and 'when' (explicit trigger phrases like 「モデル切替」「Sonnetにして」etc.). The trigger guidance is explicit. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 「モデル切替」「Sonnetにして」「Opusに変えて」「足軽全員切替」「Thinking切って」. These cover model switching, specific model names, bulk switching, and thinking toggle — all natural user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche of live-switching CLI agent models with tmux pane metadata updates and settings.yaml manipulation. The trigger terms reference specific model names (Sonnet, Opus) and domain-specific concepts (足軽, pane metadata) making conflicts unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete executable commands covering all switching scenarios. Its main weaknesses are the inclusion of internal implementation details that inflate the document without aiding execution, and the lack of explicit verification steps after performing the switch operation. The structure is reasonable but could benefit from moving internals to a referenced file.
Suggestions
Add a verification step after each switch operation, e.g., 'Verify: check tmux pane metadata with `tmux display -p -t ashigaru3 "#{@model_name}"` to confirm the switch succeeded'
Move the 'What switch_cli.sh Does (internal)' section to a separate INTERNALS.md or inline it as a collapsed/reference section, keeping SKILL.md focused on how to use the skill rather than how the script works internally
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code blocks, but includes some sections that could be tightened—the Architecture ASCII diagram and the 'What switch_cli.sh Does (internal)' section explain internals that Claude doesn't need spelled out in this much detail for execution. The Display Name Mapping table is useful reference though. | 2 / 3 |
Actionability | Provides fully executable bash commands for every scenario: single switch, bulk switch, thinking control, and inbox-based switching. Commands are copy-paste ready with concrete agent IDs, model names, and flags. The settings.yaml snippet is also directly usable. | 3 / 3 |
Workflow Clarity | The Thinking control section has a clear 3-step sequence, and the internal steps of switch_cli.sh are well-documented. However, there's no explicit validation/verification step after switching—no 'confirm the new CLI is running' or 'check pane metadata reflects the change' checkpoint, which matters for a potentially destructive operation (data loss warning is mentioned in constraints). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a Files table referencing external scripts, but the 'What switch_cli.sh Does (internal)' section is detailed implementation info that could live in a separate reference file. The Architecture diagram also adds bulk that could be externalized. No bundle files are provided to verify references. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- yohey-w/multi-agent-shogun
- Commit
4ee1377
- Reviewed
Table of Contents
Is this your skill?
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.