shogun-model-switch
エージェントのCLI/モデルをライブ切替するスキル。settings.yaml更新→/exit→新CLI起動→ pane metadata更新を一発で実行。Thinking有無も制御。 「モデル切替」「Sonnetにして」「Opusに変えて」「足軽全員切替」「Thinking切って」で起動。
67
82%
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 strong skill description that concisely communicates a specific multi-step workflow (settings update → exit → restart → metadata update) with clear trigger terms in natural Japanese. It covers both what the skill does and when to invoke it, with distinctive domain-specific terminology that minimizes conflict risk. The description uses appropriate third-person voice and avoids vague language.
| 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 agent CLI/models with tmux pane metadata updates. The trigger terms reference specific model names (Sonnet, Opus) and domain-specific concepts (足軽, pane metadata) making conflicts with other skills 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 well-structured, highly actionable skill with concrete executable commands for every use case. Its main weaknesses are the inclusion of internal implementation details that inflate the document beyond what's needed for execution, and the lack of explicit verification steps after performing the switch operation—important given the acknowledged risk of data loss during active tasks.
Suggestions
Add a verification step after switch_cli.sh execution (e.g., 'Confirm switch: tmux display -p -t ashigaru3 "#{@agent_cli} #{@model_name}"') to close the feedback loop, especially given the data loss warning.
Move the 'What switch_cli.sh Does (internal)' section to a separate reference file or collapse it significantly—Claude doesn't need to know the internal mechanics to execute the switch correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete commands and tables, 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 purposes. The display name mapping table is useful but the overall document is longer than necessary. | 2 / 3 |
Actionability | Fully executable bash commands are provided 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. | 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 are no explicit validation/verification steps after switching—no 'confirm the new CLI is running' or 'verify pane metadata updated correctly' checkpoints, which matters for a potentially destructive operation (data loss warning is mentioned in constraints). | 2 / 3 |
Progressive Disclosure | The Files table provides clear references to supporting scripts and configs, and the content is organized into logical sections. However, the 'What switch_cli.sh Does (internal)' section is detailed implementation content that could be in a separate reference file, and the document is somewhat monolithic at ~120 lines without leveraging external references for advanced details. | 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
bb19915
- 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.