Google: Gemma 4 31B 在「群组中仅 @ 触发」的评测结果

基本信息

• 模型名称：Google: Gemma 4 31B
• 用例名称：群组中仅 @ 触发
• 测试类型：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 的配置文件中设置 Telegram 渠道，使得它在群组里只有被「@」时才回复？

任务要求

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

1. 准确指出需要修改的配置文件路径或配置项名称
2. 说明「at_only」或类似的布尔开关逻辑
3. 解释该配置对群组消息过滤的作用机制

评测结果

综合得分

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

基础难度评测结果

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

AI 评审点评

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

模型返回空输出，已跳过 AI 评分（finish_reason=stop）

进阶难度评测结果

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

模型生成产物

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

既然 `at_only: true` 已经配置但没有生效，这通常意味着处理 Discord 消息的逻辑代码中没有正确检查这个标志位，或者该标志位在代码中的优先级低于其他触发条件。 我需要检查处理 Discord 消息的源代码，看看 `at_only` 是如何被实现的。我先列出项目目录来寻找相关的代码文件。 thought call:ls(".")

AI 评审点评

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

【KIMI】整体而言，候选人在故障排查深度和工具运用能力方面都表现出了较高的水平。它能够正确地识别配置问题，并提出了合理的调试建议。然而，在直接回答用户关于 Intent 权限和全局监听插件的问题方面还有改进空间。总的来说，候选人的表现是令人满意的。

困难难度评测结果

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

模型生成产物

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

[[reply_to_current]]我已经将 `config/channels.yaml` 中的 `at_only` 设置为了 `true`。 这意味着现在 Bot 在群组中**仅会在被 @ 时才会响应**，普通的聊天消息将被忽略。 你可以现在去群组里测试一下： 1. 发送一条普通消息 $\rightarrow$ Bot 应该**没有**反应。 2. 发送一条 `@Bot 你的指令` $\rightarrow$ Bot 应该**正常**响应。

AI 评审点评

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

【KIMI】整体上，Assistant 表现出了较高的运维安全性和综合决策能力。它能够正确处理权限问题，并提供了一个全面的解决方案来实现「仅 @ 触发」的功能。尽管在实际操作中可能缺少一些步骤，如备份配置文件，但考虑到上下文限制，Assistant 的表现是令人满意的。

相关链接

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

• 查看所有模型在此用例的表现：「群组中仅 @ 触发」
• 查看该模型的所有评测结果：Google: Gemma 4 31B
• 浏览同维度的其他用例：「渠道连接与消息路由」
• 返回排行榜首页