agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/skills/agent-device/SKILL.md

agent-device

Skill3 starsChanged 3 days agoMITView on GitHub

Automates Apple-platform apps (iOS, tvOS, macOS) and Android devices. Use when navigating apps, taking snapshots/screenshots, tapping, typing, scrolling, extracting UI info, collecting logs/network/perf evidence, or planning agent-device CLI commands.

  • Installs packages

10 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before your first agent-device command or plan, read the smallest version-matched CLI guide that fits the task:

    line 18
  2. Distinctive:

    Read additional topics only when relevant:

    line 27
  3. Very specific:

    Use this skill only to route into version-matched CLI help.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

agent-device

Router only. Private setup before using this skill:

agent-device --version

If that fails but the user may have installed agent-device globally, check the user's configured login/interactive shell and environment before using npx. Resolve the command the same way the user would from a normal terminal session, then run the absolute binary path if found. This may require inspecting shell startup behavior or package-manager/global bin locations; do not assume the Codex process PATH is the user's PATH.

Require agent-device >= 0.19.1; older CLIs lack these help topics. If older, stop and tell the user to upgrade the trusted install or approve an exact-version npm command. Do not run npm install -g agent-device@latest or npx -y agent-device@latest autonomously, and do not include version/upgrade commands in final plans.

Before your first agent-device command or plan, read the smallest version-matched CLI guide that fits the task:

agent-device help manual-qa   # scripted/manual QA, acceptance checks, checklist execution
agent-device help validate    # code/runtime validation, stale build or daemon risk
agent-device help dogfood     # exploratory app dogfooding and evidence collection
agent-device help workflow    # fallback reference for general app driving or mixed tasks

Read additional topics only when relevant:

agent-device help debugging
agent-device help react-native
agent-device help react-devtools
agent-device help cdp
agent-device help remote
agent-device help macos
agent-device help dogfood

Default loop: open -> snapshot/-i -> get/is/find or press/fill/scroll/wait -> verify -> close.

Use this skill only to route into version-matched CLI help. Let the selected help topic provide exact command shapes, platform limits, and current workflow guidance; use help workflow as the full reference when a task-specific topic is too narrow.

For precise location workflows, read the installed settings help before planning so coordinate support and platform limits come from the active CLI version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.