# Test Apk

> Verify a requested 5chan Android APK interaction or diagnose a specific emulator/upload failure.

- Skill: `bitsocialnet/test-apk-2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add bitsocialnet/test-apk-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bitsocialnet/test-apk-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bitsocialnet (https://skillmd.com/u/bitsocialnet)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bitsocialnet/test-apk-2

---


<!-- Generated from .agents/skills/test-apk/SKILL.md; run yarn ai-workflow:sync. -->

# Android APK Verification

Establish the requested flow, code/APK version, device, and acceptance criteria. A small check can stay local; delegate a substantial independent flow to the available `test-apk` role when useful, with the same scope and evidence requirements.

Read [device ownership](references/device-ownership.md) when selecting, starting, or reusing an emulator. Read [platform procedures](references/platform.md) for build/install commands, instrumentation, or upload diagnosis. Build only when needed to test the intended code, and coordinate heavyweight work with the verification owner.

Verify the interaction itself and report device/build status, observed behavior, relevant diagnostics, and artifact paths. Preserve existing devices and data; clean up task-owned resources. Retain existing authorization without extra pauses, while keeping live uploads and content publication within the requested scope.

Use `docs/agent-playbooks/verification.md` for any broader check selection. Do not run a second full verification chain or modify application code merely because this testing skill was selected.