Altic Studio
altic-studio provides two automation modes:
- AppleScript mode for macOS apps and system actions
- MCP CDP mode for Google Chrome browser control
- MCP file mode for safe Finder and filesystem operations
- MCP clipboard mode for text, file, and image pasteboard operations
- MCP window/workspace mode for arranging macOS apps and windows
It also includes Swift utility scripts for active-display screenshots, clipboard
file/image operations, and window/workspace management on macOS.
Mode A: AppleScript (macOS apps)
- Always execute AppleScript through Bash with
osascript.
- Always run from workspace root as the working directory.
- Quote script paths and arguments.
- Prefer direct script invocation; do not route through Python wrappers unless explicitly requested.
Command templates:
osascript "skills/altic-studio/scripts/<script>.applescript" [arg1] [arg2] ...
AppleScript Capabilities
The full Altic automation surface is exposed as scripts under skills/altic-studio/scripts:
open-application.applescript - args: <app_name>send-message.applescript - args: <phone_or_handle> <message>read-recent-messages.applescript - args: <phone_or_handle> <count>fetch-all-contacts.applescript - args: noneset-reminder.applescript - args: <text> <YYYY-MM-DD HH:MM> [list_name]create-note.applescript - args: <title> <body> [folder]search-for-note.applescript - args: <query> [max_results]create-calendar-event.applescript - args: <title> <YYYY-MM-DD HH:MM> <duration_minutes> [calendar]list-all-calendar-events-for-day.applescript - args: <YYYY-MM-DD>open-safari-tab.applescript - args: [url]close-safari-tab.applescript - args: [tab_index|-1]get-safari-tabs.applescript - args: noneswitch-safari-tab.applescript - args: <tab_index>run-safari-javascript.applescript - args: <javascript_code>navigate-safari.applescript - args: <url>reload-safari-page.applescript - args: nonesafari-go-back.applescript - args: nonesafari-go-forward.applescript - args: noneopen-safari-window.applescript - args: [url]close-safari-window.applescript - args: noneget-safari-page-info.applescript - args: nonedecrease-brightness.applescript - args: [amount_0_to_1]increase-brightness.applescript - args: [amount_0_to_1]turn-up-volume.applescript - args: [amount_0_to_100]turn-down-volume.applescript - args: [amount_0_to_100]capture-screenshot.applescript - args: [output_path] [full|interactive|window]capture-active-screen.swift - args: <output_path> (captures full display containing frontmost app)clipboard.swift - subcommands: get-files, set-files <paths...>, save-image <output_path>, set-image <image_path>window-manager.swift - subcommands: get_frontmost_app, list_windows, focus_window, move_window, resize_window, center_window, tile_windows, minimize, hide_app, quit_app
Swift command template (for active-display screenshots):
swift "skills/altic-studio/scripts/capture-active-screen.swift" "/tmp/active-screen.png"
Swift command template (for window management):
swift "skills/altic-studio/scripts/window-manager.swift" "list_windows" '{"include_minimized":false}'
Mode B: Chrome Browser Control (MCP CDP)
Use MCP tools for deterministic Chrome automation:
chrome_open_sessionchrome_navigatechrome_wait_forchrome_clickchrome_typechrome_extractchrome_screenshotchrome_close_sessionchrome_list_sessionscapture_active_screen
Execution pattern:
- Open a Chrome session.
- Navigate and wait for stable selectors.
- Interact with click and type actions.
- Verify state with extraction.
- Capture screenshots on checkpoints or failures.
- Close session.
Mode C: File Finder and File Operations (MCP)
Use MCP file tools instead of shell commands when the user asks to find, inspect,
copy, move, rename, reveal, or trash files. These tools return JSON for
successful lookups and operations, and Error: ... strings for failures.
Available tools:
find_files - args: <query> [root] [max_results] [include_hidden] [kind]list_directory - args: <path> [include_hidden] [max_results]get_file_info - args: <path>copy_file - args: <source> <destination> [overwrite] [dry_run]copy_directory - args: <source> <destination> [overwrite] [dry_run]move_file - args: <source> <destination> [overwrite] [dry_run]rename_file - args: <path> <new_name> [overwrite] [dry_run]trash_file - args: <path> [dry_run]reveal_in_finder - args: <path>get_finder_selection - args: none
File workflow rules:
- If the user refers to selected files, the current Finder window, or "this file",
call
get_finder_selection first.
- For ambiguous file names, call
find_files, then get_file_info; ask for
disambiguation when multiple plausible matches remain.
- Prefer
dry_run=true before copy_file, copy_directory, move_file,
rename_file, or trash_file when the target or destination is ambiguous.
- Do not overwrite unless the user explicitly asks for replacement; default
overwrite=false.
- Use
trash_file, not permanent deletion.
- Use
reveal_in_finder after file operations when the user wants to see the
result in Finder.
Mode D: Clipboard Operations (MCP)
Use MCP clipboard tools instead of shell commands when the user asks to inspect,
copy, paste, clear, or save clipboard contents. These tools return JSON for text
and file operations, Error: ... strings for failures, and image content for
saved clipboard images.
Available tools:
get_clipboard_text - args: [max_chars]set_clipboard_text - args: <text>clear_clipboard - args: noneget_clipboard_files - args: noneset_clipboard_files - args: <paths>save_clipboard_image - args: [output_path]set_clipboard_image - args: <path>
Clipboard workflow rules:
- Ask before overwriting clipboard contents unless the user explicitly asks to
copy, set, clear, or replace the clipboard.
- Use
get_clipboard_text first when the user asks what text is currently copied.
- Use
get_clipboard_files when the user says they copied files in Finder or
wants to paste copied files somewhere else.
- Use
save_clipboard_image when the user wants to inspect, store, or transform
an image currently on the clipboard.
- Use
set_clipboard_files with existing paths only; resolve ambiguous file
names with find_files before changing the clipboard.
- Use
set_clipboard_image only for existing image files.
Mode E: Window and Workspace Operations (MCP)
Use MCP window tools when the user asks to arrange the workspace, focus an app or
window, tile apps side by side, resize windows, minimize windows, hide apps, quit
apps, or inspect the frontmost app. These tools return JSON for successful
operations and Error: ... strings for failures.
Available tools:
get_frontmost_app - args: nonelist_windows - args: [app_name] [include_minimized]focus_window - args: [app_name] [window_id] [window_index]move_window - args: <x> <y> [app_name] [window_id] [window_index] [display_index]resize_window - args: <width> <height> [app_name] [window_id] [window_index] [display_index]center_window - args: [app_name] [window_id] [window_index] [display_index] [width] [height]tile_windows - args: [layout=columns|rows|grid] [app_names] [display_index] [padding]minimize - args: [app_name] [window_id] [window_index]hide_app - args: <app_name>quit_app - args: <app_name>
Window workflow rules:
- Call
list_windows before moving, resizing, minimizing, or focusing when the
target app has multiple windows or the target is ambiguous.
- Prefer
app_name for user-facing workflows and window_id for precise
follow-up operations after list_windows.
- Use
display_index when arranging windows on a specific display; otherwise
tools choose the display containing the target window.
- Use
tile_windows with explicit app_names when preparing a multi-app task.
- Do not call
quit_app unless the user explicitly asked to close or quit that
app.
- If a window mutation fails with an Accessibility error, tell the user to grant
Accessibility permission to the host app running the MCP server.
Operational Rules
- Validate date/time format before running reminder/calendar scripts.
- If contact lookup returns multiple options, ask for disambiguation before sending.
- If script output indicates permission issues, report exact permissions to enable.
- Prefer explicit CSS selectors and call
chrome_wait_for before click/type on dynamic pages.
- After mutating actions in Chrome, verify expected page state with
chrome_extract.
- For file mutations, verify the target with
get_file_info or list_directory
after the operation when the user needs confirmation.
- For clipboard mutations, verify with
get_clipboard_text,
get_clipboard_files, or save_clipboard_image when the user needs
confirmation.
- For window mutations, verify with
list_windows when the user needs
confirmation.
Permissions Checklist
- Contacts access
- Calendars access
- Reminders access
- Automation permission for app control
- Accessibility permission for system controls and window management
- Screen Recording permission for screenshots and improved window discovery
- Safari setting: Allow JavaScript from Apple Events
- Google Chrome installed for CDP tools
- Full Disk Access for reading Messages database
- Automation permission for Finder when revealing, trashing, or reading selection
Source: altic-dev/altic-mcp — distributed by TomeVault.
1---2name: altic-studio3description: macOS automation skill for AppleScript actions and Chrome browser control via MCP CDP tools. Use when this capability is needed.4---56# Altic Studio78`altic-studio` provides two automation modes:9101. AppleScript mode for macOS apps and system actions112. MCP CDP mode for Google Chrome browser control123. MCP file mode for safe Finder and filesystem operations134. MCP clipboard mode for text, file, and image pasteboard operations145. MCP window/workspace mode for arranging macOS apps and windows1516It also includes Swift utility scripts for active-display screenshots, clipboard17file/image operations, and window/workspace management on macOS.1819## Mode A: AppleScript (macOS apps)2021- Always execute AppleScript through Bash with `osascript`.22- Always run from workspace root as the working directory.23- Quote script paths and arguments.24- Prefer direct script invocation; do not route through Python wrappers unless explicitly requested.2526Command templates:2728```bash29osascript "skills/altic-studio/scripts/<script>.applescript" [arg1] [arg2] ...30```3132### AppleScript Capabilities3334The full Altic automation surface is exposed as scripts under `skills/altic-studio/scripts`:3536- `open-application.applescript` - args: `<app_name>`37- `send-message.applescript` - args: `<phone_or_handle> <message>`38- `read-recent-messages.applescript` - args: `<phone_or_handle> <count>`39- `fetch-all-contacts.applescript` - args: none40- `set-reminder.applescript` - args: `<text> <YYYY-MM-DD HH:MM> [list_name]`41- `create-note.applescript` - args: `<title> <body> [folder]`42- `search-for-note.applescript` - args: `<query> [max_results]`43- `create-calendar-event.applescript` - args: `<title> <YYYY-MM-DD HH:MM> <duration_minutes> [calendar]`44- `list-all-calendar-events-for-day.applescript` - args: `<YYYY-MM-DD>`45- `open-safari-tab.applescript` - args: `[url]`46- `close-safari-tab.applescript` - args: `[tab_index|-1]`47- `get-safari-tabs.applescript` - args: none48- `switch-safari-tab.applescript` - args: `<tab_index>`49- `run-safari-javascript.applescript` - args: `<javascript_code>`50- `navigate-safari.applescript` - args: `<url>`51- `reload-safari-page.applescript` - args: none52- `safari-go-back.applescript` - args: none53- `safari-go-forward.applescript` - args: none54- `open-safari-window.applescript` - args: `[url]`55- `close-safari-window.applescript` - args: none56- `get-safari-page-info.applescript` - args: none57- `decrease-brightness.applescript` - args: `[amount_0_to_1]`58- `increase-brightness.applescript` - args: `[amount_0_to_1]`59- `turn-up-volume.applescript` - args: `[amount_0_to_100]`60- `turn-down-volume.applescript` - args: `[amount_0_to_100]`61- `capture-screenshot.applescript` - args: `[output_path] [full|interactive|window]`62- `capture-active-screen.swift` - args: `<output_path>` (captures full display containing frontmost app)63- `clipboard.swift` - subcommands: `get-files`, `set-files <paths...>`, `save-image <output_path>`, `set-image <image_path>`64- `window-manager.swift` - subcommands: `get_frontmost_app`, `list_windows`, `focus_window`, `move_window`, `resize_window`, `center_window`, `tile_windows`, `minimize`, `hide_app`, `quit_app`6566Swift command template (for active-display screenshots):6768```bash69swift "skills/altic-studio/scripts/capture-active-screen.swift" "/tmp/active-screen.png"70```7172Swift command template (for window management):7374```bash75swift "skills/altic-studio/scripts/window-manager.swift" "list_windows" '{"include_minimized":false}'76```7778## Mode B: Chrome Browser Control (MCP CDP)7980Use MCP tools for deterministic Chrome automation:8182- `chrome_open_session`83- `chrome_navigate`84- `chrome_wait_for`85- `chrome_click`86- `chrome_type`87- `chrome_extract`88- `chrome_screenshot`89- `chrome_close_session`90- `chrome_list_sessions`91- `capture_active_screen`9293Execution pattern:94951. Open a Chrome session.962. Navigate and wait for stable selectors.973. Interact with click and type actions.984. Verify state with extraction.995. Capture screenshots on checkpoints or failures.1006. Close session.101102## Mode C: File Finder and File Operations (MCP)103104Use MCP file tools instead of shell commands when the user asks to find, inspect,105copy, move, rename, reveal, or trash files. These tools return JSON for106successful lookups and operations, and `Error: ...` strings for failures.107108Available tools:109110- `find_files` - args: `<query> [root] [max_results] [include_hidden] [kind]`111- `list_directory` - args: `<path> [include_hidden] [max_results]`112- `get_file_info` - args: `<path>`113- `copy_file` - args: `<source> <destination> [overwrite] [dry_run]`114- `copy_directory` - args: `<source> <destination> [overwrite] [dry_run]`115- `move_file` - args: `<source> <destination> [overwrite] [dry_run]`116- `rename_file` - args: `<path> <new_name> [overwrite] [dry_run]`117- `trash_file` - args: `<path> [dry_run]`118- `reveal_in_finder` - args: `<path>`119- `get_finder_selection` - args: none120121File workflow rules:122123- If the user refers to selected files, the current Finder window, or "this file",124 call `get_finder_selection` first.125- For ambiguous file names, call `find_files`, then `get_file_info`; ask for126 disambiguation when multiple plausible matches remain.127- Prefer `dry_run=true` before `copy_file`, `copy_directory`, `move_file`,128 `rename_file`, or `trash_file` when the target or destination is ambiguous.129- Do not overwrite unless the user explicitly asks for replacement; default130 `overwrite=false`.131- Use `trash_file`, not permanent deletion.132- Use `reveal_in_finder` after file operations when the user wants to see the133 result in Finder.134135## Mode D: Clipboard Operations (MCP)136137Use MCP clipboard tools instead of shell commands when the user asks to inspect,138copy, paste, clear, or save clipboard contents. These tools return JSON for text139and file operations, `Error: ...` strings for failures, and image content for140saved clipboard images.141142Available tools:143144- `get_clipboard_text` - args: `[max_chars]`145- `set_clipboard_text` - args: `<text>`146- `clear_clipboard` - args: none147- `get_clipboard_files` - args: none148- `set_clipboard_files` - args: `<paths>`149- `save_clipboard_image` - args: `[output_path]`150- `set_clipboard_image` - args: `<path>`151152Clipboard workflow rules:153154- Ask before overwriting clipboard contents unless the user explicitly asks to155 copy, set, clear, or replace the clipboard.156- Use `get_clipboard_text` first when the user asks what text is currently copied.157- Use `get_clipboard_files` when the user says they copied files in Finder or158 wants to paste copied files somewhere else.159- Use `save_clipboard_image` when the user wants to inspect, store, or transform160 an image currently on the clipboard.161- Use `set_clipboard_files` with existing paths only; resolve ambiguous file162 names with `find_files` before changing the clipboard.163- Use `set_clipboard_image` only for existing image files.164165## Mode E: Window and Workspace Operations (MCP)166167Use MCP window tools when the user asks to arrange the workspace, focus an app or168window, tile apps side by side, resize windows, minimize windows, hide apps, quit169apps, or inspect the frontmost app. These tools return JSON for successful170operations and `Error: ...` strings for failures.171172Available tools:173174- `get_frontmost_app` - args: none175- `list_windows` - args: `[app_name] [include_minimized]`176- `focus_window` - args: `[app_name] [window_id] [window_index]`177- `move_window` - args: `<x> <y> [app_name] [window_id] [window_index] [display_index]`178- `resize_window` - args: `<width> <height> [app_name] [window_id] [window_index] [display_index]`179- `center_window` - args: `[app_name] [window_id] [window_index] [display_index] [width] [height]`180- `tile_windows` - args: `[layout=columns|rows|grid] [app_names] [display_index] [padding]`181- `minimize` - args: `[app_name] [window_id] [window_index]`182- `hide_app` - args: `<app_name>`183- `quit_app` - args: `<app_name>`184185Window workflow rules:186187- Call `list_windows` before moving, resizing, minimizing, or focusing when the188 target app has multiple windows or the target is ambiguous.189- Prefer `app_name` for user-facing workflows and `window_id` for precise190 follow-up operations after `list_windows`.191- Use `display_index` when arranging windows on a specific display; otherwise192 tools choose the display containing the target window.193- Use `tile_windows` with explicit `app_names` when preparing a multi-app task.194- Do not call `quit_app` unless the user explicitly asked to close or quit that195 app.196- If a window mutation fails with an Accessibility error, tell the user to grant197 Accessibility permission to the host app running the MCP server.198199## Operational Rules200201- Validate date/time format before running reminder/calendar scripts.202- If contact lookup returns multiple options, ask for disambiguation before sending.203- If script output indicates permission issues, report exact permissions to enable.204- Prefer explicit CSS selectors and call `chrome_wait_for` before click/type on dynamic pages.205- After mutating actions in Chrome, verify expected page state with `chrome_extract`.206- For file mutations, verify the target with `get_file_info` or `list_directory`207 after the operation when the user needs confirmation.208- For clipboard mutations, verify with `get_clipboard_text`,209 `get_clipboard_files`, or `save_clipboard_image` when the user needs210 confirmation.211- For window mutations, verify with `list_windows` when the user needs212 confirmation.213214## Permissions Checklist215216- Contacts access217- Calendars access218- Reminders access219- Automation permission for app control220- Accessibility permission for system controls and window management221- Screen Recording permission for screenshots and improved window discovery222- Safari setting: Allow JavaScript from Apple Events223- Google Chrome installed for CDP tools224- Full Disk Access for reading Messages database225- Automation permission for Finder when revealing, trashing, or reading selection226227---228> Source: [altic-dev/altic-mcp](https://github.com/altic-dev/altic-mcp) — distributed by [TomeVault](https://tomevault.io).229<!-- tomevault:4.0:skill_md:2026-06-19 -->
tomevault-io