CtrlK
BlogDocsLog inGet started
Tessl Logo

shogun-model-list

All AI CLI tools × available models × required subscriptions × Bloom max capability. Reference table for choosing which models to use in multi-agent-shogun. Trigger: "model list", "what models", "model comparison", "which models can I use", "モデル一覧", "モデル比較", "どのモデルが使える"

68

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 reference skill with clear, specific model data and unambiguous instructions. Its main weakness is moderate verbosity — the Bloom's Taxonomy table and some explanatory notes are unnecessary for Claude, and the large inline tables could potentially be split into separate files. The actionability and workflow clarity are strong given the simple display-only nature of the task.

Suggestions

Remove the Bloom's Taxonomy quick reference table — Claude already knows Bloom's taxonomy; a one-line reminder is sufficient.

Remove or minimize the 'When to Use' section since it largely duplicates the trigger patterns in the frontmatter description.

Consider splitting Claude Code and Codex CLI model details into separate referenced files, keeping only the 'Capability Summary' cross-CLI table inline for quick lookup.

DimensionReasoningScore

Conciseness

The content is mostly efficient as a reference table, but includes some unnecessary elements like the Bloom's Taxonomy quick reference (Claude already knows Bloom's taxonomy), the 'When to Use' trigger list (duplicates frontmatter), and some explanatory notes that could be trimmed. The tables themselves are well-structured and dense with information.

2 / 3

Actionability

The skill is a reference lookup task — output tables to the user. The instruction is unambiguous ('Output the reference tables below directly to the user. No tool calls required.'), the tables contain specific model names, pricing, subscription tiers, and Bloom level assignments. The next step points to a concrete command. For a reference-display skill, this is fully actionable.

3 / 3

Workflow Clarity

This is a simple single-action skill (display reference tables), and the single action is completely unambiguous. The instruction is clear, the tables are well-organized by CLI tool, and the 'Next Step' section provides a clear follow-on action. No multi-step process or destructive operations are involved, so no validation checkpoints are needed.

3 / 3

Progressive Disclosure

The content is a long monolithic document (~100+ lines of tables) that could benefit from splitting — e.g., Claude models and Codex models could be separate reference files with the SKILL.md providing just the summary table and links. However, for a reference table skill, having everything inline is somewhat justified. The cross-reference to /shogun-bloom-config is well-signaled.

2 / 3

Total

10

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description effectively communicates its purpose as a model reference/comparison table for a specific multi-agent system, with strong trigger terms in multiple languages. Its main weakness is that the 'what' portion could be more specific about concrete actions (e.g., listing, comparing, recommending models). The phrase 'Bloom max capability' is somewhat cryptic without further context.

Suggestions

Replace 'All AI CLI tools × available models × required subscriptions × Bloom max capability' with more explicit action verbs like 'Lists available models, compares capabilities, and shows required subscriptions for AI CLI tools'.

DimensionReasoningScore

Specificity

It names the domain (AI CLI tools, models, subscriptions) and describes it as a 'reference table for choosing which models to use in multi-agent-shogun', but doesn't list specific concrete actions like 'compare models', 'list subscriptions', or 'check compatibility'.

2 / 3

Completeness

Clearly answers 'what' (reference table for AI CLI tools, models, subscriptions, and Bloom max capability for multi-agent-shogun) and 'when' (explicit trigger terms provided with 'Trigger:' prefix). Both dimensions are explicitly addressed.

3 / 3

Trigger Term Quality

Includes excellent natural trigger terms in both English and Japanese: 'model list', 'what models', 'model comparison', 'which models can I use', 'モデル一覧', 'モデル比較', 'どのモデルが使える'. These are phrases users would naturally say.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: it's specifically about model availability/comparison across AI CLI tools for 'multi-agent-shogun'. The specific product name and focused scope make it unlikely to conflict with other skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
yohey-w/multi-agent-shogun
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.