工具包指南
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:预检
始终先运行`flutter-mcp-toolkit doctor --json`。解析输出: `status: "ok"` — 继续步骤 2。 `status: "error"` 和 `error.code: "binary_not_found"` — 加载 `flutter-mcp-toolkit-setup` 并按照其安装说明进行操作。 `status: "error"` 和 `error.code: "vm_not_connected"` — 加载
第 2 步:根据用户的意图选择正确的技能
用户意图·加载技能读取状态(“屏幕上有什么?”,“显示错误”,“屏幕截图”)·`flutter-mcp-toolkit-inspect`驱动UI(“点击X”,“输入Y”,“滚动到Z”,“热重载”)·`flutter-mcp-toolkit-control`诊断(“为什么X失败?”,“显示最近的日志”,“评估表达式”)·`flutter-mcp-toolkit-debug`注册应用程序特定的 MCP 工具/资源(`MCPCallEntry`、`bootstrapFlutter` `additionalEntries`)· `flutter-mcp-toolkit-custom-tools`
第三步:执行
每个任务技能都有工具列表、参数形状和示例调用。按照技能顶部的前奏进行操作 - 它会告诉您是在调用 MCP 工具还是在 CLI 上运行。
<!-- @FMT_MODE_PRELUDE -->
## When to use
Use this skill when the user wants to inspect or drive a running Flutter app
from this conversation. Examples:
- "Tap the login button in my app"
- "Why is the home screen blank?"
- "Take a screenshot and tell me what's broken"
- "Expose my cart / flags / internal state to the agent via MCP"
If the user is asking about Flutter concepts unrelated to a running app
(architecture questions, package selection), this skill does not apply.
## Step 1: Preflight
Always run `flutter-mcp-toolkit doctor --json` first. Parse the output:
- `status: "ok"` — proceed to Step 2.
- `status: "error"` and `error.code: "binary_not_found"` — load
`flutter-mcp-toolkit-setup` and follow its install instructions.
- `status: "error"` and `error.code: "vm_not_connected"` — load
`flutter-mcp-toolkit-setup` and follow its troubleshooting section.
- Any other error — load `flutter-mcp-toolkit-debug` and read the error
envelope playbook.
## Step 2: Pick the right skill for the user's intent
| User intent | Load skill |
|---|---|
| Read state ("what's on screen?", "show me errors", "screenshot") | `flutter-mcp-toolkit-inspect` |
| Drive UI ("tap X", "type into Y", "scroll to Z", "hot reload") | `flutter-mcp-toolkit-control` |
| Diagnose ("why is X failing?", "show recent logs", "evaluate expression") | `flutter-mcp-toolkit-debug` |
| Register app-specific MCP tools/resources (`MCPCallEntry`, `bootstrapFlutter` `additionalEntries`) | `flutter-mcp-toolkit-custom-tools` |
If the task spans more than one (e.g. "tap the button and show me what
changed"), load `inspect` AND `control`. Skills are additive.
## Step 3: Execute
Each task skill has the tool list, parameter shapes, and example calls. Follow
the prelude at the top of the skill — it tells you whether you're calling MCP
tools or shelling out to the CLI.
## Tool taxonomy reference
The core toolkit tools fall into these categories. The full list with
parameter shapes lives in the task skills.
- **Inspection (read-only):** `discover_debug_apps`, `get_app_errors`,
`get_screenshots`, `get_view_details`, `get_vm`, `get_extension_rpcs`,
`semantic_snapshot`, `inspect_widget_at_point`, `capture_ui_snapshot`,
`connect_debug_app`. → `flutter-mcp-toolkit-inspect`.
- **Interaction (mutating):** `tap_widget`, `long_press`, `enter_text`,
`fill_form`, `scroll`, `swipe`, `drag`, `hover`, `press_key`, `wait_for`,
`navigate`, `handle_dialog`, `hot_reload_flutter`, `hot_restart_flutter`,
`hot_reload_and_capture`. → `flutter-mcp-toolkit-control`.
- **Debug:** `get_recent_logs`, `evaluate_dart_expression`. →
`flutter-mcp-toolkit-debug`.
- **Dynamic registry (app-defined):** after registration in the Flutter app,
list with `list_client_tools_and_resources`, then `client_tool` /
`client_resource` — wire names as **`fmt_*`** when calling MCP. →
`flutter-mcp-toolkit-custom-tools`.
## When in doubt
If `doctor` is green but a tool call fails, read the returned `error.code`
and `error.recovery` fields. The full code → recovery table is in
`flutter-mcp-toolkit-debug`.
---
> Source: [Arenukvern/mcp_flutter](https://github.com/Arenukvern/mcp_flutter) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
何时使用
第 1 步:预检
第 2 步:根据用户的意图选择正确的技能
第三步:执行
工具分类参考
文件/命令 -> flutter-mcp-toolkit doctor --json · status: "ok" · status: "error" · error.code: "binary_not_found" · flutter-mcp-toolkit-setup · error.code: "vm_not_connected" · flutter-mcp-toolkit-debug · flutter-mcp-toolkit-inspect
内容校验值 -> ae6f2fbca72a
当前原文的自动摘译,尚未人工审校。
何时使用
当用户想要从此对话中检查或驱动正在运行的 Flutter 应用程序时,请使用此技能。示例:“点击我的应用程序中的登录按钮”“为什么主屏幕是空白的?” “截图并告诉我哪里出了问题”
第 2 步:根据用户的意图选择正确的技能
用户意图·加载技能阅读状态(“屏幕上有什么?”,“显示错误”,“屏幕截图”)·
flutter-mcp-toolkit-inspect驱动器UI(“点击X”,“输入Y”,“滚动到Z”,“热重载”)·flutter-mcp-toolkit-control诊断(“为什么X失败?”,“显示最近的日志”,“评估表达式”)·flutter-mcp-toolkit-debug注册特定于应用程序MCP 工具/资源 (MCPCallEntry、bootstrapFlutteradditionalEntries) ·flutter-mcp-toolkit-custom-tools工具分类参考
核心工具包工具属于这些类别。包含参数形状的完整列表位于任务技能中。检查(只读):
discover_debug_apps、get_app_errors、get_screenshots、get_view_details、get_vm、get_extension_rpcs、semantic_snapshot、inspect_widget_at_point、capture_ui_snapshot、