Agent skill · Content & Marketing

Phone Use

MUST Load this skill for ANY task that involves GUI interaction or device control — opening apps, tapping, typing, scrolling, swiping, Back/Home/Recents, reading the screen, or any workflow that touches on-screen content. Load this even when the user does not explicitly mention the device — if the task implies a GUI operation, load this skill first.

niki62★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add niki914/agentic-nexus --skill phone-use --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Path: app/src/main/assets/skills/phone-use/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 97
Language: Kotlin
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Overview Phone Use gives you the ability to see and interact with the Android device screen. It uses Android AccessibilityService (with root-assisted auto-setup) to read the UI tree and simulate user actions. This is the ONLY way to control the device — do NOT attempt to use non-existent APIs or platform tools. **When to load:** any GUI task. App launching, tapping, typing, scrolling, swiping, navigation keys, screen reading. Even when the user doesn't say "on the phone" — infer it from the task. **When NOT to retry:** non-native apps (Flutter, Unity, WebView, games). If `screen_operation_accessibility(operation: "read")` returns empty/root-only, stop and report immediately. | Tool | Purpose | |:-----|:--------| | `screen_operation_accessibility` | Read screen tree, tap/long-click/scroll/set_text on nodes by token, search nodes — all via accessibility service | | `screen_operation_shell` | Tap/long-click/swipe/key by screen coordinates via shell. FALLBACK only — coordinates MUST come from the most recently returned screen tree | Two auxiliary tools for app discovery and launching: | Tool | Purpose | |:-----|:--------| | `search_apps` | Search installed apps by name or package na

What's inside
Steps it walks through
  1. Overview
  2. Tool Reference
  3. screenoperationaccessibility
  4. screenoperationshell
  5. launchapp / searchapps
  6. Workflow
  7. 1. Open the target app
  8. 2. Read the screen
  9. 2b. Search for specific elements (optional)
  10. 3. Act on the tree
  11. 4. Re-read after state-changing actions
  12. 5. Navigate between apps
  13. Decision Heuristics
  14. Terminal signal detection
More from agentic-nexus
All skills →
About this skill
What does the Phone Use skill do?

MUST Load this skill for ANY task that involves GUI interaction or device control — opening apps, tapping, typing, scrolling, swiping, Back/Home/Recents, reading the screen, or any workflow that touches on-screen content. Load this even when the user does not explicitly mention the device — if the task implies a GUI operation, load this skill first.

How do I install it?

Run `npx skills add niki914/agentic-nexus --skill phone-use --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From niki914/agentic-nexus, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going