Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ADB Validation Companion

    1

    Plan an Android or IVI validation capture, find gaps in ADB Validation Console exports, and prepare a reproducible defect or retest handoff.

    $6

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned
    ADB Validation Companion

    ADB Validation Companion

    Example session with this skill installed

    Review this synthetic console session for IVI-014 on build 1.2.3. Open Media, switch to Navigation, then return to Media. The surface should render within 500 ms of return. The operator reports a blank surface. Logcat records return at 14:22:10.100, render pending at 14:22:10.212 and 14:22:10.390, then ends. The bundle manifest reports Logcat exit 0 with a file and Bugreport exit 1 with no file. What can I hand off and what should I retest?

    • Read your context and instructions
    • Compiled the adb validation companion

    IVI-014 · build 1.2.3 · simulated session

    Reproduction: Open Media, switch to Navigation, then return to Media. Expected: Media renders by 14:22:10.600.

    Time or sourceEvidence
    14:22:10.100 · LogcatReturn-to-Media trigger
    Run noteOperator reported the Media surface stayed blank
    14:22:10.212 and 14:22:10.390 · LogcatRender pending. The latter is the last captured event
    Support bundle manifestLogcat exists. Bugreport returned exit 1 and has no file

    Handoff: The reported blank surface is suitable for defect triage. The 500 ms timing verdict is

    Inconclusive because the capture ends 210 ms before the deadline. Recovery is unobserved. The missing bugreport limits diagnostic context.

    Retest: Capture the same steps and record continuously through the deadline. Include the render-ready marker or record its absence through the entire window. Collect further diagnostics if needed to explain the rendering state.

    $6/mo

    Subscription · always the latest version

    • Secure checkout via Stripe
    • Cancel anytime
    • Delivered live via MCP

    About this skill

    ADB Validation Companion takes a validation case from capture plan to defect handoff. It works with supplied Android or Android Automotive logcat, validation snapshots, support bundle manifests, and run notes.

    • Plan a capture around a trigger, acceptance criterion, and recovery marker.
    • Check which required files were collected and whether the log spans the needed observation window.
    • Separate the reported symptom, verified timing result, and remaining evidence gaps.
    • Return repeatable steps, timestamped evidence, and a targeted retest.

    Includes a console export guide, a reusable handoff template, a synthetic example, and a local Python manifest checker. The companion operates on supplied files and requires no connection to a device. ADB Validation Console is an optional way to produce the exports.

    Does not connect to live devices. Cannot grade log content quality or fix device compatibility issues. Relies on the user providing specific console export maps.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed today

    Permissions

    Terminal / Shell
    Read Files

    Reads buyer-selected evidence. Optional terminal access runs the local Python manifest checker. No live device or network access is required.

    Listedtoday

    What's inside

    Frequently Asked Questions

    It checks whether the capture covers the required observation window, then separates observed symptoms, supported test verdicts, and missing evidence.

    Provide logcat text, a Validation Console snapshot, an extracted support bundle manifest, or timed run notes. Artifact coverage depends on what was collected.

    It reviews evidence you supply after collection. The console can be used separately to collect exports on an authorized device.

    Capture and review instructions, a console export guide, a handoff template, a synthetic worked example, and an optional Python manifest checker.

    Yes. It helps choose a reproducible trigger, observation window, recovery marker, and the smallest useful set of artifacts.

    It identifies observations and evidence gaps. A causal finding needs corroborating evidence from the relevant capture or retest.

    New in Testing & Debugging