Menu
This skill should be used for attached Android validation workflows that can be driven through adb_step.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | Device Validation |
| description | This skill should be used for attached Android validation workflows that can be driven through adb_step. |
Allow Codex to perform mechanical Android device interaction through adb_step instead of requiring manual user testing whenever feasible.
adb_step.adb_step.Use adb_step for:
This skill provides workflow guidance only. It does not add a new MCP tool or wrapper implementation.
adb_step for mechanical actions only.Avoid:
adb_stepUse when the user asks to "start session", "log session", "begin turn", "update turn", "complete turn", or "query session history"
Use when the user asks for "commit-sync", "checkpoint", or "sync to origin" to pause the active task and commit/push dirty repo state to origin.
Use when the user asks to "ingest text into graphrag", "add document to knowledge graph", "create entity", "create relationship", "query knowledge graph", "list graph entities", "delete document"
Use when the user asks to "list requirements", "add requirement", "create FR", "create TR", "create test requirement", "generate requirements document", or "ingest requirements".
Use when the user asks to "sync logs", "repair MCP session logs", "logging summary", or "summarize logging" to synchronize and reconcile MCP Server session logs through the plugin bridge.
Use when the user asks to "create a todo", "list todos", "update todo", "query tasks", "check todo status", "plan implementation", or "mark todo done".