Skip to content
Skills Library
Personal productivity · Tool integration

android

/android

Use "${id}", the user's OWN Android phone, through the Intentic Device app: its screen, allowed apps, picked folders and shared notifications. Use when the user says "my phone", names this phone, or needs something only the phone has (an app with no web version, a texted code, a photo or file on it).

Repository
intentic ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use "${id}", the user's OWN Android phone, through the Intentic Device app: its screen, allowed apps, picked folders and shared notifications. Use when the user says "my phone", names this phone, or needs something only the phone has (an app with no web version, a texted code, a photo or file on it).

Triggers from the description

${id}my phone
Original author description

Use "${id}", the user's OWN Android phone, through the Intentic Device app: its screen, allowed apps, picked folders and shared notifications. Use when the user says "my phone", names this phone, or needs something only the phone has (an app with no web version, a texted code, a photo or file on it).

How it works

  1. Android specifics worth knowing
Original SKILL.md headings · 20 lines, 239 words
SKILL.md preview
---
name: android
description: Use "${id}", the user's OWN Android phone, through the Intentic Device app: its screen, allowed apps, picked folders and shared notifications. Use when the user says "my phone", names this phone, or needs something only the phone has (an app with no web version, a texted code, a photo or file on it).
---

${tools}

## Android specifics worth knowing

- **Package names are how apps are named here.** `apps` lists them (`com.whatsapp`, `com.google.android.gm`). Use the
  package with `open` and `ask_access`, and the label when you talk to the person.
- **The screen in front is the only screen.** Unlike a browser's tabs, there is no working in the background: opening
  an app takes the person's screen from whatever they were doing. Say what you are about to open before you open it.
- **Back is not undo.** `device` `back` leaves a screen; in a form it may throw away what was typed. Read the screen
  again after it.
- **Keyboards cover the bottom of the screen.** After typing, the button you want may be hidden under the keyboard:
  `device` `back` closes the keyboard first, then list the elements again.
- **Lists load as they scroll.** If what you look for is not in `ui_elements`, scroll the list (`ui_act` `scroll_down`
  on the list's ref) and list again, rather than concluding it is not there.
- **Some screens are protected.** Banking apps and password fields show black in a screenshot by Android's own rule.
  `ui_elements` still names their buttons; their contents are the person's to read out, not yours to work around.
- **Permission dialogs belong to the person.** A system dialog asking to allow a permission, install something or
  change a setting is theirs to answer: tell them it is there and wait.

Versions

RepositoryScoreLicence
This page · intentic/intentic86MIT
lynricsy/hyperskills100MIT
j4flmao/agent-skills100MIT
clawic/skills90MIT

Database snapshot: 13.11.2026 · package version 30b45f7ec029 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90wearos
    Use "${id}", the user's OWN Wear OS watch, through the Intentic Device app on it: its screen, its tiles and the apps they allow. Use when the user says "my watch", names this watch, or needs something only the watch has (a watch app they are building or testing, a tile, something on their wrist).
  • 86control
    Control an authorized local Android phone or show its real-time read-only video beside the current local Codex task on macOS. Use for phone app tasks and Android UI checks.
  • 96phone-harness
    Control, inspect, test, or automate a physical Android phone connected to OpenMausBot over authorized USB debugging. Use for explicit Android, USB phone, ADB, mobile-app, tapping, typing, swiping, scrolling, screenshot, or phone-screen requests.
  • 100local-mobile-app-21dc4011
    A mobile-app screen authored at standard phone resolution (390×844) with responsive device adaptation, rounded corners, and no device frame. Use when the brief asks for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".
  • 100notif-city
    Find which apps on an Android phone push marketing notifications (deals, promotions, recommendations, news, live streams) by reading the phone's notification channels over adb, read-only, and draw them as an isometric city where each app is a building and each marketing channel…
  • 95phone-control
    Read and drive a real Android phone screen - UI tree as text with real coordinates, tap by visible label, swipe, press keys, type, screenshot, and report whether the screen actually changed. Use when a task needs the phone screen read, changed or verified (open an app, find and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.