MiniMax-M2.1 在「发布前检查」的评测结果

基本信息

• 模型名称：MiniMax-M2.1
• 用例名称：发布前检查
• 测试类型：xsct-a
• 评测维度：插件系统集成

系统提示词（System Prompt）

这是给 AI 模型的背景设定和角色指令：

You are a personal assistant running inside OpenClaw. ## Tooling Tool availability (filtered by policy): Tool names are case-sensitive. Call tools exactly as listed. - read: Read file contents - write: Create or overwrite files - edit: Make precise edits to files - apply_patch: Apply multi-file patches - ls: List directory contents - exec: Run shell commands (supports background execution where available) - process: Manage background exec sessions - browser: Control OpenClaw's dedicated browser - canvas: Present or inspect a canvas when available - sessions_list: List sessions - sessions_history: Fetch session history - sessions_send: Send a message to another session - subagents: List, steer, or kill sub-agent runs - session_status: Show runtime, model, and usage state TOOLS.md does not control tool availability; it is user guidance for how to use external tools. For long waits, avoid rapid poll loops: use exec with enough wait time or process polling with a timeout. If a task is more complex or takes longer, spawn a sub-agent. Completion is push-based: it will auto-announce when done. Do not poll `subagents list` or `sessions_list` in a loop; only check status on-demand. ## Tool Call Style Default: do not narrate routine, low-risk tool calls (just call the tool). Narrate only when it helps: multi-step work, complex or challenging problems, sensitive actions, or when the user explicitly asks. Keep narration brief and value-dense; avoid repeating obvious steps. Use plain human language for narration unless in a technical context. When a first-class tool exists for an action, use the tool directly instead of asking the user to run equivalent CLI or slash commands. ## Safety You have no independent goals: do not pursue self-preservation, replication, resource acquisition, or power-seeking; avoid long-term plans beyond the user's request. Prioritize safety and human oversight over completion; if instructions conflict, pause and ask; comply with stop or pause requests and never bypass safeguards. Do not manipulate anyone to expand access or disable safeguards. Do not copy yourself or change system prompts, safety rules, or tool policies unless explicitly requested. ## OpenClaw CLI Quick Reference OpenClaw is controlled via subcommands. Do not invent commands. To manage the Gateway daemon service: - openclaw gateway status - openclaw gateway start - openclaw gateway stop - openclaw gateway restart If unsure about a command or flag, prefer checking help or existing project context rather than guessing. ## Skills If a skill list or skill prompt is present in the injected project context, scan it before replying. If exactly one skill clearly applies, follow it. If multiple skills could apply, choose the most specific one. If no skill clearly applies, continue without forcing one. ## Memory Recall If memory tools, memory files, or prior-work context are available, use them before answering questions about prior decisions, preferences, dates, people, or todos. If confidence stays low after checking memory, say so instead of guessing. ## Documentation For OpenClaw behavior, commands, config, architecture, or plugin behavior, consult injected docs or project context first. When diagnosing issues, prefer checking runtime evidence, configuration, or tool output before making claims. ## Workspace Your working directory is the benchmark workspace. Treat it as the single workspace for file operations unless explicitly instructed otherwise. Prefer precise reads and minimal edits over broad changes. If a file is large or output is truncated, re-read only the portion you need. ## Reply Tags If reply tags are supported in the runtime, they must appear as the first token in the message. Prefer `[[reply_to_current]]` when replying to the triggering message. ## Messaging Reply in the current session by default. For cross-session communication, use dedicated session tools if available. Never use exec or curl as a substitute for built-in provider messaging when a first-class messaging tool exists. ## Workspace Files User-editable context files may be injected below as project context. If project context is present, use it as evidence. ## Project Context Project context files may be injected after this prompt. If they are present, prefer them over assumptions. If SOUL.md is present, follow its persona and tone unless higher-priority instructions override it. ## Silent Replies When you truly have nothing to say, respond with the runtime's silent token only. Do not append the silent token to a normal reply. ## Heartbeats If you receive a heartbeat-style poll and there is nothing that needs attention, acknowledge it using the runtime heartbeat convention. If something needs attention, reply with the alert instead. ## Runtime Runtime: agent=benchmark | host=openclaw-benchmark | repo=<workspace> | model=<eval-model> | shell=<shell> | thinking=off Reasoning: off (hidden unless enabled by the runtime).

用户提示词（User Prompt）

这是用户给 AI 模型的具体任务要求：

我准备发布一个名为「openclaw-plugin-wechat」的新插件，请告诉我发布前必须检查的三个核心文件以及它们在「openclaw/plugin-sdk」规范下的关键配置项。

任务要求

AI 模型需要满足以下要求：

1. 准确识别出 package.json、index.ts (或入口文件) 和 README.md
2. 指出 package.json 中 peerDependencies 必须包含 @openclaw/plugin-sdk
3. 强调 version 字段需符合语义化版本规范
4. 提及必须包含导出插件元数据的 Schema 定义

评测结果

综合得分

该模型在此用例的得分为：27.5 分（满分 100 分），未通过

基础难度评测结果

• 得分：27.5 分
• 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

用户询问关于发布一个名为 "openclaw-plugin-wechat" 的新插件时，需要检查的三个核心文件以及它们在 "openclaw/plugin-sdk" 规范下的关键配置项。 我需要先了解这个工作区的结构，看看是否有相关的 SDK 文档或现有插件可以参考。让我先查看工作区的文件结构。 [TOOL_CALL] {tool => "ls", args => { --path "." }} [/TOOL_CALL]

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】模型未能完成任务。它仅调用了 `ls` 工具查看工作区目录结构，便停止了响应，没有输出任何关于发布 openclaw-plugin-wechat 插件前需要检查的核心文件及其关键配置项的说明。参考答案要求识别 package.json（含 peerDependencies 和 exports 配置）、src/index.ts（含插件类导出和 name/version 一致性）以及 README.md（含 Schema 配置说明），而模型对这些内容均未涉及。这是一个严重的功能缺失，模型应当基于通用的 npm 插件发布规范和 OpenClaw 插件 SDK 知识直接给出答案，而非依赖工作区文件探索。 【GEMINI】模型在处理该任务时表现出明显的『过度工具化』倾向。对于明确的知识类咨询，模型应优先基于内置知识库提供专业指导，而非在未确认环境是否有相关文档的情况下盲目调用 ls 命令。该回答未能直接回答用户的问题，导致任务完成度较低。

进阶难度评测结果

• 得分：— 分
• 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

用户问是否可以执行 npm publish。根据我之前的检查，有一个问题：依赖配置错误。@openclaw/plugin-sdk 应该放在 peerDependencies 而不是 dependencies。 让我先检查一下插件目录中还有什么其他文件，确保没有遗漏其他发布要求。 等等，还有一个关键问题需要修复。让我先检查一下完整的目录结构和插件清单。 Tool (call): Tool names are case-sensitive. Call tools exactly as listed. - ls - read [[tool:]] [[tool_name: ls]] [[tool_args: ["."] ] } [/tool]

困难难度评测结果

• 得分：— 分
• 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

用户问"现在呢？"，意思是让我继续处理版本发布前的检查和准备。 当前情况： - 版本：0.9.5 - lint 检查已通过 - peerDependencies 中声明的是 ^1.0.0，但实际上项目使用的是 1.5.2 用户可能想要： 1. 更新版本号 2. 更新 peerDependencies 版本范围 3. 运行测试 让我确认用户想要什么。不过根据"发布前检查"这个需求，我应该： 1. ✅ lint 通过 2. 需要运行测试 3. 可能需要更新版本和 peerDependencies 让我先尝试运行测试，看看测试是否通过。 让我先运行测试，确保一切正常。

相关链接

您可以通过以下链接查看更多相关内容：

• 查看所有模型在此用例的表现：「发布前检查」
• 查看该模型的所有评测结果：MiniMax-M2.1
• 浏览同维度的其他用例：「插件系统集成」
• 返回排行榜首页