See Build Outcome Verifier in action — 30 seconds:
Direct link: demo-30s.mp4
Build Outcome Verifier is a premium agent skill available exclusively through:
Compatible with Claude Code, Codex CLI, Cursor, Gemini CLI, OpenClaw, Windsurf, GitHub Copilot, and 15+ other agent platforms.
Agents say "build succeeded" when:
This skill forces observable proof that the artifact is functional. No proof, no "done."
| Platform | Status | Tools Required |
|---|---|---|
| Android (APK/AAB) | ✅ Primary | adb, device/emulator |
| iOS (IPA) | 🔜 Planned | xcrun, ios-deploy |
| Web (static/PWA) | 🔜 Planned | http-server, Playwright |
| macOS/Windows | 🔜 Planned | hdiutil / Selenium |
Claude Code says "Build successful." You install it — crash on launch. This skill catches that before you waste time.
Your GitHub Actions build passes but the APK is 4KB (it's a stub). This skill runs as the last CI step: install, launch, verify. If it fails, the pipeline fails — not production.
No QA team. Pushing a build at 2am. You need to know the APK actually installs before submitting to Google Play. One command loads this skill.
Agent A builds. This skill verifies. Agent C deploys. Quality gate between stages — no broken artifacts progressing downstream.
A dependency update breaks launch but compiles fine. Only a runtime smoke test catches it. Run this on every PR merge.
Build Outcome Verifier works with any CI runner that supports Android emulators — GitHub Actions, GitLab CI, Jenkins, CircleCI. After purchasing, the skill includes a ready-to-use GitHub Actions workflow snippet.
The skill's verification commands run as the final step in your pipeline. If the app doesn't install or crashes on launch, the pipeline fails — not production.
| Permission | What It Does | Why Needed |
|---|---|---|
adb | Install APKs, launch apps, read device logs | Verify installs and detect crashes |
| Local shell | Run adb commands on the user's machine | All verification is local |
| Logcat (read-only) | Inspect crash/ANR output | Detect runtime failures |
🔒 No network calls. No telemetry. No API keys. No third-party services. Works fully offline.
| Problem | Cause | Fix |
|---|---|---|
adb: command not found | ADB not installed | sudo apt install adb / brew install android-platform-tools |
no devices/emulators found | No Android device connected | Start emulator or connect USB device |
INSTALL_FAILED_UPDATE_INCOMPATIBLE | Different signature | adb uninstall com.yourcompany.yourapp first |
| ANR in background | Background thread deadlock | Increase sleep to 15s |
Yes — adb needs a device or emulator. Most CI runners support Android emulators.
~15 seconds total. The time saved not debugging a broken deploy dwarfs this.
Not yet — planned for a future release.
Yes — it's plain markdown. Add your own verification commands between the install step and the pass declaration.
Any agent supporting SKILL.md — Claude Code, Codex CLI, Cursor, Gemini CLI, OpenClaw, Windsurf, Copilot, and 15+ others.
The agent is instructed to record the failure logs and NOT claim "task complete." It must fix the issue and rebuild before the verifier will pass.