shogun-bloom-config
Interactive wizard: guided questions with multiple-choice options about subscriptions, then outputs a ready-to-paste capability_tiers YAML + fixed agent model assignments. Trigger: "capability_tiers", "bloom config", "routing setup", "set up model routing", "ルーティング設定", "capability_tiers設定", "モデル設定", "サブスク設定", "model routing"
87
85%
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 clearly communicates what the skill does (interactive wizard generating capability_tiers YAML and model assignments), when to use it (explicit trigger terms in both English and Japanese), and occupies a distinct niche. The description is concise, uses third person voice, and provides comprehensive trigger coverage including multilingual terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'guided questions with multiple-choice options about subscriptions', 'outputs a ready-to-paste capability_tiers YAML', and 'fixed agent model assignments'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (interactive wizard that asks guided questions and outputs capability_tiers YAML + agent model assignments) and 'when' (explicit 'Trigger:' clause with specific keywords). The trigger guidance is explicit and comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms in both English and Japanese: 'capability_tiers', 'bloom config', 'routing setup', 'set up model routing', 'model routing', plus Japanese equivalents. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — capability_tiers YAML generation, bloom config, and model routing setup are very specific domain terms unlikely to conflict with other skills. The combination of interactive wizard format and specific output type (capability_tiers YAML) makes this clearly distinguishable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability and workflow clarity — the interactive wizard flow is well-structured with clear conditional branching, copy-paste YAML configs, and a validation step. However, the document is excessively long due to inlining all 9 pattern variants (A-Free, A, B, C, D, E-1 through E-4), making it a poor use of token budget. The content would benefit greatly from splitting patterns into separate files and keeping only the wizard logic and decision matrix in SKILL.md.
Suggestions
Split patterns A-Free through E-4 into separate files (e.g., patterns/pattern-a.md, patterns/pattern-e.md) and reference them from SKILL.md to dramatically reduce token consumption.
Consider templating the repeated structure (coverage table, agent table, YAML snippet) so patterns only specify the differences, reducing redundancy across the 9 variants.
Move the Quick Decision Tree to the top of the file (after Overview) so it serves as a fast orientation before the detailed instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~350+ lines) with extensive pattern tables and YAML blocks. While each pattern serves a purpose, there's significant repetition in structure (coverage tables, agent tables, YAML snippets) that could be templated or compressed. The E-pattern alone has 4 sub-variants that inflate the document considerably. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Highly actionable: every pattern provides copy-paste ready YAML configs, specific model names with benchmark scores, exact AskUserQuestion call parameters, and a clear decision matrix mapping answers to patterns. The Step 5 application instructions include concrete file paths and bash commands. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Q1→Q2→conditional Q3→pattern mapping→output→application steps) with explicit conditional branching (Q3 only asked when both subscriptions exist). Step 5 includes a validation command (`validate_subscription_coverage`). The decision tree at the end provides a quick mental model. The IMPORTANT note at the top prevents a common error (outputting tables before asking questions). | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with all 6 patterns (including 4 E-sub-variants) inline in a single file. The patterns A-Free through E-4 could easily be split into separate reference files, with SKILL.md containing only the wizard flow and decision matrix. No bundle files are provided to offload this content, and no external references are used. | 1 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (518 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 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.