| FMRS | 54 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 14 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Teams with a debuggable, running Flutter/React Native/Electron/Tauri/mobile/web app who want natural-language E2E testing instead of writing test scripts
- Developers who want to drive exploratory testing directly from an MCP client like Claude Desktop, Cursor, Windsurf, or Copilot
- Scenarios where low-token UI understanding (accessibility-tree snapshots instead of screenshots) matters for cost
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Teams that require a tool maintained by an official upstream vendor (e.g. Flutter, Google, Anthropic) — this is a third-party project maintained by ai-dashboad
- Restricted environments that cannot integrate a platform SDK into the app or cannot install local npm/CLI tooling
- Situations requiring the production-proven maturity and community scale of established tools like Playwright or Appium
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Local execution permission to launch and run the `flutter-skill` executable over stdio
- Connection and control permissions over the app/browser instance under test (tap, type, screenshot, read widget tree, etc.)
- Access to runtime data such as app logs, console messages, and network requests
- Network port listening permission when using the HTTP `serve` mode (configurable via `--port`/`--host` or environment variables)
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - This is a third-party open-source implementation, not maintained by Flutter, Google, or Anthropic — the source material does not describe any audit, signing, or supply-chain security process
- The tools can perform arbitrary interactions (tap, type, execute JavaScript via `eval`, inject login sessions, etc.); if driven by a malicious or manipulated prompt, they could take unintended or destructive actions against the app under test
- Tools like `eval` execute arbitrary JavaScript in the page context, and `mock_api`/`intercept_requests` can alter network behavior — restrict use to trusted development/test environments
- The manifest version (0.9.36) indicates the project is still pre-1.0 and its interface may change
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Cursor, Windsurf, VSCode Copilot, Cline, Continue, OpenClaw | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 100 | 15 |
|---|