菜单
UI元素树解析——通过uiautomator获取屏幕元素坐标，比截图识图快10倍。使用时机：需要找按钮/文本框/菜单的精确坐标来点击。| UI element tree parsing via uiautomator. 10x faster than screenshot+vision for finding button/text positions. Use when: need precise coordinates to tap a specific UI element.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/xvxv-stack7/termux-shizuku --skill phone-elements命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
统一快速研究入口 + Query Planner。质量关键不是搜多少次，而是怎么构造 query——先提取字段，再生成多条不同目的的短 query，相关性闸门过滤，技术/专业问题优先 GitHub（repo-scoped）直接拿 issue 全文。| Unified research with Query Planning for coding agents. Never dump a raw question; plan purpose-built short queries, gate by relevance, and for technical questions go straight to GitHub issues.
安卓后台监控+防沉迷系统。使用时机：需要后台监控手机状态、限制应用使用时长、自动锁应用、事件驱动弹窗提醒。| Android background monitoring with anti-addiction. Use when: background phone monitoring, app time limits, auto force-stop, event-driven notifications needed.
音乐控制——搜索、选歌、播放指定歌曲，搭配AI主动放歌。使用时机：music_moment事件触发时，或用户说"放首歌"时。| Music control — search, select, and play specific songs via NetEase Cloud Music API. Use when: music_moment event fires, or user says "play a song".
基于 SOC 职业分类
正在显示 SKILL.md
| name | phone-elements |
| description | UI元素树解析——通过uiautomator获取屏幕元素坐标，比截图识图快10倍。使用时机：需要找按钮/文本框/菜单的精确坐标来点击。| UI element tree parsing via uiautomator. 10x faster than screenshot+vision for finding button/text positions. Use when: need precise coordinates to tap a specific UI element. |
Dump Android's UI element tree via uiautomator dump, parse it, and find elements by text/ID/class with pixel-precise coordinates. 1 second end to end, vs 7-8 seconds for screenshot + AI vision.
Built-in Android feature — no extra app needed.
xml.etree.ElementTree is stdlib)# Verify uiautomator available
adb -s 127.0.0.1:5555 shell uiautomator dump /dev/tty 2>/dev/null | head -1
# or
rish -c 'uiautomator dump /dev/tty' 2>/dev/null | head -1
# Find "确认" button and tap it — one command
python3 skills/phone-elements/elements.py --text "确认" --tap
# Find submit button by resource ID
python3 skills/phone-elements/elements.py --id "submit" --tap
# Find all clickable elements (no filter)
python3 skills/phone-elements/elements.py --limit 20
# Just dump the raw XML for manual inspection
python3 skills/phone-elements/elements.py --dump-only
[
{
"idx": 0,
"text": "确认",
"class": "android.widget.Button",
"id": "com.example:id/confirm_btn",
"x": 180,
"y": 510,
"w": 120,
"h": 60,
"clickable": true
}
]
x and y are the center coordinates — ready to input tap directly.
# Shizuku
rish -c 'input tap <x> <y>'
# ADB
adb -s 127.0.0.1:5555 shell input tap <x> <y>
| Method | Time | Use case |
|---|---|---|
elements.py --text "确认" --tap | ~1s | Known button text |
| Screenshot + vision AI | ~7-8s | Unknown layout, scene understanding |
| uiautomator dump raw | ~0.5s | Debug, explore UI structure |
/dev/tty not supported.uiautomator dump returns non-zero exit code even when XML is valid (missing theme_compatibility.xml). Script handles this — checks XML content, not exit code.uiautomator is AOSP/dev/tty typically works, file dump as backupdumpsys activity). HarmonyOS NEXT: untested (no ADB)/dev/tty (AOSP standard) → file dump (/sdcard/ui_dump.xml). Whichever works first wins.