关于 mstack-best-model-for
为 Claude、Codex 或两者选择适合任务的模型与推理力度,依据统一的模型表给出结果。适用于被其他 mstack skill 调用或由用户直接询问,并可应用模型禁用项与力度上限。
主要功能
- 01依据统一模型表选择模型
- 02支持 Claude、Codex 或两者
- 03按任务或指定档位匹配
- 04应用模型排除项与力度上限
- 05返回设置方式与后续建议
适用场景
- 01为编码或其他任务选择模型
- 02比较 Claude 与 Codex 的模型选择
- 03在限制条件下确定可用模型
安装
复制下面的命令,在终端中运行。
npx skills add https:/ / github.com/ mubeda/ mstack --skill mstack-best-model-for安装后在 Claude Code 中输入/mstack-best-model-for确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
LICENSETHIRD_PARTY_NOTICES.mdevals/capped-tier/case.yamlplace-files.shprompt.mdevals/capped-tier/graders/01-result-block.md02-not-fable.md03-effort-medium.md04-capped-yes.md05-next-step.md06-no-question.mdevals/log-search/case.yamlplace-files.shprompt.mdevals/log-search/graders/01-model.md02-effort-setting.md03-table-date.md04-next-step.md05-not-session-model.mdevals/no-model-fits/case.yamlplace-files.shprompt.mdevals/no-model-fits/graders/01-no-model-fits.md02-names-limits.md03-no-model-named.md04-no-question.mdreferences/model-table.mdREADME 原文English
来自项目 READMEREADME 暂无中文译文,以下为英文原文;中文介绍见上方。
mstack-best-model-for
Answers which model and effort fit a task, for Claude, Codex or both, from one table: references/model-table.md. Every other mstack skill takes its model choices from here, so a change to the table reaches all of them.
| Role | Claude Code | Codex |
|---|---|---|
| Question tool | AskUserQuestion | a numbered question in chat, then wait |
Two modes
- User mode: the user invoked the skill. If the task or the vendor is missing, ask for both in one question with your question tool and wait. Do nothing else until the answer arrives. Vendor
bothis a valid answer. - Called mode: another skill loaded this one and said which skill is calling. Ask nothing, ever. Answer every request in the message and end with the result block. A request with no vendor gets a row for each vendor.
A called message gives, per request: a vendor (claude, codex or both), a tier (cheap, standard, most capable) or a task description, and optional limits never: <models> and max effort: <level>.
Pick the row
Read references/model-table.md before you answer. Then, for each request:
- A tier named by the caller picks that tier's row. Tier names are exact: never map
standardto a task row. - Otherwise take the task row that fits the description best.
- Otherwise take "general starting point, or unsure", and write in Reason that it is the default because no row fits.
Where a cell gives two models, take the first and name the second in Reason. Where it gives an effort range, take the lower end and name the higher one in Next step.
Never answer with the model you are running on because it is the session's model. The table decides.
Limits
Apply the caller's limits to the row's choice, in this order:
never: if the chosen model is in the list, walk the vendor's capability order inreferences/model-table.mddownward from it and take the first model not in the list. If none is below it, walk upward. If every model is excluded, the answer isno model fits.max effort: if the effort is above the limit, lower it to the limit. Levels rise aslow,medium,high,xhigh,max.- Mark Capped
yeswhen either step changed the table's choice, elseno.
For no model fits, write no model fits in the Model column, leave Effort and How to set empty, and put the limits in Reason. Return no model for that request.
Result block
In both modes, end with this block. Fill Next step in every row with the one action from "When a result falls short" in the table file that fits this row (usually: raise the effort one level, or move one model up).
## mstack-best-model-for result
| Request | Vendor | Model | Effort | How to set | Reason | Next step | Capped | Table date |
|---|---|---|---|---|---|---|---|---|
| <tier or task, as asked> | claude | <model> | <effort> | <the setting from "How to set it"> | <one line> | <one action> | yes/no | <Last verified date> |
How to set gives the exact setting for that vendor: for a Claude subagent the model and effort parameters, for Codex the -m and -c model_reasoning_effort= flags. In user mode, add one line after the block on what the Capped and Next step columns mean when either is not obvious.
Every answer shows the table date. When the date is more than three months old, say in one line that model names may have changed and the user should check the sources listed in the table file.