poll-poll134/android-blackbox-analysis-skill
android-app-blackbox-competitive-analysis
VerifiedUse when users request Android competitor research, systematic feature or interface mapping, evidence screenshots, interaction coverage, comparison-ready product dossiers, or Android system-boundary verification without APK decompilation.
examples/sanitized-complete-example/reports/final-report.en.md
View on GitHub# Sample Clone Manager Black-Box Analysis Example
> Status: complete synthetic public example. This report does not describe a real product and must not be cited as factual evidence about any app capability or defect.
## Executive Summary
- `[OBSERVED][SYNTHETIC]` The example covers five states from an empty home screen through app selection, creation result, card menu, and permission diagnostics (`DEMO-0001` through `DEMO-0005`).
- `[COMPUTED]` The public directory contains five text screen summaries with reproducible SHA-256 hashes, five screenshot-index rows, fourteen synthetic control rows, and ten coverage gaps.
- `[NOT_TESTED]` No device was connected, no APK was installed or run, and no login, payment, runtime isolation, or system-setting change was verified.
## Scope and Exclusions
- Subject: fictional `Sample Clone Manager`, package `com.example.clone`.
- Allowed: demonstrate how a free creation path, card menu, and diagnostics are structured.
- Excluded: payment, real login, account deletion, external messaging, external installation, and real permission changes.
- Unavailable: camera, paid membership, and a real account.
- Freeze point: `DEMO-0005`.
## Feature and Screen Loops
### Create One Instance
`[OBSERVED][SYNTHETIC]` The empty home exposes Add app (`DEMO-0001`); the app picker shows Sample Notes and Create (`DEMO-0002`); the result shows `Sample Notes · 0` in a Ready state (`DEMO-0003`). This forms an example entry-selection-result loop.
### Manage an Instance
`[OBSERVED][SYNTHETIC]` The card exposes More actions (`DEMO-0003`), and the menu lists Start, Stop, Rename, Backup, Delete, and Cancel (`DEMO-0004`). The example supports only the menu information structure. It does not prove successful actions, and Delete was not executed.
### Permission Diagnostics
`[OBSERVED][SYNTHETIC]` Diagnostics distinguish notifications allowed, location not granted, and camera unavailable in the environment (`DEMO-0005`). One custom-rendered row lacks hierarchy coverage, so control coverage remains partial.
## Android Runtime and External Interfaces
`[NOT_TESTED]` There is no real package, Activity, process, UID, AppOps, permission, or system Intent evidence. A visible settings entry does not prove that a system page opened or that permission state changed. Pending checks are recorded in `analysis/system-interface-evidence.csv`.
## Strengths and Limitations
The synthetic information architecture demonstrates a short first-instance path, stable instance ID, grouped lifecycle actions, and a distinction between denied and environmentally unavailable permissions. These are example-design conclusions, not competitor facts.
The main limitations are the absence of raw screenshots and UI XML, runtime evidence, and real interaction outcomes; the unavailable camera; and untested login and payment. The example cannot support judgments about real product quality, isolation strength, or backend success.
## Coverage Conclusion
| Capability package | Status | Evidence |
|---|---|---|
| First-instance creation | Synthetic example loop | `DEMO-0001`–`DEMO-0003` |
| Card management menu | Entry and options only | `DEMO-0003`, `DEMO-0004` |
| Permission diagnostics | Partial coverage | `DEMO-0005` |
| Real account | Not tested | scope |
| Payment | Out of scope | scope |
| Android runtime isolation | Not tested | system interface evidence |
Conclusion: this directory fully demonstrates cross-references among input, evidence IDs, interface and control indexes, coverage gaps, capability synthesis, system boundaries, and a final report. It does not replace a real authorized analysis.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |