How do I install the Prepare Site Breakage Triage Repro Build skill?

Run npx skillmds@latest add duckduckgo/prepare-site-breakage-triage-repro-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Prepare Site Breakage Triage Repro Build safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Prepare Site Breakage Triage Repro Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Prepare Site Breakage Triage Repro Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Prepare Site Breakage Triage Repro Build?

duckduckgo (@duckduckgo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Prepare Site Breakage Triage Repro Build by duckduckgo

Name: Prepare Site Breakage Triage Repro Build
Author: duckduckgo

Prepare Site Breakage Triage Repro Build

Build, install, launch, screenshot, and cleanup mechanics for automated reproduction of site breakage on Cursor self-hosted Android agents in `ddg-native-android`. Use when setting up a device for automated site breakage triage repro runs.

duckduckgo Updated Sep 17, 2026

File contents

Build and install

Use npm run android:build for build smoke.
Use npm run android:install when the target AVD does not already have DDG installed.
If an emulator restart loses the install but the APK exists, reinstall with:

adb install -r android/app/build/outputs/apk/internal/debug/<apk-name>

Emulator

Default to ddg_pixel9_api35 as a known-good AVD.
Start headlessly with explicit software GPU rendering:

emulator -avd ddg_pixel9_api35 -no-window -no-snapshot-save -no-boot-anim -gpu swiftshader

If the emulator crashes, disappears from ADB, or fails to capture screenshots, retry once with:

emulator -avd ddg_pixel9_api35 -no-window -no-snapshot-save -no-boot-anim -gpu lavapipe

Record the GPU mode used in the required output. Keep the proxy, URL, app package, and screenshot workflow unchanged between attempts.

ADB reliability

Wrap long or failure-prone ADB calls with timeout, especially screencap, dumpsys, uiautomator, and clean up adb shell commands.
If a retry starts another AVD, use explicit serial targeting for all later commands:

adb -s <serial> ...

Load URL

Use the debug package explicitly:

adb shell am start -W -a android.intent.action.VIEW -d '<url>' com.duckduckgo.mobile.android.debug

Screenshots

Prefer device-file screenshots; avoid adb exec-out screencap -p because it may hang.

adb shell screencap -p /sdcard/screenshot_initial.png
adb pull /sdcard/screenshot_initial.png /opt/cursor/artifacts/<dir>/screenshot_initial.png

System UI recovery

If screenshots are blocked by Application Not Responding: com.google.android.apps.nexuslauncher, verify DDG is foreground/responsive first.

adb shell input keyevent BACK
adb shell am force-stop com.google.android.apps.nexuslauncher

Then relaunch the URL activity and report the cleanup in the required output.

Runtime configuration cleanup

Remove /data/local/tmp/webview-command-line from every AVD touched
Force-stop DDG, then stop emulators

---name: prepare-site-breakage-triage-repro-builddescription: Build, install, launch, screenshot, and cleanup mechanics for automated reproduction of site breakage on Cursor self-hosted Android agents in `ddg-native-android`. Use when setting up a device for automated site breakage triage repro runs.---## Build and install- Use `npm run android:build` for build smoke.- Use `npm run android:install` when the target AVD does not already have DDG installed.- If an emulator restart loses the install but the APK exists, reinstall with:```shadb install -r android/app/build/outputs/apk/internal/debug/<apk-name>```## Emulator- Default to `ddg_pixel9_api35` as a known-good AVD.- Start headlessly with explicit software GPU rendering:```shemulator -avd ddg_pixel9_api35 -no-window -no-snapshot-save -no-boot-anim -gpu swiftshader```If the emulator crashes, disappears from ADB, or fails to capture screenshots, retry once with:```shemulator -avd ddg_pixel9_api35 -no-window -no-snapshot-save -no-boot-anim -gpu lavapipe```Record the GPU mode used in the required output. Keep the proxy, URL, app package, and screenshot workflow unchanged between attempts.### ADB reliability- Wrap long or failure-prone ADB calls with `timeout`, especially `screencap`, `dumpsys`, `uiautomator`, and clean up `adb shell` commands.- If a retry starts another AVD, use explicit serial targeting for all later commands:```shadb -s <serial> ...```## Load URLUse the debug package explicitly:```shadb shell am start -W -a android.intent.action.VIEW -d '<url>' com.duckduckgo.mobile.android.debug```## ScreenshotsPrefer device-file screenshots; avoid `adb exec-out screencap -p` because it may hang.```shadb shell screencap -p /sdcard/screenshot_initial.pngadb pull /sdcard/screenshot_initial.png /opt/cursor/artifacts/<dir>/screenshot_initial.png```## System UI recoveryIf screenshots are blocked by `Application Not Responding: com.google.android.apps.nexuslauncher`, verify DDG is foreground/responsive first.```shadb shell input keyevent BACKadb shell am force-stop com.google.android.apps.nexuslauncher```Then relaunch the URL activity and report the cleanup in the required output.## Runtime configuration cleanup- Remove `/data/local/tmp/webview-command-line` from every AVD touched- Force-stop DDG, then stop emulators

Frequently asked questions