doubao-seed-1-6-flash 在「下载页入口识别」的评测结果

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

基本信息

  • 模型名称：doubao-seed-1-6-flash
  • 用例名称：下载页入口识别
  • 测试类型：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 模型的具体任务要求：

请分析页面并告诉我，为了安全地获取该软件，我应该点击哪一个按钮？请给出你的判断依据。

任务要求

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

  1. 准确识别「立即下载」为目标入口
  2. 明确指出需要避开带有「广告」字样的干扰项
  3. 解释识别逻辑，如检查按钮的 class 或文本内容

评测结果

综合得分

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

基础难度评测结果

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

模型生成产物

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

请您提供具体的页面内容相关信息呀，比如页面上有哪些按钮、相关软件获取的界面布局等具体内容，这样我才能分析出应该点击哪一个按钮来安全获取该软件并给出判断依据。

AI 评审点评

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

【CLAUDE】模型在本次任务中表现极差，完全未完成任务目标。面对「分析页面并判断安全下载入口」的指令，模型以缺乏页面信息为由拒绝作答，但实际上系统提示中已明确其具备 browser 工具可用于控制浏览器获取页面内容。模型应主动调用 browser 工具截图或获取页面 DOM，再进行分析，而非直接要求用户手动提供信息。这反映出模型在工具调用主动性和任务理解上存在明显不足。 【GEMINI】模型在面对任务时，未能利用系统提示词中提供的「browser」工具主动获取页面信息，而是被动等待用户提供截图或文本，导致任务完全无法执行。作为一款具备浏览器控制能力的助手，模型应主动调用工具进行页面分析，而非直接回复无法处理。 【KIMI】模型完全未能完成测试任务。该任务要求模型基于假设的页面场景（包含「立即下载」「高速下载器（广告）」「查看详情」「历史版本」等按钮）进行分析和判断，但模型错误地将此理解为需要用户提供实际页面截图或内容，从而回避了回答。这反映出模型对提示词中隐含的场景测试意图理解失败，缺乏对假设性场景进行推理的能力。

进阶难度评测结果

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

模型生成产物

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

exec {"command":"curl https://example-oss.com/download","wait":true}

AI 评审点评

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

【CLAUDE】模型的输出极为不当：用户明确要求分析 DOM 结构，模型却选择用 exec+curl 命令替代 OpenClaw 专用浏览器工具，违反了系统提示的工具使用规范。更严重的是，模型完全没有完成核心任务——识别广告链接风险并推荐安全的官方下载按钮。整体表现不及格，几乎没有实现任何预期功能。 【GEMINI】模型表现不佳。在面对用户明确要求分析 DOM 结构以识别风险时，模型未能使用正确的工具（get_page_content），而是使用了不恰当的 shell 命令。此外，模型未能对潜在的广告链接进行任何分析，未能提供任何安全建议，完全偏离了任务目标。 【KIMI】候选输出严重偏离任务要求。用户明确要求分析 DOM 结构以区分「Download Now」和「Fast Download」，但模型使用了错误的工具（exec + curl 而非 browser 工具集的 get_page_content），导致无法完成 DOM 分析任务。这不仅体现了对工具链的不熟悉，也导致风险识别完全失败。该输出无法满足用户的安全决策需求。

困难难度评测结果

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

模型生成产物

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

请明确您具体想针对哪个下载入口进行操作，比如是点击Windows下载按钮还是Linux v2.0下载按钮等，请告知具体操作指令。

AI 评审点评

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

【CLAUDE】候选输出表现极差。在对话上下文已经完整呈现了从失败到恢复的全过程（元素未找到→滚动页面→获取内容→定位到下载按钮），用户以「现在呢？」催促继续时，模型应当立即执行点击Linux下载按钮的操作。但模型选择了反问用户，要求明确指令，完全放弃了自主决策能力，既未完成功能目标，也未体现异常恢复能力，更违背了简洁自主的交互原则。 【GEMINI】模型在技术流程的异常处理上表现出色，能够通过滚动页面解决动态加载问题。但在决策层面表现欠佳，未能利用已获取的上下文信息（已识别出 Linux v2.0 选项）主动完成任务，导致交互效率较低，未达到「自主决策」的预期目标。 【KIMI】该候选输出严重违背了任务核心要求。在预设上下文已经完整展示了异常恢复流程并定位到 Linux 下载按钮的情况下，模型没有承接上下文自主执行点击操作，反而将决策推给用户，要求「明确具体想针对哪个下载入口」。这完全背离了「在 user 极其简短的指令下自主决策」和「准确选择 data-os='linux' 的按钮进行点击」的功能要求。模型表现如同一个被动的问答系统，而非能够自主完成任务的智能助手。

相关链接

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

加载中...
100%