selector-map-calibrate

Calibrate Connect mobile selector maps against live emulator devices for Android APK versions.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill selector-map-calibrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: selector-map-calibrate
Source: https://github.com/dimagi-internal/ace/tree/main/skills/selector-map-calibrate
Command: npx skills add https://github.com/dimagi-internal/ace --skill selector-map-calibrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a new Connect Android APK version is released, teams typically copy the previous selector map, mark all rows as unverified, and only fix broken selectors reactively when a test run encounters a failure. This approach never converges, as unverified selectors are tied to mutually exclusive device states that cannot be captured in a single snapshot, leaving most selectors unverified indefinitely and causing flaky mobile tests.

Core Features & Use Cases

  • Full device state walk: Drives a cold-booted emulator through every app state from first launch to deliver home to capture UI dumps for all selector map rows.
  • Drift reconciliation: Identifies mismatches between the selector map and live UI dumps, updates map entries with verified values, and removes dead or unused rows.
  • Recipe migration: Replaces hardcoded raw resource IDs in static test recipes with references to verified selector map entries, then validates the updated recipes on-device.
  • Use case: When releasing Connect APK 2.63.0, use this skill to fully verify the new selector map, migrate all test recipes to use verified selectors, and generate a calibration report documenting coverage and residual gaps.

Quick Start

Use the selector-map-calibrate skill to fully verify the selector map for Connect APK version 2.63.0 against a fresh emulator and migrate all static test recipes to use the verified selectors.

Frequently Asked Questions about selector-map-calibrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calibrate a Connect mobile selector map against an Android emulator?

Selector map calibration drives a cold-booted Android emulator through every app state from first launch to deliver home. It captures UI dumps for all selector map rows, reconciles selector drift, and updates map entries with verified values.

Can I fully verify a selector map for a specific Connect APK version?

The best way to migrate static test recipes off raw resource IDs is to replace hardcoded values with references to verified selector map entries. This ensures recipe-lint clean migrated recipes and validates the updated recipes directly on-device.

How do I document residual gaps and coverage when fixing selector drift?

Yes, you can fully verify a selector map for a specific Connect APK version by running a full device state walk against a fresh emulator. This process generates a calibration report documenting coverage and complete audit trails for all calibration activities.

Do I need a cold-booted emulator to resolve non-convergent reactive patching of mobile selectors?

To document residual gaps and coverage when fixing selector drift, generate a calibration report after reconciling the selector map. This report provides complete audit trails for calibration activities, verified selector provenance, and records any remaining coverage gaps.

Do I need a cold-booted emulator to resolve non-convergent reactive patching of mobile selectors?

Yes, resolving non-convergent reactive patching requires a cold-booted emulator to perform a full device state walk. This ensures all mutually exclusive device states are captured accurately, allowing dead or unused selector rows to be removed safely.