运行时验证
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
<!-- @FMT_MODE_PRELUDE -->
# Flutter MCP CLI Runtime Validation
Use this skill when you need agent-style runtime validation through `flutter-mcp-toolkit` with minimal operator steps.
## Two-Step Flow
1. Launch the Flutter app in debug mode.
2. Run one CLI command:
```bash
dart run mcp_server_dart/bin/flutter_mcp_toolkit.dart --save-images --output-dir .flutter_mcp/runtime_validation validate-runtime \
--target ws://127.0.0.1:8181/<token>/ws \
--timeout-ms 10000 \
--post-reload-delay-ms 500 \
--after-reload
```
Optional skill install in the same command:
```bash
dart run mcp_server_dart/bin/flutter_mcp_toolkit.dart validate-runtime \
--target ws://127.0.0.1:8181/<token>/ws \
--install-skill
```
Permission behavior for this flow:
- `validate-runtime` stays read/write only for visual capture and defaults to `auto_request_once`.
- `doctor` remains read-only.
- On macOS, Screen Recording permission belongs to the host process running `flutter-mcp-toolkit`.
- On web, `flutter_layer` is the only supported truth path and no OS permission prompt is expected.
- If the first `capture_ui_snapshot` attempt uses host `desktop_window` and fails (common on macOS when the window is not foregrounded, or for iOS Simulator), `validate-runtime` automatically retries once with `flutter_layer`.
- You may pass the VM URI as global `--vm-service-uri` instead of `validate-runtime --target` when only one URI is needed.
## What `validate-runtime` Must Prove
- Doctor preflight passes critical checks.
- Required toolkit extensions exist:
- `ext.mcp.toolkit.app_errors`
- `ext.mcp.toolkit.view_details`
- `ext.mcp.toolkit.view_screenshots`
- `ext.mcp.toolkit.inspect_widget_at_point`
- Screenshot capture works.
- View details (layout metadata) are available.
- App errors are retrievable.
- If `--after-reload` is enabled, post-reload screenshot also works.
## Output Handling
- Use `data.summary` as pass/fail status for automation.
- Use `data.summary.captureFallbackUsed` to see whether the `flutter_layer` retry succeeded after a failed `desktop_window` attempt.
- Use `data.steps` for per-step evidence and retries.
- Use `data.doctor.checks` to explain setup blockers.
- Use `data.summary.screenshotFiles` for saved screenshot paths when `--save-images` is enabled.
- When `--save-images` is enabled, read screenshot file URLs from step data.
- For visual debugging reports, also run:
- `exec --name capture_ui_snapshot --args '{"errorsCount":4,"compress":true,"includeViewDetails":true,"includeErrors":true}'`
- `exec --name inspect_widget_at_point --args '{"x":<int>,"y":<int>}'`
## Failure Rules
- If toolkit extensions are missing, stop and report instrumentation gap with exact fix:
- add `mcp_toolkit` to app dependencies
- ensure `MCPToolkitBinding.instance.bootstrapFlutter(...)` or equivalent manual initialization runs before `runApp`
- hot restart or rerun the app
- If first explicit URI connect fails, retry is automatic for retryable connection errors.
- If screenshots are blank, verify app window is visible and retry.
- If macOS visual capture is denied, use:
- `dart run mcp_server_dart/bin/flutter_mcp_toolkit.dart permissions status`
- `dart run mcp_server_dart/bin/flutter_mcp_toolkit.dart permissions request`
- `dart run mcp_server_dart/bin/flutter_mcp_toolkit.dart permissions open-settings`
- If app cannot be instrumented, do not claim screenshot/layout/error inspection success.
## Visual QA + Source Mapping Rules
- Always compare before/after screenshot evidence around changes.
- For each reported visual issue, provide coordinate + `inspect_widget_at_point` output.
- Map defects to source using `get_app_errors` top stack frame (`file`, `line`, `column`) when available.
- Do not use `debug_dump_*` unless explicitly requested.
## Challenge Cases (Always Call Out Explicitly)
- No running debug app: `doctor` critical failure on `vm_target_reachable`; request app launch before continuing.
- Wrong target URI/token: treat as connection mismatch and retry with exact `app.debugPort.wsUri`.
- Toolkit added but still missing extensions: hot reload is often insufficient, require hot restart/full rerun.
- Non-modifiable app (cannot add toolkit): report inspection as unavailable instead of guessing.
---
> Source: [Arenukvern/mcp_flutter](https://github.com/Arenukvern/mcp_flutter) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
两步流程
validate-runtime 必须证明什么
输出处理
失败规则
视觉 QA + 源映射规则
文件/命令 -> flutter-mcp-toolkit · validate-runtime · auto_request_once · doctor · flutter_layer · capture_ui_snapshot · desktop_window · --vm-service-uri
内容校验值 -> 0ae8ff54917a
当前原文的自动摘译,尚未人工审校。
两步流程
在调试模式下启动 Flutter 应用程序。运行一个 CLI 命令:在同一命令中安装可选技能:此流程的权限行为:
validate-runtime仅针对视觉捕获保持读/写状态,默认为auto_request_once。validate-runtime 必须证明什么
医生在飞行前通过了严格的检查。存在所需的工具包扩展:
ext.mcp.toolkit.app_errorsext.mcp.toolkit.view_detailsext.mcp.toolkit.view_screenshots输出处理
使用
data.summary作为自动化的通过/失败状态。使用data.summary.captureFallbackUsed查看desktop_window尝试失败后,flutter_layer重试是否成功。使用data.steps获取每步证据并重试。使用data.doctor.checks来解释设置拦截器。当启用--save-images时,使用data.summary.screenshotFiles作为保存的屏幕截图路径。失败规则
如果缺少工具包扩展,请停止并报告检测差距并进行精确修复:将
mcp_toolkit添加到应用程序依赖项,确保在runApp热启动或重新运行应用程序之前运行MCPToolkitBinding.instance.bootstrapFlutter(...)或等效的手动初始化如果第一个显式 URI 连接失败,则会自动重试可重试的连接错误。视觉 QA + 源映射规则
始终比较更改前后的屏幕截图证据。对于每个报告的视觉问题,提供坐标 +
inspect_widget_at_point输出。使用get_app_errors顶部堆栈帧(file、line、column)(如果可用)将缺陷映射到源。除非明确要求,否则请勿使用debug_dump_*。