skills.rest
bitsocialnet
bitsocialnetOFFICIAL
Explore all skills by this author →
Website𝕏@bitsocialnetGitHub

test-apk

Delegate Android wrapper testing to a dedicated subagent with logcat diagnostics.

1|1|Updated Feb 1, 2026
Search Tags:#testing#diagnostics#android#emulator#wrapper#webview
One-click install
npx skills add https://github.com/bitsocialnet/bitsocial-web --skill test-apk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-apk
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/test-apk
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill test-apk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates Android wrapper testing to a dedicated test-apk subagent to keep the main context clean.

Core Features & Use Cases

  • Delegates Android tests to a dedicated subagent for wrapper environments.
  • Guides on gathering requirements, delegating steps, building and installing, running tests, and capturing diagnostics for Android wrappers (WebView shells, TWAs) on local emulators or connected devices.

Quick Start

Tell the test-apk subagent to run a smoke test on the connected emulator.

Frequently Asked Questions about test-apk

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

FAQPage Schema
How do I run Android wrapper tests on a local emulator without cluttering the main context?▼

Android wrapper testing can be delegated to a dedicated test-apk subagent that handles builds, installations, and diagnostics independently, keeping your main context clean while executing tests on connected devices or emulators.

What is the best way to debug WebView or TWA issues on an Android emulator?▼

Debugging WebView or TWA issues is handled by delegating focused tests to a subagent that coordinates environment checks and captures logcat diagnostics to isolate problems within the Android wrapper environment.

Do I need a connected device or emulator to test Android wrappers?▼

Yes, testing Android wrappers requires an available emulator or connected device, along with a wrapper project root, App/package id, and build/install commands provided by the parent agent.

How do I capture logcat diagnostics during Android wrapper testing?▼

Logcat diagnostics are captured by the subagent during focused test execution on the emulator or connected device, coordinating environment checks to isolate wrapper-specific runtime issues and errors.

Can I use this for testing Android WebView shells and Trusted Web Activities?▼

Yes, this approach supports testing Android wrappers including WebView shells and Trusted Web Activities by guiding the subagent through gathering requirements, building, installing, and running smoke tests on emulators.

Why does delegating Android tests to a subagent keep the context clean?▼

Delegating Android tests to a subagent isolates the verbose build, install, and diagnostic output from the main context, allowing the parent agent to receive only summarized results without context pollution.

Related Skills

Explore More Software Engineering Skills→
luigiinredluigiinred
1

build-android-app

Build, install, and launch an Android app on a detected emulator.

Community
Advanced
AniTrendAniTrend
51

adb-device-workflow

Automate Android device connection and debug APK installation via ADB.

Official
Intermediate
philo-grovesphilo-groves
12

maxtac-android-runtime-debugging

Capture Android runtime evidence via ADB, logcat, JDWP, and Frida.

Community
Advanced
MadAppGangMadAppGang
278

claudish-usage

Routes Cubist CLI tasks through sub-agents to prevent context window pollution.

Official
Advanced