StepFun: Step 3.5 Flash 在「插件本地调试」的评测结果
这是该 AI 模型在此测试用例上的详细评测结果。
基本信息
- 模型名称：StepFun: Step 3.5 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 模型的具体任务要求：
我在本地用「ts-node」运行插件一切正常，但是执行「npm run build」并发布到 OpenClaw 插件目录后，系统提示「Failed to load plugin: Cannot find module」。这可能是什么原因？
任务要求
AI 模型需要满足以下要求：
- 指出「dependencies」与「devDependencies」在打包后的区别
- 提到检查「package.json」中的「main」或「exports」字段路径是否指向编译后的 dist 目录
- 说明 OpenClaw 运行时对编译产物（JS文件）的依赖要求
评测结果
综合得分
该模型在此用例的得分为：— 分（满分 100 分），未通过
基础难度评测结果
- 得分：— 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我来帮你诊断这个常见的 TypeScript 插件部署问题。让我先看看你的项目结构。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【KIMI】候选输出完全未能回答用户的问题。用户明确询问插件本地运行正常但发布后报「Cannot find module」的原因，这是一个典型的 TypeScript 插件部署问题，涉及 package.json 配置、依赖管理和编译产物路径等知识点。然而候选输出仅停留在「让我先看看项目结构」的初始步骤，没有提供任何实质性的诊断分析或解决方案，与参考答案中详细列出的两个主要原因（main 字段指向错误、devDependencies 未安装）完全不符。该输出在基础诊断准确性维度上得分为 0。
进阶难度评测结果
- 得分：21.5 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我将读取 manifest.json 文件以分析具体的 Schema 错误原因。 ./plugins/weather-bot/manifest.json
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】候选输出是一个纯工具调用动作，仅触发了对 manifest.json 的读取，没有提供任何关于 OpenClaw 插件 Schema 规范的实质性分析或修复建议。对话上下文已经提供了足够的线索（目录结构和 package.json 内容），模型应当能够在调用工具的同时给出初步诊断和修复方向。参考答案明确指出了缺失字段、配置修复步骤和验证命令，而候选输出完全未触及这些内容，配置规范掌握度极低。 【GEMINI】模型当前仅停留在执行工具调用的阶段，未能根据用户请求提供实质性的分析结果和修复方案。在面对「请继续分析并告诉我修复方案」的明确指令时，模型应在读取文件后立即结合规范给出诊断，而非仅输出工具调用。建议模型在后续步骤中补充缺失的 Schema 字段说明、配置规范及验证命令。 【KIMI】候选输出严重不完整，仅包含一个未执行的读取文件意图，完全没有针对「Invalid Plugin Schema」错误进行任何实质性分析或提供修复方案。用户明确请求「继续分析 manifest.json 并告诉我修复方案」，但候选输出仅停留在准备读取文件的阶段，未产出任何有价值的诊断信息或解决方案，无法满足用户的实际需求。
困难难度评测结果
- 得分：80.8 分
- 通过状态：已通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
当前已定位到两个生产环境特有的问题： 1. **同步阻塞**：`sync-processing: heavy image task blocked event loop for 5000ms` —— 插件在主线程同步处理大图，导致事件循环卡顿，这是插件崩溃的直接诱因。 2. **缓存不可写**：`file-system: cannot write to /usr/src/app/plugins/weather-bot/cache` —— 生产环境的 `cache` 目录对插件进程只读，无法生成或更新缓存文件，导致后续逻辑异常。 本地能运行是因为开发环境通常拥有更高的文件系统权限，且同步阻塞被本地硬件性能掩盖，不会立即触发崩溃保护。 **接下来需要修复**： - 将同步图像处理改为异步（使用 `worker_threads` 或 `child_process`） - 将缓存路径迁移到可写的 `tmp` 目录（如 `/tmp` 或环境变量指定的目录） - 生产环境需确保插件对缓存目录具备写权限 是否开始修复这些代码问题？
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【GEMINI】模型展现了良好的故障排查能力，能够从 Node.js 运行机制的角度给出专业且客观的诊断结果。修复建议方向正确，具备实操性。如果能更深入地结合 OpenClaw SDK 的 API 规范和 Webhook 异步处理架构，评价会更高。 【KIMI】整体而言，候选人的输出在复杂故障排查与架构优化方面表现出色，准确地识别了生产环境特有的问题，并给出了具体的解决方案。这些解决方案涉及Node.js事件循环、容器化权限限制和OpenClaw SDK的高级特性，显示出候选人对这些概念有深入的理解。然而，输出在某些细节上仍有提升空间，如使用'sharp'库的异步方法和配置OpenClaw的'sandbox'权限。如果候选人能在这些方面进一步完善输出，将更接近完美的解决方案。
相关链接
您可以通过以下链接查看更多相关内容：
