safari
Skill4 starsChanged 7 months agoMITView on GitHub
Safari desktop heuristics for background-computer-use. Use when the user asks you to navigate, scroll, click links, switch tabs, or otherwise drive Safari without stealing focus.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jootsing-research/skillstheir own version, first seen Sep 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jootsing-research/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- apple-musicSkill
- chromeSkill
- clockSkill
- computer-useSkill
- notionSkill
- numbersSkill
- spotifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 11
Always call get_app_state app="Safari" before interacting.
≈ “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.
Files
Driving Safari with background computer use
Safari's accessibility coverage is good overall, but its address bar and web content areas have two quirks that bite naive automation.
- Always call
get_app_state app="Safari"before interacting. - To navigate to a URL, call
set_value app="Safari" element_index=<smart-search-field> value="https://…".- The smart search field's ID is
WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD. set_valuesubmits by default; don't also post a separateReturn.- Internally this uses a typing fallback, because Safari silently
ignores
AXValuewrites on the URL bar.
- The smart search field's ID is
- To scroll the page, call
scroll app="Safari" element_index=<scroll-area> direction="down". The tool tries a native AX page-scroll first, then posts wheel events to the correct WKWebView helper pid, then falls back toPageDown/PageUpkeystrokes if nothing moved. click(element_index=<link>)works on in-page links viaAXPresseven when the Safari window is occluded.- Tab switches:
click(element_index=<tab>)on anAXTabButton. Close withperform_secondary_action(action="close tab")rather than hit-testing the tiny close glyph.
Detailed notes live in server/app-hints/Safari.md; they are injected as
<app_hints> on every get_app_state call for Safari.
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
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.

