Skip to content

dimagi-internal/ace / skills/common-screenshot-capture

common-screenshot-capture

Verified

Capture and publish common Connect platform screenshots for training deck common modules. Manual trigger only — not part of /ace:run.

Common Screenshot Capture

Capture platform-level screenshots (CommCare install, PersonalID signup, Connect navigation) that are shared across ALL training decks. These are the "how Connect works" screenshots every opp reuses — driven by the Connect APK's own UI, not by any opp-specific config. Run manually when the Connect app UI changes.

Replaces the broader connect-baseline-screenshots skill with a focused scope aligned to the training deck common modules defined in templates/training-deck/_common/platform-setup.yaml.

When to run

Manual trigger only. NOT part of /ace:run. Run when:

  • Connect app has a UI update (new APK version)
  • PersonalID signup flow changes
  • Common screenshots are missing or stale. bin/ace-doctor's common_screenshot_pool probe WARNs when the pinned APK has no usable pool (ace#3060)
  • First-time setup for a new Connect app version
  • A new common training-deck module adds a Connect surface not previously covered

The check-in cadence is operator-judgment, not automated.

Prerequisites

  • ACE_WEB_PAT_TOKEN set (per-machine; mint via /ace:ace-web-pat-mint). Required for Step 0 fork.
  • AVD bootable via mobile_ensure_avd_running (this skill cold-boots itself; no pre-running AVD required).
  • Any rotated secret updated in ACE's Canopy vault and written to .env (/ace:setup --force-env, then restart Claude Code).

Coverage table — what's reachable live, what needs static fixtures

AliasSourceRecipeVerified live
commcare-welcomeLive04-personal-id.yaml (fresh-install state, no GO TO CONNECT MENU button)✓ 2026-05-24
connect-homeComposited (base: 00-connect-home.yaml)Step 5.4✓ 2.64.0, 2026-10-16
sync-buttonQUARANTINED03-sync-button.yaml — defective, see below✗ byte-identical to connect-home (ace#1832)
claim-oppComposited (base: 01-claim-opp.yaml, requires OPP_NAME)Step 5.4✓ 2.64.0, 2026-10-16
learn-installLive02-learn-install.yaml (requires OPP_NAME for crash recovery)✓ 2.64.0, 2026-10-17 (ace#3064)
personal-id-startLive04-personal-id.yaml (nav-drawer Sign In/Register)✓ 2026-05-24
personal-id-phoneLive04-personal-id.yaml✓ 2026-05-24
personal-id-nameLive04-personal-id.yaml✓ 2026-05-24
personal-id-verifyTemplate assetn/a — not this skill's job (ace#873)n/a
personal-id-photoTemplate assetn/a — not this skill's job (ace#873)n/a
personal-id-locationTemplate assetn/a — not this skill's job (ace#873)n/a
personal-id-doneTemplate assetn/a — not this skill's job (ace#873)n/a

sync-button is QUARANTINED — its recipe cannot produce a distinct frame (ace#1832). 03-sync-button.yaml fires takeScreenshot: "sync-button" BEFORE its own tapOn: action_sync, from a pre-state its header declares identical to 00-connect-home.yaml's post-state. So the alias is a byte-identical copy of connect-home, by construction, on every capture — not a flake. Measured 2026-09-06, both Drive ids fetched unauthenticated:

connect-home 1nUv5Yw4Z4L3xyXCU9xYZvrQBk9cLZADC
sync-button  1BqFXsUju_wFaIDYNsviTInBbOgGMzibp
md5 4d1c205591270cc4638b439c3a9981ff   (both)
242,393 bytes, 1080x2400, `cmp` reports no difference

Until the recipe is repaired and re-validated on a device, the pool publishes this alias as source: fixture, placeholder: true — a visible empty slot on any slide that cites it. That is deliberate: a deck citing @sync-button today would caption the Connect home screen as the sync control, and tell a field worker to look for a green check mark that is not in the picture. An empty slot is a smaller lie than a confident wrong one.

It did not bite yet only because the syncing slide in templates/training-deck/_common/platform-setup.yaml is prose-only and cites no image — a fact about that one slide, not a property of the pool. The next slide to cite it inherits the defect.

Repair is one recipe move (capture after the tap + settle wait) plus a device run to confirm the post-sync frame actually differs; the residual is that it may not, once the 5s wait has let any sync toast expire. See the banner in mcp/mobile/recipes/baseline/03-sync-button.yaml.

The PersonalID completion half left this roster (ace#873, operator decision 2026-08-13). It is no longer a capture target of any kind — not live, not a fixture-fallback. Those four screens are now committed deck-template artwork, declared in templates/training-deck/_common/assets/assets.yaml and loaded by training-deck-generate into manifest.template.

The reason is that they are uncapturable as a property of ACE's identity, not of the harness: +7426 demo phones bypass SMS OTP server-side, and the test user already exists, so "sign up" is an account recovery flow that returns the stored photo, skips the cached permissions dialog, and ends on "Account Recovered". Capturing that and captioning it as first-time sign-up would state something false to every trainee.

Carrying them as fixtures-awaiting-capture meant every run tried, failed, and recorded a miss against coverage that could never be closed — which is what made a coverage gate impossible to write (ace#856). As template content they are excluded from the coverage ratio by construction, and a missing one is a template-bundle defect rather than a run defect.

personal-id-id was removed outright, not converted. No such surface exists in the 2.63.x PersonalID flow: no row in connect-2.62.0, connect-2.63.0 or connect-2.63.2, no recipe step drives it, and both live-verified registration walks in connect-register-from-otp.yaml enumerate the full screen sequence with no ID scan. fixtures/README.md already prescribed exactly this remedy for a surface that turns out not to exist.

Still fixtures: the three install-flow aliases below. Those ARE capturable by anyone with a Google-signed-in device — they are simply out of scope for our AVD, which is a different situation and keeps a different label.

| play-store-search | Fixture | n/a (Play Store requires Google sign-in; out of scope for automation) | placeholder PNG | | commcare-install | Fixture | n/a (same) | placeholder PNG | | commcare-open | Fixture | n/a (same) | placeholder PNG |

8 reachable via live recipes; 8 require operator-committed static fixtures at templates/training-deck/_common/fixtures/<alias>.png.

Process

Step 0: Fork a known-good run to pin OPP_NAME

The claim-opp and learn-install captures require an UNCLAIMED Connect opp whose Learn CCZ installs cleanly. The ACE demo user's invite list accumulates stale pre-Nova-fix opps that hit "A part of your application is invalid" when claimed (reproduced live 2026-05-24 against LEEP run 20260506-1440). To guarantee a clean capture target, fork a recent successful run BEFORE invoking the baseline recipes.

/ace:fork-run \
  --opp_slug <recent-good-slug> \
  --from_run_id <YYYYMMDD-HHMM> \
  --from_skill connect-program-setup \
  --mode keep-all \
  --feedback "Common-screenshot baseline capture: fresh opp for claim-opp + learn-install."

Pick a <recent-good-slug> / <from_run_id> whose most recent run went through Phase 4 successfully on a post-2026-05-22 build. The fork re-runs Phase 4 + downstream — fresh Connect opp + fresh invite to ACE_E2E_PHONE. Read the new opp's name from run_state.yaml.phases.connect-setup.products.connect.opportunity.name and use it verbatim as OPP_NAME in Step 3.

Skip Step 0 only when interactively debugging — pass an operator-chosen OPP_NAME and accept that "first unclaimed match" fallback may hit stale broken invites.

Step 1: Cold-boot the AVD

mobile_ensure_avd_running({ avdName: process.env.ACE_AVD_NAME })

Auto-bootstrap registers the demo user (ACE_E2E_PHONE) and applies the environment baseline. Per CLAUDE.md "Phase preconditions are restored, not adapted" — always cold-boot per dispatch.

Step 2: Determine Connect APK version

After the AVD is up:

adb -s <serial> shell dumpsys package org.commcare.dalvik | grep versionName

This version string keys the output folder and manifest (e.g. 2.63.0).

Step 3: Create target Drive folder

ACE/_common/connect-screenshots/<version>/

via drive_create_folder. Parent MUST live on a Shared Drive (SA quota is 0 in My Drive — assertParentOnSharedDrive guards this).

Step 4: Run baseline recipes in sequence

All 5 shipped recipes live at mcp/mobile/recipes/baseline/. Run in order — each leaves the AVD in a state the next can build on.

Pass the same screenshotDir root to all of them. Since #1130 the MCP namespaces each dispatch's output as <screenshotDir>/<recipeId>/, and confines the start-of-run wipe (#756) to that subdir — so one recipe can no longer wipe an earlier recipe's captures, and the PNGs listed under each step below land in that recipe's own subdirectory. Read them back from the returned screenshotsDir / screenshots[].path, not by globbing the root.

4a. 04-personal-id.yaml (FIRST — requires wiped CommCare)

Prep before invoking:

# Re-enable GMS — bootstrap disables it for face-capture ManualMode,
# but CommCare 2.63.0's PersonalID launch blocks on a no-dismiss
# "Enable Google Play services" dialog when GMS is disabled.
adb -s <serial> shell pm enable com.google.android.gms

# Wipe local CommCare data — fresh-install state shows the authentic
# Welcome screen (without the post-registration GO TO CONNECT MENU
# button).
adb -s <serial> shell pm clear org.commcare.dalvik
adb -s <serial> shell am force-stop org.commcare.dalvik

Then:

mobile_run_recipe({
  recipePath: 'mcp/mobile/recipes/baseline/04-personal-id.yaml',
  screenshotDir: '/tmp/ace-baseline-capture/',
  envVars: {
    COUNTRY_CODE: env.ACE_E2E_COUNTRY_CODE.replace(/^\+/, ''), // "7"
    PHONE_LOCAL: env.ACE_E2E_PHONE_LOCAL,                       // "4260000100"
    PIN: env.ACE_E2E_PIN,                                       // "111111"
    NAME: env.ACE_E2E_NAME,                                     // "ACE Test"
    BACKUP_CODE: env.ACE_E2E_BACKUP_CODE,                       // "222222"
  },
});

Produces: commcare-welcome.png, personal-id-start.png, personal-id-phone.png, personal-id-name.png (+ bonus personal-id-app-lock.png, personal-id-backup-code.png, personal-id-done.png which currently shows "Account Recovered" — treat as bonus, not the deck alias).

Leaves AVD on the recovery-completed Connect home.

4b. 00-connect-home.yaml (navigation entry)

mobile_run_recipe({
  recipePath: 'mcp/mobile/recipes/baseline/00-connect-home.yaml',
  screenshotDir: '/tmp/ace-baseline-capture/',
  envVars: { PIN: env.ACE_E2E_PIN },
});

Produces: commcare-welcome.png (re-capture; prefer the one from 4a which is from a truly fresh-install state), connect-home.png.

Leaves AVD on the Connect opp list.

4c. 03-sync-button.yaml (from connect-home state)

mobile_run_recipe({
  recipePath: 'mcp/mobile/recipes/baseline/03-sync-button.yaml',
  screenshotDir: '/tmp/ace-baseline-capture/',
});

Produces: sync-button.png. Also triggers a server sync so any newly-forked opp (Step 0) pulls down to the device's invite list before Step 4d.

4d. 01-claim-opp.yaml (requires OPP_NAME from Step 0 fork)

mobile_run_recipe({
  recipePath: 'mcp/mobile/recipes/baseline/01-claim-opp.yaml',
  screenshotDir: '/tmp/ace-baseline-capture/',
  envVars: { OPP_NAME: forkedOppName }, // verbatim from Step 0
});

Produces: claim-opp.png (opp-detail with Start button), bonus claim-opp-list.png (the scrolled list view).

4e. 02-learn-install.yaml (taps Start, downloads Learn CCZ)

mobile_run_recipe({
  recipePath: 'mcp/mobile/recipes/baseline/02-learn-install.yaml',
  screenshotDir: '/tmp/ace-baseline-capture/',
  envVars: { OPP_NAME: forkedOppName }, // same value as 4d; read only by the crash-recovery branch
});

Produces: learn-install.png and learn-install-home.png (the post-install Learn StandardHomeActivity).

The 2.64.0 surface. After Start, 2.64.0 shows a FULL-SCREEN blue page (Connect toolbar on top, phone-with-heart icon, "Downloading Learn App", a progress bar; "Step N of 11" while it runs), not the 2.63-era progress dialog. Then a "Launching App / Contacting Server" dialog, then the Learn home. The recipe WAITS for the "Downloading Learn App" text before taking learn-install (a one-shot probe straight after the tap ran before the page rendered and was skipped). The frame is ~37 KB because it is mostly solid blue, so the 30 KB floor below admits it.

Start is tapped once (ace#3064). A retryTapIfNoChange tap re-taps while start_learn_app is still in flight, and the second callback crashes CommCare 2.64.0 (ConnectJobIntroFragment.java:161, the ace#2584 stack). If the device still lands off the download path, the recipe recovers on its own: the Job Card's DOWNLOAD LEARN APP gate (connect_learning_button) is tapped once, and a crash back to the job list is recovered with Resume on the OPP_NAME tile, then DOWNLOAD LEARN APP. Validated live on 2026-10-17 (worker-1, opp 20260730-1718): a single tap, no CommCare crash, learn-install captured, Learn home reached.

Step 4.5: Sweep the device-video spool

Sweep the device-video spool. Local mobile_run_recipe calls record an mp4 per run and spool a copy for this session.

  1. Call mobile_list_session_videos (no arguments). It returns { spoolDir, videos: [<absolute path>, …] }. Use the atom — do NOT hand-resolve ~/.ace/mobile-videos/<ppid>/ (the ppid belongs to the MCP process, not to you) and do NOT glob mobile-videos/*/, which would read and then destroy a CONCURRENT session's spool.
  2. Upload each returned file to ACE/_common/connect-screenshots/<version>/videos/_device/<filename> via drive_upload_binary (mimeType: "video/mp4"). This skill uploads no videos from result.videos[], so there is nothing to de-duplicate against here — upload everything the atom returns.
  3. Call mobile_clear_session_videos (no arguments) to clear the spool. It returns { spoolDir, cleared } — log cleared.

Empty spool is normal — recording is best-effort and ACE_MOBILE_RECORD=off disables it.

Step 5: Upload to Drive

For each captured PNG mapped to a deck alias (see Coverage table above for the canonical mapping):

  1. Verify file size > 30 KB (lowered from 100 KB — learn-install is legitimately ~38 KB due to a mostly-blue Downloading dialog). PNGs below 30 KB are almost certainly corrupt.
  2. Upload via drive_upload_binary({ mimeType: "image/png", shareAnyoneWithLink: true }). The anyone-with-link flag is REQUIRED for Slides createImage ingest. See app-screenshot-capture Step 5 for the canonical explanation.
  3. Target path: ACE/_common/connect-screenshots/<version>/<alias>.png.

For each alias in the Coverage table marked Fixture:

  1. Read templates/training-deck/_common/fixtures/<alias>.png from the repo (committed by an operator after a one-time manual capture).
  2. Upload to the same Drive path as a live capture.
  3. If the fixture file is missing, write the alias entry with placeholder: true and note: "Awaiting manual capture" — the manifest still records the gap so the deck-render skill emits a visible placeholder slot instead of failing silently.

Step 5.4: Composite the opp-bearing frames (ace#3060)

connect-home and claim-opp always show some real program: the test worker's invites are real ACE runs. A frame showing one program's name cannot go on every program's deck (the 2026-05-26 audit). So publish them composited: the real capture from Step 4, with only the opp-specific strings replaced. Illustration only. collectCaptureEntries refuses a composited frame in any evidence manifest.

  1. Pull the font the device renders with: adb -s <serial> pull /system/fonts/Roboto-Regular.ttf <dir>/ (CommCare bundles no fonts).

  2. Write or update templates/training-deck/_common/composites/connect-<version>.yaml. Pin the base capture's sha256 and the font's sha256; every text element in the capture's UI dump must be a keep rule (generic chrome) or a replace rule. Measure font_px/line_px from the original, and make each replacement fill as many lines as the original did (the compositor never moves pixels).

  3. Render each frame:

    ACE_ROOT="${CLAUDE_PLUGIN_ROOT:-$(python3 -c "import json,os; d=json.load(open(os.path.expanduser('~/.claude/plugins/installed_plugins.json'))); print(d['plugins']['ace@ace'][0]['installPath'])")}"
    node "$ACE_ROOT/node_modules/tsx/dist/cli.mjs" "$ACE_ROOT/scripts/composite-pool-frame.ts" \
      --spec "$ACE_ROOT/templates/training-deck/_common/composites/connect-<version>.yaml" \
      --frame connect-home --base <capture.png> --dump <capture.xml> \
      --font <dir>/Roboto-Regular.ttf --out <poolDir>/connect-home.png
    

    It refuses on a base or font hash mismatch, or on any uncovered text element. An APK that adds a string therefore fails here rather than leaking it.

  4. Look at every output beside its base. The checks make it generic; only eyes make it look right.

  5. Upload the base captures to <version>/_base/ (not shared; they show real run names). Write the manifest entry as source: composited with composited_from from the script's .provenance.json.

Step 5.5: Pool distinctness gate (ace#1832)

Before the manifest is written, and before ANY alias is published as source: live. The cross-opp sibling of app-screenshot-capture Step 5.5, with a different remedy — see below for why.

  1. Hash every asset headed for the pool, live and fixture alike, with ONE digest for the whole pool:

    shasum -a 256 <poolDir>/*.png     # or: md5 -q <poolDir>/*.png
    
  2. Pass every asset as { alias, digest, source } to classifyPoolDistinctness in lib/screenshot-pool-distinctness.ts. Do not hand-roll the comparison — the helper carries the reasoning and the test carries the controls.

  3. verdict: 'fail' is a HARD FAIL of this step, not a warn. For every alias in report.quarantine:

    • do NOT publish it as source: live;
    • write it into the manifest as source: fixture, placeholder: true with note: "<alias> byte-identical to <other> — see ace#1832", so the deck emits a visible empty slot;
    • emit the matching describePoolCollisions line into auto_surfaced.
  4. Then read the recipes and find which alias is lying. The helper deliberately elects no winner (a pool has no ordering that could justify one), so this is the human/agent step. Every instance so far has had the same recipe-shaped cause: a takeScreenshot placed before the action that would make the surface distinct. Fix the recipe, re-capture, and only then un-quarantine.

Why REJECT and not duplicate_of. app-screenshot-capture marks a byte-identical journey frame duplicate_of: <canonical-step> and lets downstream cite the canonical one — correct there, because two steps genuinely observed one moment. A pool alias is a semantic promise, not a step: @sync-button means "a picture of the sync control". Redirecting it to the connect-home frame IS the defect (ace#866's class — "downstream slides claim things the duplicate can't show"; ace#1832 cited this as "#867's caption-contradicts-pixels class", but #867 is the camera-only HQ-setting residual, a different defect), not the fix. So the pool rejects; it never redirects.

Step 6: Write manifest.yaml

connect_apk_version: "2.63.0"
captured_at: "2026-05-24T15:42:36Z"
captured_by: "ace@dimagi-ai.com"
source_avd: "ACE_Pixel_API_34"
source_opportunity:
  slug: "<forked-slug>"
  run_id: "<forked-run-id>"
  opportunity_id: "<uuid>"

screenshots:
  # Live captures from recipes
  commcare-welcome:    { drive: "<fileId>", source: live,    recipe: "04-personal-id.yaml" }
  connect-home:        { drive: "<fileId>", source: live,    recipe: "00-connect-home.yaml" }
  sync-button:         { drive: "<fileId>", source: live,    recipe: "03-sync-button.yaml" }
  claim-opp:           { drive: "<fileId>", source: live,    recipe: "01-claim-opp.yaml" }
  learn-install:       { drive: "<fileId>", source: live,    recipe: "02-learn-install.yaml" }
  personal-id-start:   { drive: "<fileId>", source: live,    recipe: "04-personal-id.yaml" }
  personal-id-phone:   { drive: "<fileId>", source: live,    recipe: "04-personal-id.yaml" }
  personal-id-name:    { drive: "<fileId>", source: live,    recipe: "04-personal-id.yaml" }
  # Fixture aliases (committed PNGs OR placeholder gaps)
  personal-id-verify:  { drive: "<fileId>", source: fixture, note: "Demo +7426 phones bypass OTP; static fixture from real-OTP user flow" }
  personal-id-photo:   { drive: "<fileId>", source: fixture, note: "Recovery returns existing photo; static fixture from fresh-signup user flow" }
  personal-id-id:      { drive: "<fileId>", source: fixture, note: "Awaiting confirmation this screen exists in current APK" }
  personal-id-location:{ drive: "<fileId>", source: fixture, note: "Recovery caches permission; static fixture from fresh-signup user flow" }
  personal-id-done:    { drive: "<fileId>", source: fixture, note: "Recovery shows 'Account Recovered'; deck needs 'Profile complete!' equivalent" }
  play-store-search:   { drive: "<fileId>", source: fixture, note: "Play Store requires Google sign-in; out of scope for automation" }
  commcare-install:    { drive: "<fileId>", source: fixture, note: "Same" }
  commcare-open:       { drive: "<fileId>", source: fixture, note: "Same" }

Upload the manifest via drive_create_file (mimeType text/yaml).

Aliases

The manifest keys MUST match the aliases used in templates/training-deck/_common/platform-setup.yaml. The platform-setup module references these exact aliases via @<alias> syntax in its slide definitions. Any mismatch causes the training-deck-render skill to emit a placeholder instead of a screenshot.

Current required aliases (16):

AliasTemplate slideFlow
play-store-searchinstall-commcareInstall
commcare-installinstall-commcareInstall
commcare-openinstall-commcareInstall
commcare-welcomeinstall-commcareInstall
personal-id-startpersonal-id-startPersonalID
personal-id-namepersonal-id-startPersonalID
personal-id-phonepersonal-id-startPersonalID
personal-id-verifypersonal-id-startPersonalID
personal-id-photopersonal-id-detailsPersonalID
personal-id-idpersonal-id-detailsPersonalID
personal-id-locationpersonal-id-detailsPersonalID
personal-id-donepersonal-id-detailsPersonalID
connect-homeconnect-homeNavigation
claim-oppclaim-opportunityNavigation
learn-installinstall-learnNavigation
sync-buttonsyncingSyncing

Self-eval

Five criteria. verdict: pass requires all five; verdict: warn acceptable when only gaps flags fire (live recipe failures and missing fixtures); verdict: fail when live captures violated quality/sharing/distinctness rules.

  1. Coverage: All 16 required aliases present in manifest (even if source: fixture with placeholder: true). FAIL if any missing.
  2. Live capture quality: All source: live PNGs ≥ 30 KB (lowered from 100 KB — learn-install is legitimately ~38 KB due to a mostly-solid-blue Downloading dialog). FAIL if any below threshold.
  3. Sharing: All files set to anyone-with-link. FAIL if any not shared (Slides image import will fail with "image cannot be reached").
  4. Gaps (warn-only): source: fixture entries with placeholder: true (no actual PNG committed yet). Warns the operator that a one-time manual capture is still needed for the deck to render fully.
  5. Distinctness: classifyPoolDistinctness (Step 5.5) returns verdict: 'pass' — no two aliases resolve to the same bytes. FAIL on any collision. Existence, size and sharing are all satisfied by a duplicate; only this criterion can tell you an alias is showing someone else's screen (ace#1832).

Write verdict to ACE/_common/connect-screenshots/<version>/verdict.yaml:

skill: common-screenshot-capture
target: _common
ran_at: <ISO timestamp>
connect_apk_version: "<version>"

overall_score: 8.5           # 0.0–10.0
verdict: pass | warn | fail

dimensions:
  coverage:           { score: 10.0, weight: 0.30 }  # 16/16 aliases present (live or fixture)
  live_capture_quality: { score: 9.0, weight: 0.30 } # all live PNGs >= 30 KB
  sharing:            { score: 10.0, weight: 0.20 }  # all uploaded with anyone-with-link
  gaps:               { score: 6.0,  weight: 0.20 }  # 8 live / 8 fixture; 0 placeholder

per_item:
  - ref: "commcare-welcome"
    source: live
    score: 10
    verdict: pass
    note: "111 KB, shared, captured from authentic fresh-install state"
  # ... one per alias

auto_surfaced:
  - severity: WARN
    message: "5 PersonalID + 3 install-flow aliases sourced from operator-committed fixtures; 0 placeholder gaps remaining."

Output

  • Screenshots in ACE/_common/connect-screenshots/<version>/
  • manifest.yaml in the same folder
  • verdict.yaml in the same folder

MCP tools used

  • ace-mobile: mobile_ensure_avd_running, mobile_install_apk, mobile_run_recipe
  • ace-gdrive: drive_create_folder, drive_upload_binary, drive_create_file, drive_set_anyone_with_link

Mode behavior

  • Auto: run all recipes, upload all PNGs, write manifest + verdict.
  • Review: show the connect-apk-version + recipe list before running; pause for confirmation.
  • Dry-run: run recipes locally (capturing PNGs to /tmp) but skip the Drive upload. State tracks dry-run-success.

Failure modes

  • Any mobile_run_recipe failure → read the forensics first. On a recipe status: 'fail' (or a thrown driver-death failure, where the artifacts ride on error.failureForensics), Read failureForensics.screenshotPath + .uiDumpPath before writing a verdict or escalating. Canonical contract: playbook/integrations/mobile-integration.md § Failure forensics.
  • AVD not running / test user not signed in. Halt with a pointer at /ace:mobile-bootstrap.
  • Step 0 fork fails (ACE_WEB_PAT_TOKEN invalid/missing). Halt with remediation /ace:ace-web-pat-mint. Without a fresh forked opp, claim-opp + learn-install captures may target stale broken invites.
  • Step 4a fails on "Enable Google Play services" dialog. GMS prep step (adb shell pm enable com.google.android.gms) was skipped or ineffective. Re-run the prep + retry recipe.
  • personal-id-name doesn't render (recipe completes but no personal-id-name.png captured). The active ${ACE_E2E_PHONE} was on a snapshot-reload path that skipped the Name screen. Rotate to a fresh pool test worker (skills/test-worker-pool) OR commit a fixture.
  • claim-opp / learn-install recipe times out OR hits "application invalid". Forked OPP_NAME points at a stale build. Re-fork from a more recent successful run (Step 0).
  • Recipe selector mismatch (Connect APK rebuilt with new resource-ids). Surface the failing recipe + step. Operator runs maestro studio to re-calibrate selectors in mcp/mobile/selectors/connect-<version>.yaml before re-running.
  • Drive upload fails (Shared-Drive guard). Verify ACE/_common/ lives on a Shared Drive; SA quota is 0 in My Drive.
  • Screenshot < 30 KB. Likely a blank or corrupt capture (the learn-install mid-flight dialog is the only known sub-100KB legitimate capture; everything else >100KB).

Change log

DateChangeAuthor
2026-05-23Initial version. Focused common-screenshot skill for training deck common modules, aligned to platform-setup.yaml alias contract. Complements connect-baseline-screenshots (broader baseline) and app-screenshot-capture (per-opp).ACE team
2026-05-24Live-recipe baseline shipped. 5 navigation+sync recipes (00-connect-home, 01-claim-opp, 02-learn-install, 03-sync-button) + 1 PersonalID recipe (04-personal-id) drive 8 of 16 alias captures end-to-end. SKILL.md rewritten with explicit per-recipe orchestration, Step 0 /ace:fork-run integration for deterministic OPP_NAME pinning, GMS-enable prerequisite, lowered 30KB quality threshold (was 100KB) to admit the legitimately-small learn-install mid-flight capture, and per-alias `source: livefixturemanifest schema withplaceholder: true` warn-only gap reporting. 8 fixture aliases (5 PersonalID unreachable + 3 Play Store auth-blocked) documented in templates/training-deck/_common/fixtures/README.md. (0.13.361)
2026-09-06Pool-distinctness gate + sync-button quarantined (dimagi-internal/ace#1832). The pool published two aliases resolving to ONE image: sync-button was a byte-identical copy of connect-home (md5 4d1c205591270cc4638b439c3a9981ff, 242,393 bytes, 1080x2400, both fetched unauthenticated 2026-09-06 and cmp-identical). Not a flake — 03-sync-button.yaml fires its takeScreenshot BEFORE its own tapOn: action_sync, from a pre-state its header declares identical to 00-connect-home.yaml's post-state, so it reproduces on every capture. The four existing self-eval criteria were all satisfied by the duplicate (it exists, it is >30KB, it is shared) — existence and distinctness are different properties. New Step 5.5 hashes every asset and gates on classifyPoolDistinctness (lib/screenshot-pool-distinctness.ts, hard FAIL, never a redirect — a pool alias is a semantic promise, so duplicate_of is the defect not the fix), new self-eval criterion 5, and sync-button marked QUARANTINED in the Coverage table until its recipe is repaired and re-validated on a device.ACE team
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 197kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall