agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/observe/SKILL.md

observe

Skill56 starsChanged 35 days agoApache-2.0View on GitHub

Use this skill to inspect the current state of a connected mobile device through the AutoMobile observe capability and summarize the active app, visible UI, and any obvious interaction targets.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use design and ship.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    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:

    Use the AutoMobile observation tooling to inspect the current device state.

    line 8
  2. Very specific:

    Call the observe capability for the active device.

    line 12
  3. Distinctive:

    If the hierarchy is noisy, summarize only the controls that matter to the user’s goal.

    line 14
  4. Distinctive:

    When follow-up automation is likely, call out obvious next interaction targets such as buttons, fields, tabs, or permission prompts.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 9 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

Observe Device

Use the AutoMobile observation tooling to inspect the current device state.

Workflow

  1. Call the observe capability for the active device.
  2. Report the active app or activity, the most relevant visible UI elements, and the observation timestamp.
  3. If the hierarchy is noisy, summarize only the controls that matter to the user’s goal.
  4. When follow-up automation is likely, call out obvious next interaction targets such as buttons, fields, tabs, or permission prompts.

Output Structure

  • Active app and activity
  • Key visible UI elements
  • updatedAt timestamp
  • Short note on likely next actions when useful

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.

Check your setup, free