e2e-testing — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited e2e-testing (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
flutter-skill is an MCP server that connects AI agents to running apps across 8 platforms. The agent takes screenshots, taps elements, enters text, scrolls, navigates, inspects UI trees, and verifies state — all through natural language.
| Platform | Setup |
|---|---|
| Flutter (iOS/Android/Web) | flutter pub add flutter_skill |
| React Native | npm install flutter-skill-react-native |
| Electron | npm install flutter-skill-electron |
| iOS (Swift/UIKit) | SPM: FlutterSkillSDK |
| Android (Kotlin) | Gradle: flutter-skill-android |
| Tauri (Rust) | cargo add flutter-skill-tauri |
| KMP Desktop | Gradle dependency |
| .NET MAUI | NuGet package |
# npm (recommended)
npm install -g flutter-skill
# Homebrew
brew install ai-dashboad/flutter-skill/flutter-skill
# Or download binary from GitHub ReleasesAdd to your AI agent's MCP config (Claude Desktop, Cursor, Windsurf, OpenClaw, etc.):
{
"mcpServers": {
"flutter-skill": {
"command": "flutter-skill",
"args": ["server"]
}
}
}flutter-skill initAuto-detects project type and patches your app with the testing bridge.
Verify: Output should confirm the project type was detected and main entry point was patched. If it fails, check that you are in the project root and the framework is supported.
flutter-skill launch .Verify: A VM Service URI appears in the output (e.g. ws://127.0.0.1:50000/ws). If no URI appears, check that Flutter/the target framework is installed and the app compiles.
The agent follows this core loop:
screenshot() — see the current screeninspect_interactive() — discover all tappable/typeable elements with semantic refstap(ref: "button:Login") — tap using stable semantic referenceenter_text(ref: "input:Email", text: "[email protected]") — type into fieldwait_for_element(key: "Dashboard") — verify navigation succeededscreenshot() — confirm final stateIf `inspect_interactive()` returns no elements: Take a screenshot to confirm the screen loaded, then check get_logs() for errors. The app may still be loading — retry after a short wait.
| Tool | Description |
|---|---|
screenshot | Capture current screen as image |
tap | Tap element by key, text, ref, or coordinates |
enter_text | Type text into a field |
scroll | Scroll up/down/left/right |
swipe | Swipe gesture between points |
long_press | Long press an element |
drag | Drag from point A to B |
go_back | Navigate back |
press_key | Send keyboard key events |
| Tool | Description |
|---|---|
inspect_interactive | Get all interactive elements with semantic ref IDs |
get_elements | List all elements on screen |
find_element | Find element by key or text |
wait_for_element | Wait for element to appear (with timeout) |
get_element_properties | Get detailed properties of an element |
| Tool | Description |
|---|---|
set_text | Replace text in a field |
clear_text | Clear a text field |
get_text | Read text content |
| Tool | Description |
|---|---|
get_logs | Read app logs |
clear_logs | Clear log buffer |
inspect_interactive returns elements with stable semantic reference IDs:
button:Login → Login button
input:Email → Email text field
toggle:Dark Mode → Dark mode switch
button:Submit[1] → Second Submit button (disambiguated)Format: {role}:{content}[{index}]
7 roles: button, input, toggle, slider, select, link, item
Use refs for reliable element targeting that survives UI changes:
tap(ref: "button:Login")
enter_text(ref: "input:Email", text: "[email protected]")screenshot() → inspect_interactive() → tap/enter_text → screenshot() → verifyAlways call screenshot() before and after actions. Use wait_for_element() after navigation — apps need time to transition.
screenshot() to verify the UI responded.wait_for_element(key: "target_screen") with a timeout. If it times out, call screenshot() and get_logs() to diagnose.get_logs() and inspect_interactive() to understand what elements are present.inspect_interactive()~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.