agentleFS
LocalKinAILocalKinAI/kinclaw/skills/app_open_clean/SKILL.md

app_open_clean

Skill9 starsChanged 6 months agoApache-2.0View on GitHub

Open a macOS app AND dismiss any blocking welcome / "What's New" / setup-prompt sheet that appeared on launch. Returns the app name and whether a modal was dismissed. Use this INSTEAD of `shell open -a X` when first opening an app you haven't driven before — saves the agent from the common failure mode of typing into a welcome modal instead of the actual UI.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    If the app has no modal (already dismissed, or never had one), the script exits clean and reports "no modal found" — completely safe to …

    line 144
  2. Very specific:

    If your installed app has a different dismiss button label not in the priority list (e.g.

    line 184

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

app_open_clean — open + dismiss welcome modal

A common failure pattern when an LLM agent first drives a Mac app: launch the app → start typing or clicking → realize too late that a "What's New" or "Welcome" sheet was sitting on top of the real UI the whole time. The keystrokes go nowhere or hit the wrong target. The app looks unresponsive but is actually working fine; the modal is invisible to the AX-walk because it's a separate sheet.

This skill handles both phases in a single tool call:

  1. open -a <app> — launches via Launch Services
  2. osascript walks the frontmost process's windows + sheets, clicks the highest-priority dismiss button it finds, repeats once for stacked welcome flows.

If the app has no modal (already dismissed, or never had one), the script exits clean and reports "no modal found" — completely safe to call on already-open apps.

When to use

  • You're driving a built-in macOS app you haven't touched in this session: Reminders, Mail, Calendar, Photos, Maps, Music, etc.
  • You just upgraded macOS — every app's "What's New" fires once.
  • A third-party app you've never opened on this machine (Bear, Slack, Notion, etc.).

When NOT to use

  • App is already running and you've already used it — shell open -a is enough, no modal will appear.
  • The "modal" you want to keep — e.g. you opened Mail to use the Add Account flow on purpose. (Use shell open -a Mail directly then.)

Examples

app_open_clean app=Reminders
  → opened: Reminders
    dismissed: Continue → Got It

app_open_clean app=Calculator
  → opened: Calculator
    dismissed: (no modal found)

Why a SKILL.md and not native

Pure shell + osascript. No Go state, no AX walking via kinax that this skill doesn't already get from the standard ui tool. Sticks to the "thin kernel + fat skill" thesis — apps come and go, modal shapes evolve, this is exactly what forge should be writing.

Override / extend

If your installed app has a different dismiss button label not in the priority list (e.g. "Begin", "OK, got it", "下一步"), edit this SKILL.md and add it to dismissBtns. Or forge a sibling skill named after the specific app.

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.