agentleFS
Sign inStart free
travisjneumantravisjneuman/.claude/skills/agent-desktop/SKILL.md

agent-desktop

Skill106 starsChanged 8 months agoMITView on GitHub

Control native desktop apps with agent-desktop accessibility snapshots and actions on macOS, Windows, or Linux. Use for desktop UI tasks, never browser automation or web research.

  • Installs packages

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a higher-priority desktop-control tool is configured for this host (see local rules), prefer it.

    line 12
  2. Very specific:

    If the CLI is missing, report the pinned prerequisite npm install -g agent-desktop@1.0.2.

    line 14
  3. Very specific:

    Use current snapshot refs with click, set-value, type, or press, following the loaded guides.

    line 27
  4. Very specific:

    Default operation is background friendly.

    line 34
  5. Very specific:

    Never use --force without explicit approval.

    line 38

“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 Desktop

Thin guidance for vercel-labs/agent-desktop v1.0.2, an Apache-2.0 Rust shell CLI using macOS AX, Windows UI Automation, and Linux AT-SPI.

Route and prerequisites

  • If a higher-priority desktop-control tool is configured for this host (see local rules), prefer it.
  • This is a native desktop route, never a browser/source-intake route. Never scrape or drive browser web research with it.
  • If the CLI is missing, report the pinned prerequisite npm install -g agent-desktop@1.0.2; install only when authorized.
  • On macOS, use agent-desktop permissions --guide and ask the user to grant Accessibility. Screenshots also need Screen Recording permission.
  • At first use, load both upstream guides rather than guessing command syntax:
agent-desktop skills get desktop
agent-desktop skills get platform

Work loop

  1. Identify the requested app/window with list-apps or list-windows as needed.
  2. Read agent-desktop snapshot --app "<App>" -i.
  3. Use current snapshot refs with click, set-value, type, or press, following the loaded guides. Quote refs in PowerShell.
  4. Re-snapshot after UI changes before choosing another ref. Use find, get, or is for targeted inspection; use mouse-click only when refs cannot address the target.

Tracing is off unless you pass --trace <path>; only pass it when the task needs a trace. Keep traces and screenshots out of repositories and avoid capturing credentials or unrelated private content.

Platform limits and approval

  • Default operation is background friendly. Use --headed only when needed: it moves the real cursor and can steal focus.
  • Windows type and right-click require headed mode. Windows/Linux headless key actions need the target focused; do not assume background targeting establishes focus.
  • Hyprland/Wayland pointer, drag, and window control are unsupported; report that limit rather than improvising another runtime.
  • The CLI has no built-in confirmation or allowlist. Before account writes, purchases, sends, or deletions, require explicit user approval for that exact action and target. Existing action-specific approval suffices.
  • Never use --force without explicit approval. Stop at permission/provider gates and report the blocker.
  • Report what the requested interaction returned; do not claim completion from a successful command alone.

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