big-arrow-on-the-screen skill
A skill that gives an agent a pointer on your Mac screen, using arrows, boxes and labels to show the button you need.
- 836 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI draws over applications and can raise windows; cards can interact with the clipboard.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/big-arrow-on-the-screenDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI draws over applications and can raise windows; cards can interact with the clipboard.
This is third-party code. Review the repository files before installing.
What it does
big-arrow-on-the-screen helps an agent show an action a person needs to perform in a Mac interface. It draws a labeled pointer over windows while preserving keyboard focus in the current application. Clicks on the target pass through to the application underneath. Targets can be specified by coordinates or found by element name. The skill teaches the agent to write a clear label, wait for the user and remove the hint. Separate floating cards handle questions and multiple values, returning answers as JSON.
Who it is for. For Claude Code and Codex users who need visual guidance for settings and manual actions in macOS apps.
Good fit when
- Point out a confirmation button in a system dialog.
- Mark successive controls during an application walkthrough.
- Let the user copy a labeled value into the selected field.
- Collect a choice through a card while preserving the current screen workflow.
Not a fit when
- You need the tool to press buttons for the user.
- You need this specific project on Windows or Linux.
- You need continuous screen recording and saved tutorial video.
Example request
Show where to enable the terminal permission on screen and wait for me to act.Limitations
A Mac with macOS 14 or later is required; this pointer is not supplied for Windows or Linux. Finding a button by name requires Accessibility permission for the application launching the CLI, such as your terminal. Window-title matching on newer macOS versions can require Screen Recording access; without it the title may be unavailable. An agent can select the wrong element, so read the hint and check the button’s purpose before clicking it yourself.
How to disable. Run `bigarrow stop --all` to remove arrows. Close cards using the X in their windows or `bigarrow stop --cards`. Remove the skill from the agent’s skill directory when its instructions are no longer needed.
FAQ
How long does an arrow stay visible?
By default, `bigarrow point` lasts 8 seconds and `bigarrow start` lasts 300 seconds. Set `--duration` to change it; zero removes the time limit.
Can I target a button by name?
Yes. `--element` matches a control, and `bigarrow elements --app X` lists available matches in an application.
What happens when the agent exits?
Its arrows exit with their owner process. A question card closes after every question is answered; a values-only card needs the X or a separate close command.
How does a card return an answer?
Through `bigarrow wait`, which waits for a choice or typed response and returns JSON.
Does it require a service account?
No. It runs locally without an account, background daemon or telemetry.
Discussion
No questions or reviews yet.
Related
SkillsA skill and MCP for voiced screen recordings: the agent turns a spoken bug walkthrough into tasks with screenshots and code
A set of everyday agent skills: web search, browser automation, Gmail, Google Calendar and Drive, speech transcription and YouTube transcripts
Skills that turn a coding agent's output into plain language: honest reports, straight verdicts, followable steps
A skill that cross-examines a plan before work starts: numbered questions in rounds with a recommended answer and no changes until you confirm
cafe3310's personal skill collection: spec-driven project work, reviews, reports, browser, 3D and video in one repository
18 skills and 6 agents for UX strategy: from research and flows to accessibility, ethics and engineering handoff
README in short
Hints support shape, color and size controls. When another application covers a target, the pointer hides until the target becomes visible again.
README badge
Original SKILL.md
---
name: big-arrow
description: "Point at something on the human's macOS screen with a big arrow and a sign (\"Franz, click HERE\"), and hand over values, secrets and questions on a floating cue card, using the bigarrow CLI. Use whenever the human has to look at, click, type into or choose a specific spot, button, field, window, tab or menu: show me where, point to it, which button, where do I click, zeig mir wo, guide me through this UI, the human must approve or sign something, or you need the human's hand and they may not be looking at the terminal; also to hand over credentials, a password, token, 2FA code, IBAN or command to paste, or to ask the human a question or a choice while they are away from the terminal. Mandatory when it is time-critical: a code that expires, a login or payment page that times out, a build waiting on the human."
license: MIT
allowed-tools: Bash(bigarrow:*)
metadata:
short-description: "Point at the screen with a big arrow and a sign"
---
# big-arrow
`bigarrow` draws a click-through arrow with a sign, needs no permission and never takes the
focus. Point at the thing itself, a line in the terminal is easy to miss.
Needs bigarrow 0.5.1 or newer. If `bigarrow --version` prints an older one, run
`brew upgrade franzenzenhofer/tap/bigarrow` first: an old binary has no `card` and prints
`{{value}}` as plain text.
```bash
open "x-apple.systempreferences:com.apple.preference.security?Privacy_ScreenCapture"
bigarrow start --element "Ghostty" --app "System Settings" --text "Franz, switch this on: Ghostty may record your screen" --say
# watch for the result (page changed, job continued, file appeared), then:
bigarrow stop
```
## Rules
- Open the exact pane or URL yourself, then point at the one control left for the human. Never
walk them through menus. The human clicks; you point.
- The sign is one full sentence naming the action ("Franz, click Save", never "here"). When the
click approves, grants, pays, signs, sends or deletes, add what happens: "Franz, click Pay:
49 EUR to Hetzner". The human decides; the facts go on the sign, not only in the terminal.
- `--say` when the human may not be looking. Time-critical (code expires, page times out, job
waits): `--color red --say` and say by when: "Franz, enter the 2FA code now, it expires in 60 s".
- Something to paste (a command you may not run, a URL, a code): put it on the sign as
`{{value}}`. The human sees the value on a copy button (no braces); one click copies all of it
and the arrow stays. Point at where it goes: "Franz, copy {{sudo xcodebuild -license accept}}
and paste it here", then check that it was pasted.
- One arrow per step; `bigarrow stop` the moment the step is done. Arrows also end alone: after
300 s, when your session exits, when the human answers (hook below).
- A click on the sign or shaft, except a copy button, removes the arrow (target clicks pass
through). A removed arrow was seen: check the result, do not redraw. Skip `--close-button`
unless asked.
## Cards: values, secrets, answers