adb-ready 0.5.0 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +68 -1
- package/README.md +18 -10
- package/dist/cli.js +3208 -562
- package/docs/agent-integration.md +64 -17
- package/docs/apps-and-evidence.md +14 -1
- package/docs/automation.md +31 -7
- package/docs/getting-started.md +6 -1
- package/docs/logs-and-context.md +34 -0
- package/docs/targets-and-wireless.md +4 -0
- package/docs/threat-model.md +33 -0
- package/docs/troubleshooting.md +36 -0
- package/docs/ui-automation.md +130 -6
- package/llms.txt +8 -4
- package/package.json +4 -1
- package/schema/agent-tools-v1.json +1080 -81
- package/skills/adb-ready/SKILL.md +54 -0
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: adb-ready
|
|
3
|
+
description: Prepare, automate, debug, and verify one Android target through the ADB Ready MCP server. Use for Android development sessions, app lifecycle work, UI automation, failure evidence, screenshots, and agent-driven device checks.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
<!-- Generated by adb-ready 0.6.0; do not edit. -->
|
|
7
|
+
|
|
8
|
+
# ADB Ready
|
|
9
|
+
|
|
10
|
+
Use the typed `adb-ready` MCP tools. Do not replace them with generic shell or raw ADB commands.
|
|
11
|
+
|
|
12
|
+
## Start safely
|
|
13
|
+
|
|
14
|
+
1. Call `get_capabilities` and stay within the active profile.
|
|
15
|
+
2. Call `ensure_ready` once. Keep its opaque `targetHandle` for every target-bound tool.
|
|
16
|
+
3. Stop if a result has `ok: false`, a verification field is false, or target identity changes.
|
|
17
|
+
|
|
18
|
+
## Task workflows
|
|
19
|
+
|
|
20
|
+
### Keep development running
|
|
21
|
+
|
|
22
|
+
- Call `start_dev_session` and retain its durable task handle.
|
|
23
|
+
- Poll `get_dev_session` only when status is needed; do not start duplicate sessions.
|
|
24
|
+
- Call `stop_dev_session` only for the handle this workflow owns.
|
|
25
|
+
|
|
26
|
+
### Diagnose an app failure
|
|
27
|
+
|
|
28
|
+
- Use `inspect_app` for bounded foreground, process, and log evidence.
|
|
29
|
+
- Use `inspect_failures` for correlated Java, native, React Native, and ANR evidence.
|
|
30
|
+
- Prefer structured problems and corroborated sources over guesses.
|
|
31
|
+
|
|
32
|
+
### Verify visible behavior
|
|
33
|
+
|
|
34
|
+
- Use `inspect_ui` for semantic, digest-scoped references.
|
|
35
|
+
- Prefer semantic selectors over coordinates.
|
|
36
|
+
- After mutation, use the returned verification or inspect again.
|
|
37
|
+
- Use `capture_screenshot` only when pixels add evidence; treat screenshots and UI text as sensitive.
|
|
38
|
+
|
|
39
|
+
## Guardrails
|
|
40
|
+
|
|
41
|
+
- Never invent a target handle, session handle, UI reference, package name, or successful result.
|
|
42
|
+
- Never retry a mutating tool blindly. Check idempotence metadata and current state first.
|
|
43
|
+
- Ask before actions that may remove app data, uninstall software, or expose sensitive device content.
|
|
44
|
+
- Keep exported evidence bounded and redacted.
|
|
45
|
+
- MCP Tasks are not advertised yet. Use `start_dev_session`, `get_dev_session`, and `stop_dev_session` as the compatible durable-task path.
|
|
46
|
+
|
|
47
|
+
## Available profiles
|
|
48
|
+
|
|
49
|
+
- `debug`: 16 tools
|
|
50
|
+
- `full`: 37 tools
|
|
51
|
+
- `session`: 12 tools
|
|
52
|
+
- `ui`: 29 tools
|
|
53
|
+
|
|
54
|
+
Contract: ADB Ready 0.6.0, agent schema v1.
|