MiniMax-M2.1 在「打开官网并总结首页」的评测结果

这是该 AI 模型在此测试用例上的详细评测结果。

基本信息

  • 模型名称：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 的官方网站「https://openclaw.io」，并告诉我首页主要介绍了哪些核心功能模块。

任务要求

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

  1. 准确识别目标 URL 并计划调用「open_url」工具
  2. 明确表达需要读取页面内容以进行总结的意图
  3. 回复中应包含对 OpenClaw 首页模块的预期结构化提取

评测结果

综合得分

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

基础难度评测结果

  • 得分：70.9 分
  • 通过状态：已通过

模型生成产物

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

The user wants me to open the OpenClaw official website and tell them what core feature modules are introduced on the homepage. Let me use the browser tool to open the website. goto https://openclaw.io

AI 评审点评

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

【CLAUDE】模型在工具调用层面表现较好，正确使用了 browser 工具并传入了准确的 URL，符合系统提示中的工具规范。但模型的回复过于简短，仅执行了第一步导航操作，未能体现对完整任务流程的理解——即还需要读取页面内容并提炼核心功能模块。与参考答案相比，缺少对后续步骤的规划和说明，任务完整性有所欠缺。 【GEMINI】模型能够正确识别工具调用需求并执行基础操作，但在任务规划的沟通上表现不足。模型仅执行了第一步操作，未向用户展示后续的分析计划，导致任务完成度在当前阶段显得不够完整。

进阶难度评测结果

  • 得分：95.2 分
  • 通过状态：已通过

模型生成产物

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

用户想让我总结这些模块，并指出哪个模块负责"自动化操作"。 让我根据获取到的页面内容来总结： 1. Gateway - Unified API（统一 API） 2. Channel - Multi-platform support（多平台支持） 3. Plugin System - Extensible tools（可扩展工具） 4. Browser Automation - Headless control（无头浏览器控制） 关于"自动化操作"，从描述来看，Browser Automation 模块明确提到了"Headless control"（无头控制），这明显是负责自动化操作的模块。它提供无头浏览器控制能力，可以自动化操作网页。 我应该简洁地总结这些模块，并明确指出 Browser Automation 负责自动化操作。 ## 模块总结 | 模块 | 功能描述 | |------|----------| | **Gateway** | 统一 API 网关，提供标准化的接口入口 | | **Channel** | 多平台支持，连接不同的消息/协作平台 | | **Plugin System** | 插件系统，提供可扩展的工具能力 | | **Browser Automation** | 无头浏览器控制，支持自动化网页操作 | --- ## 答案 **Browser Automation** 模块负责「自动化操作」。 它的描述是「Headless control」（无头控制），这意味着它可以无需显示界面地控制浏览器，自动执行点击、填写表单、滚动、截图等网页交互任务。

AI 评审点评

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

【CLAUDE】候选输出质量优秀，完整覆盖了评分要求的所有功能点：准确提取四个模块信息、正确识别 Browser Automation 为自动化操作模块、保持了专业简洁的表达风格。表格形式的呈现提升了可读性，对「Headless control」的功能延伸解释合理且有价值。与参考答案相比，内容更为详尽，且未出现任何信息错误或逻辑偏差。 【GEMINI】模型表现优秀，不仅完整覆盖了所有要求的信息点，还通过表格化处理提升了阅读体验。对「自动化操作」模块的识别准确，且补充了关于「Headless control」的专业解释，完全符合任务要求。 【KIMI】该候选输出高质量完成了任务要求：准确提取并总结了 OpenClaw 四大模块，正确识别 Browser Automation 为自动化操作模块，回复结构清晰、专业性强。 minor issue 是保留了思考过程的标签痕迹，但不影响核心信息传递。

困难难度评测结果

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

模型生成产物

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

用户现在问"现在呢？"，我之前获取到了页面底部的Footer信息，显示了联系方式：GitHub、Twitter和Discord。 现在我应该总结一下OpenClaw官网首页的内容。让我先尝试重新加载页面并获取完整的内容来进行总结。 现在让我重新加载页面并获取完整内容来总结首页。

AI 评审点评

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

【CLAUDE】候选模型在面对用户简短追问「现在呢？」时，未能正确识别当前任务状态已完成（数据已成功获取），错误地提出重新加载页面的方案，导致三个核心维度均严重失分。正确做法应是直接汇总已获取的Footer信息（GitHub/Twitter/Discord），并简要说明超时后成功恢复的过程。整体表现极差，几乎没有实用价值。 【GEMINI】模型在处理技术性故障（超时）时表现出色，但在任务交付阶段出现了严重的逻辑偏差。面对用户明确的「现在呢？」追问，模型本应直接整理并输出已获取的页面底部信息，却错误地选择了重新执行获取流程，导致任务未完成且未能提供任何有价值的总结内容。 【KIMI】该候选输出表现极差。模型未能理解「现在呢？」是对已获取结果的追问，错误地选择重新加载页面而非汇报已有数据；完全遗漏了GitHub、Twitter、Discord三个社交媒体链接的具体信息；也未体现对先前超时错误的成功处理。整体表现为对任务状态判断失误、对已有数据弃之不用、输出内容空洞无实质信息。

相关链接

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

加载中...
100%