agentleFS
memi-designmemi-design/design-skills/skills/apple-desktop-automation/SKILL.md

apple-desktop-automation

Skill7 starsChanged 4 months agoMITView on GitHub

Prepare macOS agents to work with Apple apps, local files, permissions, and desktop automation.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this Note when a Memoire or Studio run needs macOS automation, Apple Notes, Reminders, iMessage, desktop app control.

    line 12
  2. Distinctive:

    Check Accessibility, Screen Recording, Automation, and file permissions before driving desktop apps.

    line 16
  3. Distinctive:

    Prefer app-specific CLIs or Shortcuts before using broad GUI automation.

    line 17
  4. Distinctive:

    Keep personal app access opt-in and scoped to the named task.

    line 18
  5. Distinctive:

    Never run destructive desktop actions without a visible confirmation step.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Apple Desktop Automation

Prepare macOS agents to work with Apple apps, local files, permissions, and desktop automation.

When to Use

Use this Note when a Memoire or Studio run needs macOS automation, Apple Notes, Reminders, iMessage, desktop app control.

Workflow

  1. Check Accessibility, Screen Recording, Automation, and file permissions before driving desktop apps.
  2. Prefer app-specific CLIs or Shortcuts before using broad GUI automation.
  3. Keep personal app access opt-in and scoped to the named task.
  4. Capture screenshots or structured app output after important desktop actions.
  5. Never run destructive desktop actions without a visible confirmation step.

Sources

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.