Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →k9i-0/mobile-automation
MCP (dart-mcp + Marionette) を使ったFlutterアプリのE2E自動化・UI検証ガイド。シミュレーターでのUI動作確認、モックプレビュー検証、Bridge経由のE2Eテスト、スクリーンショット撮影など、アプリの動作検証が必要なときに使う。「動作確認して」「UIを検証して」「E2Eテスト」「シミュレーターで確認」「モックで確認」と言われたときや、UI変更後の検証フェーズで使用すること。
Passed 19 of 21 test cases with the skill, and 5 of 21 without it.
and 26 more in the full report
15 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
After navigating to a new screen in our Flutter app, I want to verify the screen state. I have tools for getting widget trees, capturing screenshots, fetching interactive elements, and checking logs. What tool should be called first, and what is the rule regarding screenshot usage?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends get_interactive_elements as the highest priority tool for post-navigation checks. | Passed | Passed |
| Recommends restricting screenshot capture to a maximum of 3 to 5 per session. | Missed | Passed |
The instructions your model reads when the skill loads.
検証対象に応じて必要な参照だけ読む。dart-mcp / Marionette で実行時の状態を確認する。
8766。ユーザーが指定したデバイス・接続先を優先する。本番 8765 のプロセスを停止しない。git rev-parse --show-toplevel、アプリはその配下の apps/mobile。e2e-verifier 等へ委譲できる。get_interactive_elements のキー・boundsを使う。画面遷移やジェスチャー後は結果を確認する。test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.