Skip to content

poll-poll134/android-blackbox-analysis-skill

android-app-blackbox-competitive-analysis

Verified

Use 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.

FileKindSize
SKILL.mdskill md3.2 KB
examples/sanitized-complete-example/README.en.mdmarkdown2.0 KB
examples/sanitized-complete-example/README.mdmarkdown1.8 KB
examples/sanitized-complete-example/analysis/capability-matrix.csvother1.3 KB
examples/sanitized-complete-example/analysis/system-interface-evidence.csvother1.2 KB
examples/sanitized-complete-example/evidence/screen-summaries/DEMO-0001_empty-home.mdmarkdown254 B
examples/sanitized-complete-example/evidence/screen-summaries/DEMO-0002_app-picker.mdmarkdown253 B
examples/sanitized-complete-example/evidence/screen-summaries/DEMO-0003_instance-created.mdmarkdown254 B
examples/sanitized-complete-example/evidence/screen-summaries/DEMO-0004_instance-menu.mdmarkdown249 B
examples/sanitized-complete-example/evidence/screen-summaries/DEMO-0005_permission-diagnostics.mdmarkdown463 B
examples/sanitized-complete-example/indexes/control_coverage.csvother1.7 KB
examples/sanitized-complete-example/indexes/coverage_gaps.csvother1.2 KB
examples/sanitized-complete-example/indexes/interface_index.csvother1.1 KB
examples/sanitized-complete-example/indexes/screenshot_index.csvother1.4 KB
examples/sanitized-complete-example/input/capture-plan.csvother638 B
examples/sanitized-complete-example/input/scope.en.mdmarkdown849 B
examples/sanitized-complete-example/input/scope.mdmarkdown760 B
examples/sanitized-complete-example/reports/final-report.en.mdmarkdown3.6 KB
examples/sanitized-complete-example/reports/final-report.mdmarkdown3.1 KB
references/analysis-guide.mdmarkdown2.0 KB
references/evidence-model.mdmarkdown1.9 KB
scripts/build_indexes.mjsexecutablescript6.8 KB
scripts/capture_evidence.shexecutablescript4.8 KB
scripts/image_info.pyexecutablescript1.3 KB
scripts/init_case.shexecutablescript1.3 KB
scripts/package_release.pyexecutablescript2.6 KB
scripts/redact_check.mjsexecutablescript3.1 KB
scripts/scroll_sweep.shexecutablescript2.5 KB
scripts/smoke_test.shexecutablescript1.8 KB
scripts/tap_ui.shexecutablescript1.3 KB
scripts/ui_pick.pyexecutablescript1.9 KB
scripts/validate_example.mjsexecutablescript12.2 KB
scripts/validate_skill.mjsexecutablescript2.6 KB
templates/capability-matrix.csvother126 B
templates/report-template.mdmarkdown1.2 KB
templates/system-interface-evidence.csvother120 B

references/analysis-guide.md

View on GitHub
# Analysis Guide

## Scope first

Write `scope.md` before interacting with the app:

- designated ADB target;
- app package and version;
- allowed accounts and test data;
- actions requiring user participation;
- destructive or paid actions excluded;
- unavailable hardware or network prerequisites.

## Capability map

Organize findings as product capabilities rather than a list of taps. Typical capability families:

- first launch and privacy choices;
- navigation, search, and content discovery;
- creation and configuration;
- item lifecycle and batch management;
- data backup, restore, migration, and deletion;
- permissions, notifications, background behavior, and system settings;
- security, credentials, and privacy protections;
- accounts, entitlements, support, and legal disclosures;
- external content and Android system integration.

Keep interaction details in the evidence index. The final capability table should remain decision-friendly.

## Runtime boundary

Use Android commands to observe package, task, process, permission, AppOps, storage, and component state. Do not convert a process name, task label, or UI claim into proof of a separate operating system, kernel, hardware identity, or security boundary.

When traffic is encrypted, record only what is directly supported: destination visibility, component launch, WebView use, or network capability. Do not invent endpoint parameters or response schemas.

## Coverage review

For each capability, check:

- entry state;
- prerequisite state;
- primary success path;
- cancel/back path;
- error or blocked state;
- persistence after restart when relevant;
- Android runtime state when relevant;
- untested or excluded boundary.

Stop expanding only when every known capability has an evidence status, not when every control has been clicked.

## Comparison output

Use one row per capability package:

| Capability | Product A | Product B | Difference | Recommendation | Priority |
|---|---|---|---|---|---|

Keep screenshots, controls, and exact interactions in supporting indexes rather than the meeting table.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall