Przejdź do treści
Biblioteka skilli
Produktywność osobista · Automatyzacja

follow

/follow

Wykonuje na Macu czynności wymagające klikania według przewodnika butler, zamiast tylko wypisywać instrukcje do ręcznego wykonania.

Repozytorium
hermes-butler ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

85/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Wykonuje na Macu czynności wymagające klikania według przewodnika butler, zamiast tylko wypisywać instrukcje do ręcznego wykonania.

Oryginalny opis (EN)

Use when the user asks Hermes to fix/configure/oper-ate something on their Mac that needs clicking: drive a butler guide instead of listing instructions.

Jak działa

  1. When to use
  2. When NOT to use
  3. Step format (required quality)
  4. Pitfalls that waste a whole guide
Sekcje z nagłówków SKILL.md, w oryginale · 121 linii, 1 217 słów
Podgląd SKILL.md
---
name: follow
description: "Use when the user asks Hermes to fix/configure/oper-ate something on their Mac that needs clicking: drive a butler guide instead of listing instructions."
---

# Butler Follow mode

Hermes plans; the butler walks the plan on the user's screen. Every step is a
real control on their real display; the plugin verifies arrival from the OS
before advancing.

## When to use

- The user asks to change something accessible on macOS UI: settings, app
  preferences, browser pages, web forms, installer flows.
- The user asks "what am I looking at" style questions - use butler_capture
  first, answer, optionally offer a guide for the fix.

## When NOT to use

- Terminal/server work: no visible screen, the butler stays idle.
- Anything needing action *for* the user: typing passwords, confirming
  payments. The butler guides, the user's hands act.
- Content-finding tasks on web pages (find a section, read the docs, pull
  data from a portal): the agent should DRIVE THE BROWSER ITSELF instead -
  open the URL, read the DOM, locate the content, verify it - and only then
  ask the user whether they want a butler walkthrough of the route or a
  direct handover (page already open where it needs to be, or the exact
  URL). Butler walks take the user's hands and attention; for "where is X
  on this site" they are a slower, worse default than pointing at the answer.
- NEVER write `find.label` values for controls you have not observed live -
  not from memory, not from "typical Moodle layout". Observe in a DOM read
  (web) or butler_capture (native) FIRST, then plan. A guide whose labels
  were invented stalls the user at step 1 and costs two restart cycles.
  OCR is a fallback for the butler reading AX-gated content - never the
  planning input; for Chromium pages browser automation is the readable
  layer, not the butler.

## Step format (required quality)

- keep to a maximum of six steps; rewrite longer plans into a first guide plus
  a follow-up after user confirmation.
- `say`: imperative, one line, name the control exactly as it will look: not
  "open settings", but "Click Network".
- `find.label`: the exact expected control text; fall back with a second
  short guide if the capture reports a stall.
- Scrolling: the engine already covers controls that ARE in the tree but scrolled
  out of view - macOS reports those with a degenerate box (`DEGENERATE_BOX_MAX`,
  box `[0, 832, 0, 0]`), so the ring is suppressed and the note "Scroll to bring
  <label> into view" appears with the stall clock reset. Do not duplicate that in
  `say`, and do not read silence there as a missing plan.
- Scrolling the agent MUST cover: a target that is absent from the AX tree
  entirely (below) still needs the user told where to go, because no note can
  fire for a control nobody captured. There, weave "Scroll down to <label>" into
  the `say` - there is no scroll action and no ring to rely on.
- Settings pane BODIES are unreadable: each pane runs as its own app extension
  and appears in the tree as a childless `AXApplication`. A depth-24 walk of the
  open Network pane returned the sidebar's elements and zero detail-side
  children *while the pane was visible on screen*, and `target: "Network"` even
  matched an unrelated app. So "unread" is not the same fault as "below the
  fold": the rows were never captured at any scroll position. Sidebar rows and
  the window title (which takes the pane name) are all you get, so a guide into
  a pane body must be voice-led past that point.
- Launch steps ("open System Settings first"): use `"find": {}` with no
  label - a hands-off step. The butler does not ring anything; it verifies
  the transition through `expect` (`{"app": "System Settings"}`) once the app
  is actually open. Never hunt for app icons inside other apps' windows.
- `find.app`: the app this step happens in. Name it once (usually on the first
  step) and every later app-less step inherits the nearest earlier app, so one
  `find.app: "System Settings"` scopes the whole walk; `expect.app` alone scopes
  its own step too. A scoped step matches ONLY controls captured from that app,
  so silently verifying content from another app (another app's window, this
  chat's transcript) is now impossible, and `find.window`/`expect.window` only
  PREFERS that title — a menu or sheet is another window of the same app, so it
  must stay eligible. If a guide stalls with "Switch to X — this step happens
  in X", the plan is right and the window is wrong: tell the user to switch to
  X and leave the guide running; do not rewrite the step.
- `expect`: any observable change (`expect` keys pass through unfiltered):
  `{"app": "..."}` for app opens (open counts, focus not required),
  `{"window": "..."}` for pane navigation — the frontmost window's TITLE
  taking the pane's name is the click-observable for settings-style panes
  (fires only after the user actually navigates),
  `{"visible": "..."}` for controls that should merely EXIST afterward
  (blink-risky for click steps: it verifies the moment the control appears,
  before the user acts - prefer `window` for those),
  `{"focus": "..."}` for keyboard-selection changes (AX focus is unreliable
  on sidebar rows and menu cells - prefer `window` there too).
- Status `capture_failed`: the OS read itself failed (missing grant). Fix the
  grant (doctor --ask) and restart; do NOT rewrite the plan.
## Pitfalls that waste a whole guide

- **Never verify a pane that lives in the same window as this chat.** The
  desktop transcript renders every label the agent has written (bubbles, tool
  text, live thinking) as AXStaticText rows with 1px-high boxes, so an
  `expect: {"visible": "..."}` fires the instant the needle is on screen and
  the guide races past steps the user never clicked. Rings stay correct
  (best_match prefers real boxes and button roles); only the EXPECT half is
  fooled. For Hermes' own Settings inside the Hermes window, hand the path to
  the user in chat instead of starting a guide.
- **Settings inside the Hermes desktop app is a route in the main window, not
  a separate window and not a pane title.** Window title stays "Hermes", so
  `expect: {"window": ...}` can never fire. Grounded labels: `Open settings`
  (gear, top right, AXButton), then nav rows `Appearance` and `Notifications`
  (AXButton, each with an `Expand: <name>` chevron). Sub-pages such as
  `Desktop alerts` and `Sounds` only exist after the parent expands.
- `osascript` on this machine lacks an Accessibility grant: System Events
  cannot click controls for you and `screencapture` fails (no Screen
  Recording grant), while computer_use reports a 0x0 window for the Electron
  app. The butler companion is the only working screen reader here.

- If `butler_guide_status` reports stalled: rewrite the stalled step with a
  better `find.label` and start a fresh short guide; never repeat the same
  failing step verbatim.
- ## Grounding rule (do not violate)

- Never guess `find.label`/`expect` text from memory or inference: read the
  real screen first with butler_capture (OCR fallback covers gated Chromium),
  or ask the user for the exact control/course name before starting a guide.
  Assumed names stall the guide and waste the user's time (an entire guide was
  wasted on a wrong course name: 'Final Year Project' was assumed when the
  actual Moodle card read 'Individual Project').
- If a capture cannot read the page, confirm names with the user before
  starting, not after a stall.
- When the guide ends: summarize what was completed; offer the next step.

Wersje

W bazie nie ma innych skilli o nazwie follow.

Migawka bazy z 13.11.2026 · wersja paczki b33a40a353e3 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 85usage
    Zamienia odpowiedź w przewodnik krok po kroku na ekranie zamiast suchego tekstu i dobiera tryb do tego, o co pyta użytkownik.
  • 100butler
    Działa jako router w trybie zarządcy: planuje, dzieli, deleguje i weryfikuje zadania, a kod przekazuje sesjom wykonawczym.
  • 100butler
    Działa jako router w trybie butler: planuje, dzieli, deleguje i weryfikuje zadania w osobnych sesjach, sam nie pisząc kodu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.