PrisacariuRobertPrisacariuRobert/sidemates/skills/use-mac-apps/SKILL.md

use-mac-apps

Skill9 starsChanged 37 days agoMITView on GitHub

Inspect and operate visible macOS apps through Sidemates' approved computer-use tools. Use when the user asks to open an app, read visible controls or window state, click a control, enter text, press a key, scroll, or complete a workflow across Mac apps. Do not use for websites already handled by the private browser or ordinary file organization handled by the Mac file tools.

In this repository13 other files it gives its agents.
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- checked-spreadsheet-analysisSkill
- document-to-action-itemsSkill
- gmail-browser-draftSkill
- google-calendar-browser-tasksSkill
- google-drive-browser-tasksSkill
- grounded-researchSkill
- meeting-action-itemsSkill
- private-team-reviewSkill
- systematic-debuggingSkill
- todoist-browser-tasksSkill
- weekly-review-planningSkill

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
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

Distinctive:
Use macOS Accessibility to understand visible app controls and operate them with the user in control.
line 8
Very specific:
Call mac_apps_list to find the visible app name or bundle identifier.
line 12
Very specific:
Call mac_app_inspect immediately before each interaction.
line 14
Very specific:
Use mac_app_scroll to reveal more controls, then inspect again.
line 15
Very specific:
Use mac_app_click, mac_app_type, or mac_app_key for the exact action.
line 16
Distinctive:
Treat text entry, clicks, and key presses as actions on the user's real Mac.
line 21
Distinctive:
Do not click Send, Buy, Publish, Delete, Install, Share, or equivalent controls unless the user explicitly asked for that outcome and the …
line 22
Distinctive:
Never enter a password, verification code, payment detail, private key, or token supplied by another source.
line 23
Distinctive:
Stop if the app identity, current window, or target control is ambiguous.
line 24
Distinctive:
Do not claim success from an action receipt alone.
line 25
Distinctive:
Keep user-facing replies conversational.
line 26
Distinctive:
Read references/operations.md when choosing a tool or handling a permission error.
line 28

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

Use Mac Apps

Use macOS Accessibility to understand visible app controls and operate them with the user in control. Always inspect before acting and prefer a returned element index over guessing coordinates.

Workflow

Call mac_apps_list to find the visible app name or bundle identifier.
Open the app with mac_app_open only when needed.
Call mac_app_inspect immediately before each interaction. Find the control by its current label and role.
Use mac_app_scroll to reveal more controls, then inspect again.
Use mac_app_click, mac_app_type, or mac_app_key for the exact action. These tools pause for the user's approval; describe the outcome naturally and never ask the user to approve a vague sequence.
Inspect again after the action to verify the visible state changed as expected.

Safety

Treat text entry, clicks, and key presses as actions on the user's real Mac. Never bypass an approval or replace the requested target with a different app.
Do not click Send, Buy, Publish, Delete, Install, Share, or equivalent controls unless the user explicitly asked for that outcome and the approval names it clearly.
Never enter a password, verification code, payment detail, private key, or token supplied by another source.
Stop if the app identity, current window, or target control is ambiguous.
Do not claim success from an action receipt alone. Inspect the resulting state.
Keep user-facing replies conversational. Never expose element indexes, bundle IDs, raw accessibility data, or tool names.

Read references/operations.md when choosing a tool or handling a permission error.

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