connect-baseline-screenshots

Capture per-version Connect UI navigation screenshots as indexed PNG assets with a manifest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the wasted effort of re-capturing identical Connect navigation screenshots for every new ACE opportunity's training deck, which consumes unnecessary AVD time and resources whenever the Connect APK updates or common UI elements change.

Core Features & Use Cases

  • Shared Baseline Capture: Captures standard Connect UI flow screenshots (sign-in, opportunity list, claim, sync, payments, settings etc.) that are identical across all ACE opportunities, stored in a shared common assets folder for reuse.
  • Quality Validation: Generates a self-evaluation verdict that checks screenshot quality, selector stability, and version metadata accuracy against a 7.0/10 threshold.
  • Use Case: When the Connect Android APK ships a new version with UI changes, run this Skill once to update the shared screenshot library instead of re-capturing the same 20+ navigation screenshots for every new ACE opportunity.

Quick Start

Use the connect-baseline-screenshots skill to capture the latest baseline Connect navigation screenshots for the current APK version and upload them to the shared common assets folder for use in all ACE training decks.

Frequently Asked Questions about connect-baseline-screenshots

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

FAQPage Schema
How do I automate screenshot capture for Android training decks when the APK updates?

Capture baseline screenshots by running an automated capture flow against the Connect Android APK to generate indexed PNG assets of common navigation screens. This produces a shared library and a manifest file for downstream training deck generation, eliminating redundant manual capture per opportunity.

What are baseline screenshots and when do I need them for ACE workflows?

Baseline screenshots are standardized captures of common Connect UI navigation flows like sign-in, sync, and payments. You need them in ACE workflows whenever the Connect Android APK is updated, UI elements are rebranded, or new surfaces are added to the shared training library.

How do I validate screenshot quality and selector stability after capturing UI navigation flows?

Validate screenshot quality through a self-evaluation verdict that checks selector stability, screenshot quality, and version metadata accuracy against a 7.0/10 threshold. This verdict is generated automatically alongside the indexed PNG assets and manifest file during the capture process.

Can I reuse navigation screenshots across multiple ACE opportunities to save AVD time?

You can reuse navigation screenshots across multiple ACE opportunities by capturing them once into a shared common assets folder. This shared baseline approach eliminates wasted AVD time and resources spent re-capturing identical Connect UI flows for every new training deck.

What's the best way to update training deck screenshots after a Connect Android APK rebrand?

The best way to update training deck screenshots after a rebrand is to run a baseline capture workflow once against the new APK. It produces a refreshed set of indexed PNG assets and a manifest file, automatically updating the shared library for all downstream ACE training decks.