[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T98CD6XK30QRMF8209QVM":3,"skill-same:01M77T98CD6XK30QRMF8209QVM":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77T98CD6XK30QRMF8209QVM","safari-control",null,"Use Safari directly on macOS when work must happen in the user's real Safari session instead of a separate automation browser. Best for reading the current tab, inspecting the live session layout, operating Safari menu bar or native toolbar controls, reading page text and structure, running page JavaScript, waiting for page conditions, exporting page artifacts, and performing lightweight DOM interactions in the active Safari tab. If Safari JavaScript from Apple Events is disabled, guide the user to enable it or fall back to desktop-control for visual interaction.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fsafari-control\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: safari-control\ndescription: Use Safari directly on macOS when work must happen in the user's real Safari session instead of a separate automation browser. Best for reading the current tab, inspecting the live session layout, operating Safari menu bar or native toolbar controls, reading page text and structure, running page JavaScript, waiting for page conditions, exporting page artifacts, and performing lightweight DOM interactions in the active Safari tab. If Safari JavaScript from Apple Events is disabled, guide the user to enable it or fall back to desktop-control for visual interaction.\n---\n\n# Safari Control\n\nUse this skill when the task must happen in **Safari itself**:\n\n- The user is already logged in there\n- Safari extensions, cookies, or profiles matter\n- You need the current tab, tab list, page URL, or page text\n- A headless browser would not reflect the real session\n\nDo **not** force Safari to behave like Playwright. Prefer Safari's session access and DOM helpers first, Safari native UI automation second, and `desktop-control` only for pointer-heavy UI.\n\n## Core Tool\n\nRun commands from the `safari-control` skill directory so the relative `scripts\u002F` path resolves correctly.\n\n```bash\nswift scripts\u002Fsafari_control.swift \u003Ccommand>\n```\n\n## Recommended Flow\n\nUse this exact flow unless the task clearly starts in one specific layer:\n\n1. Check environment and active page:\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift current --json\n```\n\n`doctor` is the branch point:\n\n- `safari_js=false`: do not use DOM commands until the user enables JavaScript from Apple Events.\n- `accessibility=false`: do not use native Safari chrome commands.\n- `screenshot_background=false`: use `screenshot --mode foreground` when you need an image.\n- If Safari is missing required permissions or features, tell the user before proceeding. In particular, check whether Safari allows Automation, JavaScript in the Smart Search field, and JavaScript from Apple Events. Enabling these unlocks more functionality, but also increases risk because automation and scripted interactions gain more power over the user's Safari session. If the user refuses, do not keep pushing the recommendation and continue with the reduced feature set.\n\n2. If Safari session state matters, inspect it before mutating anything:\n\n```bash\nswift scripts\u002Fsafari_control.swift list-windows --json\nswift scripts\u002Fsafari_control.swift list-tabs --json\n```\n\n3. If you need page content or web-page actions, verify DOM access:\n\n```bash\nswift scripts\u002Fsafari_control.swift check-js\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\n```\n\n4. Choose the lowest layer that fits:\n\n- Prefer **DOM commands** for page content, forms, links, and standard web controls.\n- Use **native Safari controls or menus** for the smart search field, toolbar buttons, tab groups, and menu bar commands.\n- Use **desktop-control** only for extension popups, native pickers, pointer-heavy drag\u002Fdrop, or UI Accessibility cannot expose.\n- When you want to draw the user's attention to important content on the page, you may use JavaScript to visually highlight it, such as adding a red outline, background tint, or temporary annotation.\n\n## Command Layers\n\n### 1. Environment and Session\n\nUse for machine-readable state and tab\u002Fwindow management.\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift current --json\nswift scripts\u002Fsafari_control.swift list-windows --json\nswift scripts\u002Fsafari_control.swift list-tabs --json\nswift scripts\u002Fsafari_control.swift save-session .\u002Fsession.json --front-only\nswift scripts\u002Fsafari_control.swift restore-session .\u002Fsession.json\nswift scripts\u002Fsafari_control.swift new-window https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift switch-window 2\nswift scripts\u002Fsafari_control.swift switch-tab 2 --window 1\nswift scripts\u002Fsafari_control.swift switch-tab-title 'Dashboard'\nswift scripts\u002Fsafari_control.swift switch-tab-url '\u002Fdashboard'\nswift scripts\u002Fsafari_control.swift duplicate-tab\nswift scripts\u002Fsafari_control.swift close-tab --tab 2 --window 1\nswift scripts\u002Fsafari_control.swift close-window --window 2\n```\n\nRules:\n\n- Prefer `--json` for agent-readable output.\n- Most read-only page commands support `--window N --tab M`, so you can inspect background tabs without switching focus.\n- `save-session` before invasive work when preserving the user's layout matters.\n- `restore-session` is additive: it recreates windows and tabs, it does not merge with or close current ones.\n\n### 2. Page Read and Inspect\n\nUse when JavaScript from Apple Events is enabled and the target is inside the web page.\n\n```bash\nswift scripts\u002Fsafari_control.swift snapshot --limit 20 --heading-limit 10 --form-limit 5\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift interactive --json\nswift scripts\u002Fsafari_control.swift query 'form input' --json\nswift scripts\u002Fsafari_control.swift element-info 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift find-text 'Buy now' --json\nswift scripts\u002Fsafari_control.swift exists 'button[data-testid=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift count 'button'\nswift scripts\u002Fsafari_control.swift get-text --mode article\nswift scripts\u002Fsafari_control.swift extract-links --json\nswift scripts\u002Fsafari_control.swift extract-tables --json\nswift scripts\u002Fsafari_control.swift run-js 'document.title'\nswift scripts\u002Fsafari_control.swift eval-js 'document.querySelectorAll(\\\"a\\\").length'\n```\n\nRules:\n\n- Prefer `snapshot` before manual probing on unfamiliar pages.\n- Prefer `snapshot --interactive-only` when you only need actionable controls and want smaller output.\n- Prefer `get-text --mode article` before `body`; it is usually less noisy.\n- Prefer `element-info` when a selector exists but behaves unexpectedly.\n\n### 3. Page Actions and Waits\n\nUse for standard DOM interactions after confirming the target is inside the page.\n\n```bash\nswift scripts\u002Fsafari_control.swift focus 'input[name=\\\"email\\\"]'\nswift scripts\u002Fsafari_control.swift focus-text 'Email' --selector 'input, textarea, select'\nswift scripts\u002Fsafari_control.swift fill 'input[name=\\\"email\\\"]' 'user@example.com'\nswift scripts\u002Fsafari_control.swift click 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift click-text 'Continue' --exact\nswift scripts\u002Fsafari_control.swift select-option 'select[name=\\\"country\\\"]' CN --by value\nswift scripts\u002Fsafari_control.swift check '#agree'\nswift scripts\u002Fsafari_control.swift uncheck '#agree'\nswift scripts\u002Fsafari_control.swift upload 'input[type=\\\"file\\\"]' .\u002Favatar.png\nswift scripts\u002Fsafari_control.swift submit 'form'\nswift scripts\u002Fsafari_control.swift wait-selector 'form' --visible\nswift scripts\u002Fsafari_control.swift wait-text 'Success'\nswift scripts\u002Fsafari_control.swift wait-count '.result-item' 10 --op ge\nswift scripts\u002Fsafari_control.swift wait-title 'Success'\nswift scripts\u002Fsafari_control.swift wait-url '\u002Fsuccess'\nswift scripts\u002Fsafari_control.swift wait-download 'report-*.csv'\nswift scripts\u002Fsafari_control.swift reload\nswift scripts\u002Fsafari_control.swift back\nswift scripts\u002Fsafari_control.swift forward\n```\n\nRules:\n\n- Prefer `exists`, `count`, `wait-*`, and `snapshot` to branch explicitly before acting.\n- After an action, wait on a concrete condition instead of sleeping.\n- Use `press-key` and `press-shortcut` only for page-level DOM handlers, not Safari chrome.\n- `back`, `forward`, and `reload` return structured before\u002Fafter state for change detection.\n\n### 4. Native Safari UI\n\nUse when the target is Safari chrome, not the page.\n\n```bash\nswift scripts\u002Fsafari_control.swift list-menu-bar --json\nswift scripts\u002Fsafari_control.swift list-menu-items View --json\nswift scripts\u002Fsafari_control.swift click-menu View 'Reload Page'\nswift scripts\u002Fsafari_control.swift list-native-controls --json\nswift scripts\u002Fsafari_control.swift focus-native-control WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD --field identifier --exact\nswift scripts\u002Fsafari_control.swift set-native-value WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD 'https:\u002F\u002Fexample.com' --field identifier --exact\nswift scripts\u002Fsafari_control.swift press-native-control ReloadButton --field identifier --exact\nswift scripts\u002Fsafari_control.swift perform-native-action WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD AXConfirm --field identifier --exact\nswift scripts\u002Fsafari_control.swift list-native-menu-items NewTabGroupButton --field identifier --exact --json\nswift scripts\u002Fsafari_control.swift click-native-menu-item NewTabGroupButton 'New Empty Tab Group' --field identifier --exact\nswift scripts\u002Fsafari_control.swift native-open-url https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift native-search 'open claw'\nswift scripts\u002Fsafari_control.swift native-search 'open claw' --confirm-mode both\nswift scripts\u002Fsafari_control.swift press-system-shortcut Cmd+L\nswift scripts\u002Fsafari_control.swift press-system-key Enter\n```\n\nRules:\n\n- The menu examples in this section assume Safari is running with an English UI.\n- Start with `list-native-controls --json` before guessing identifiers.\n- The native control JSON now includes `pressable`, `focusable`, `settable`, and `menuable` fields. Use those before choosing `press-native-control`, `focus-native-control`, `set-native-value`, or menu actions.\n- `native-open-url` and `native-search` default to `--confirm-mode ax`. Use `enter` or `both` only if Safari's native confirm path is insufficient on that machine.\n- Use `list-menu-items` or `list-native-menu-items` before clicking when Safari is localized.\n\n## Common Task Templates\n\n### Read the current page\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift check-js\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift get-text --mode article\n```\n\n### Fill a form in the real Safari session\n\n```bash\nswift scripts\u002Fsafari_control.swift current --json\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift fill 'input[name=\\\"email\\\"]' 'user@example.com'\nswift scripts\u002Fsafari_control.swift click 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift wait-url '\u002Fsuccess'\n```\n\n### Operate Safari's own address bar or toolbar\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift list-native-controls --json\nswift scripts\u002Fsafari_control.swift native-open-url https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift press-native-control ReloadButton --field identifier --exact\n```\n\n## Export and Evidence\n\nUse when you need durable files instead of transient terminal output.\n\n```bash\nswift scripts\u002Fsafari_control.swift screenshot .\u002Fsafari.png\nswift scripts\u002Fsafari_control.swift screenshot .\u002Fsafari-foreground.png --mode foreground\nswift scripts\u002Fsafari_control.swift snapshot-with-screenshot .\u002Fsafari.png --path .\u002Fsnapshot.json\nswift scripts\u002Fsafari_control.swift save-html .\u002Fpage.html\nswift scripts\u002Fsafari_control.swift save-text .\u002Fpage.txt --mode article\nswift scripts\u002Fsafari_control.swift save-links .\u002Flinks.json\nswift scripts\u002Fsafari_control.swift save-tables .\u002Ftables.json\nswift scripts\u002Fsafari_control.swift save-snapshot .\u002Fsnapshot.json --interactive-only\nswift scripts\u002Fsafari_control.swift save-page-bundle .\u002Fpage-bundle --interactive-only --zip\n```\n\nRules:\n\n- `auto` screenshot mode tries background capture first and falls back to foreground.\n- `snapshot-with-screenshot` and `save-page-bundle` can read a background tab via `--window` \u002F `--tab`, but the screenshot still comes from the visible Safari window.\n\n## JavaScript Access Requirement\n\nIf `check-js` reports disabled, tell the user to enable:\n\n1. Safari Settings\n2. Advanced\n3. Developer features if needed\n4. Developer\n5. `Allow JavaScript from Apple Events`\n\nThen retry `check-js`.\n\nIf native Safari automation or script-driven workflows are blocked, also tell the user to verify Safari settings such as:\n\n1. Allow Automation\n2. Allow JavaScript in the Smart Search field\n3. Allow JavaScript from Apple Events\n\nExplain that these settings enable more Safari-control features, but they also grant more power to automation and scripted interactions. If the user declines, continue with only the features that remain available.\n\n## Release and Distribution\n\nThese are maintenance commands, not the normal interaction path:\n\n```bash\nswift scripts\u002Fsafari_control.swift build .\u002Fdist\nswift scripts\u002Fsafari_control.swift build .\u002Fdist --zip\nswift scripts\u002Fsafari_control.swift release\nswift scripts\u002Fsafari_control.swift release --name safari-control-demo --notes 'Internal preview build'\nswift scripts\u002Fsafari_control.swift version\n```\n\nUse these when you want a compiled binary, a release directory, zip artifacts, or build metadata with git and environment information.\n\n## Limits\n\n- Safari scripting is strong for session state, structured page inspection, waits, and standard DOM interactions.\n- Safari scripting is not a robust replacement for full browser automation.\n- Complex form workflows, native pickers, extension UIs, canvas apps, and pointer-heavy interactions should move to `desktop-control`.\n- `upload` is for small files injected into `input[type=file]`, not large native picker workflows.\n- `wait-download` is filesystem polling, not a Safari download API.\n- `export-cookies` exposes `document.cookie`, not HttpOnly cookies or the full Safari cookie jar.\n- `export-storage` only sees the current origin.\n","# Safari Control\n\nUse this skill when the task must happen in **Safari itself**:\n\n- The user is already logged in there\n- Safari extensions, cookies, or profiles matter\n- You need the current tab, tab list, page URL, or page text\n- A headless browser would not reflect the real session\n\nDo **not** force Safari to behave like Playwright. Prefer Safari's session access and DOM helpers first, Safari native UI automation second, and `desktop-control` only for pointer-heavy UI.\n\n## Core Tool\n\nRun commands from the `safari-control` skill directory so the relative `scripts\u002F` path resolves correctly.\n\n```bash\nswift scripts\u002Fsafari_control.swift \u003Ccommand>\n```\n\n## Recommended Flow\n\nUse this exact flow unless the task clearly starts in one specific layer:\n\n1. Check environment and active page:\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift current --json\n```\n\n`doctor` is the branch point:\n\n- `safari_js=false`: do not use DOM commands until the user enables JavaScript from Apple Events.\n- `accessibility=false`: do not use native Safari chrome commands.\n- `screenshot_background=false`: use `screenshot --mode foreground` when you need an image.\n- If Safari is missing required permissions or features, tell the user before proceeding. In particular, check whether Safari allows Automation, JavaScript in the Smart Search field, and JavaScript from Apple Events. Enabling these unlocks more functionality, but also increases risk because automation and scripted interactions gain more power over the user's Safari session. If the user refuses, do not keep pushing the recommendation and continue with the reduced feature set.\n\n2. If Safari session state matters, inspect it before mutating anything:\n\n```bash\nswift scripts\u002Fsafari_control.swift list-windows --json\nswift scripts\u002Fsafari_control.swift list-tabs --json\n```\n\n3. If you need page content or web-page actions, verify DOM access:\n\n```bash\nswift scripts\u002Fsafari_control.swift check-js\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\n```\n\n4. Choose the lowest layer that fits:\n\n- Prefer **DOM commands** for page content, forms, links, and standard web controls.\n- Use **native Safari controls or menus** for the smart search field, toolbar buttons, tab groups, and menu bar commands.\n- Use **desktop-control** only for extension popups, native pickers, pointer-heavy drag\u002Fdrop, or UI Accessibility cannot expose.\n- When you want to draw the user's attention to important content on the page, you may use JavaScript to visually highlight it, such as adding a red outline, background tint, or temporary annotation.\n\n## Command Layers\n\n### 1. Environment and Session\n\nUse for machine-readable state and tab\u002Fwindow management.\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift current --json\nswift scripts\u002Fsafari_control.swift list-windows --json\nswift scripts\u002Fsafari_control.swift list-tabs --json\nswift scripts\u002Fsafari_control.swift save-session .\u002Fsession.json --front-only\nswift scripts\u002Fsafari_control.swift restore-session .\u002Fsession.json\nswift scripts\u002Fsafari_control.swift new-window https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift switch-window 2\nswift scripts\u002Fsafari_control.swift switch-tab 2 --window 1\nswift scripts\u002Fsafari_control.swift switch-tab-title 'Dashboard'\nswift scripts\u002Fsafari_control.swift switch-tab-url '\u002Fdashboard'\nswift scripts\u002Fsafari_control.swift duplicate-tab\nswift scripts\u002Fsafari_control.swift close-tab --tab 2 --window 1\nswift scripts\u002Fsafari_control.swift close-window --window 2\n```\n\nRules:\n\n- Prefer `--json` for agent-readable output.\n- Most read-only page commands support `--window N --tab M`, so you can inspect background tabs without switching focus.\n- `save-session` before invasive work when preserving the user's layout matters.\n- `restore-session` is additive: it recreates windows and tabs, it does not merge with or close current ones.\n\n### 2. Page Read and Inspect\n\nUse when JavaScript from Apple Events is enabled and the target is inside the web page.\n\n```bash\nswift scripts\u002Fsafari_control.swift snapshot --limit 20 --heading-limit 10 --form-limit 5\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift interactive --json\nswift scripts\u002Fsafari_control.swift query 'form input' --json\nswift scripts\u002Fsafari_control.swift element-info 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift find-text 'Buy now' --json\nswift scripts\u002Fsafari_control.swift exists 'button[data-testid=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift count 'button'\nswift scripts\u002Fsafari_control.swift get-text --mode article\nswift scripts\u002Fsafari_control.swift extract-links --json\nswift scripts\u002Fsafari_control.swift extract-tables --json\nswift scripts\u002Fsafari_control.swift run-js 'document.title'\nswift scripts\u002Fsafari_control.swift eval-js 'document.querySelectorAll(\\\"a\\\").length'\n```\n\nRules:\n\n- Prefer `snapshot` before manual probing on unfamiliar pages.\n- Prefer `snapshot --interactive-only` when you only need actionable controls and want smaller output.\n- Prefer `get-text --mode article` before `body`; it is usually less noisy.\n- Prefer `element-info` when a selector exists but behaves unexpectedly.\n\n### 3. Page Actions and Waits\n\nUse for standard DOM interactions after confirming the target is inside the page.\n\n```bash\nswift scripts\u002Fsafari_control.swift focus 'input[name=\\\"email\\\"]'\nswift scripts\u002Fsafari_control.swift focus-text 'Email' --selector 'input, textarea, select'\nswift scripts\u002Fsafari_control.swift fill 'input[name=\\\"email\\\"]' 'user@example.com'\nswift scripts\u002Fsafari_control.swift click 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift click-text 'Continue' --exact\nswift scripts\u002Fsafari_control.swift select-option 'select[name=\\\"country\\\"]' CN --by value\nswift scripts\u002Fsafari_control.swift check '#agree'\nswift scripts\u002Fsafari_control.swift uncheck '#agree'\nswift scripts\u002Fsafari_control.swift upload 'input[type=\\\"file\\\"]' .\u002Favatar.png\nswift scripts\u002Fsafari_control.swift submit 'form'\nswift scripts\u002Fsafari_control.swift wait-selector 'form' --visible\nswift scripts\u002Fsafari_control.swift wait-text 'Success'\nswift scripts\u002Fsafari_control.swift wait-count '.result-item' 10 --op ge\nswift scripts\u002Fsafari_control.swift wait-title 'Success'\nswift scripts\u002Fsafari_control.swift wait-url '\u002Fsuccess'\nswift scripts\u002Fsafari_control.swift wait-download 'report-*.csv'\nswift scripts\u002Fsafari_control.swift reload\nswift scripts\u002Fsafari_control.swift back\nswift scripts\u002Fsafari_control.swift forward\n```\n\nRules:\n\n- Prefer `exists`, `count`, `wait-*`, and `snapshot` to branch explicitly before acting.\n- After an action, wait on a concrete condition instead of sleeping.\n- Use `press-key` and `press-shortcut` only for page-level DOM handlers, not Safari chrome.\n- `back`, `forward`, and `reload` return structured before\u002Fafter state for change detection.\n\n### 4. Native Safari UI\n\nUse when the target is Safari chrome, not the page.\n\n```bash\nswift scripts\u002Fsafari_control.swift list-menu-bar --json\nswift scripts\u002Fsafari_control.swift list-menu-items View --json\nswift scripts\u002Fsafari_control.swift click-menu View 'Reload Page'\nswift scripts\u002Fsafari_control.swift list-native-controls --json\nswift scripts\u002Fsafari_control.swift focus-native-control WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD --field identifier --exact\nswift scripts\u002Fsafari_control.swift set-native-value WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD 'https:\u002F\u002Fexample.com' --field identifier --exact\nswift scripts\u002Fsafari_control.swift press-native-control ReloadButton --field identifier --exact\nswift scripts\u002Fsafari_control.swift perform-native-action WEB_BROWSER_ADDRESS_AND_SEARCH_FIELD AXConfirm --field identifier --exact\nswift scripts\u002Fsafari_control.swift list-native-menu-items NewTabGroupButton --field identifier --exact --json\nswift scripts\u002Fsafari_control.swift click-native-menu-item NewTabGroupButton 'New Empty Tab Group' --field identifier --exact\nswift scripts\u002Fsafari_control.swift native-open-url https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift native-search 'open claw'\nswift scripts\u002Fsafari_control.swift native-search 'open claw' --confirm-mode both\nswift scripts\u002Fsafari_control.swift press-system-shortcut Cmd+L\nswift scripts\u002Fsafari_control.swift press-system-key Enter\n```\n\nRules:\n\n- The menu examples in this section assume Safari is running with an English UI.\n- Start with `list-native-controls --json` before guessing identifiers.\n- The native control JSON now includes `pressable`, `focusable`, `settable`, and `menuable` fields. Use those before choosing `press-native-control`, `focus-native-control`, `set-native-value`, or menu actions.\n- `native-open-url` and `native-search` default to `--confirm-mode ax`. Use `enter` or `both` only if Safari's native confirm path is insufficient on that machine.\n- Use `list-menu-items` or `list-native-menu-items` before clicking when Safari is localized.\n\n## Common Task Templates\n\n### Read the current page\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift check-js\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift get-text --mode article\n```\n\n### Fill a form in the real Safari session\n\n```bash\nswift scripts\u002Fsafari_control.swift current --json\nswift scripts\u002Fsafari_control.swift snapshot --interactive-only --limit 30\nswift scripts\u002Fsafari_control.swift fill 'input[name=\\\"email\\\"]' 'user@example.com'\nswift scripts\u002Fsafari_control.swift click 'button[type=\\\"submit\\\"]'\nswift scripts\u002Fsafari_control.swift wait-url '\u002Fsuccess'\n```\n\n### Operate Safari's own address bar or toolbar\n\n```bash\nswift scripts\u002Fsafari_control.swift doctor\nswift scripts\u002Fsafari_control.swift list-native-controls --json\nswift scripts\u002Fsafari_control.swift native-open-url https:\u002F\u002Fexample.com\nswift scripts\u002Fsafari_control.swift press-native-control ReloadButton --field identifier --exact\n```\n\n## Export and Evidence\n\nUse when you need durable files instead of transient terminal output.\n\n```bash\nswift scripts\u002Fsafari_control.swift screenshot .\u002Fsafari.png\nswift scripts\u002Fsafari_control.swift screenshot .\u002Fsafari-foreground.png --mode foreground\nswift scripts\u002Fsafari_control.swift snapshot-with-screenshot .\u002Fsafari.png --path .\u002Fsnapshot.json\nswift scripts\u002Fsafari_control.swift save-html .\u002Fpage.html\nswift scripts\u002Fsafari_control.swift save-text .\u002Fpage.txt --mode article\nswift scripts\u002Fsafari_control.swift save-links .\u002Flinks.json\nswift scripts\u002Fsafari_control.swift save-tables .\u002Ftables.json\nswift scripts\u002Fsafari_control.swift save-snapshot .\u002Fsnapshot.json --interactive-only\nswift scripts\u002Fsafari_control.swift save-page-bundle .\u002Fpage-bundle --interactive-only --zip\n```\n\nRules:\n\n- `auto` screenshot mode tries background capture first and falls back to foreground.\n- `snapshot-with-screenshot` and `save-page-bundle` can read a background tab via `--window` \u002F `--tab`, but the screenshot still comes from the visible Safari window.\n\n## JavaScript Access Requirement\n\nIf `check-js` reports disabled, tell the user to enable:\n\n1. Safari Settings\n2. Advanced\n3. Developer features if needed\n4. Developer\n5. `Allow JavaScript from Apple Events`\n\nThen retry `check-js`.\n\nIf native Safari automation or script-driven workflows are blocked, also tell the user to verify Safari settings such as:\n\n1. Allow Automation\n2. Allow JavaScript in the Smart Search field\n3. Allow JavaScript from Apple Events\n\nExplain that these settings enable more Safari-control features, but they also grant more power to automation and scripted interactions. If the user declines, continue with only the features that remain available.\n\n## Release and Distribution\n\nThese are maintenance commands, not the normal interaction path:\n\n```bash\nswift scripts\u002Fsafari_control.swift build .\u002Fdist\nswift scripts\u002Fsafari_control.swift build .\u002Fdist --zip\nswift scripts\u002Fsafari_control.swift release\nswift scripts\u002Fsafari_control.swift release --name safari-control-demo --notes 'Internal preview build'\nswift scripts\u002Fsafari_control.swift version\n```\n\nUse these when you want a compiled binary, a release directory, zip artifacts, or build metadata with git and environment information.\n\n## Limits\n\n- Safari scripting is strong for session state, structured page inspection, waits, and standard DOM interactions.\n- Safari scripting is not a robust replacement for full browser automation.\n- Complex form workflows, native pickers, extension UIs, canvas apps, and pointer-heavy interactions should move to `desktop-control`.\n- `upload` is for small files injected into `input[type=file]`, not large native picker workflows.\n- `wait-download` is filesystem polling, not a Safari download API.\n- `export-cookies` exposes `document.cookie`, not HttpOnly cookies or the full Safari cookie jar.\n- `export-storage` only sees the current origin.\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fs\u002Fsafari-control",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill safari-control",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill safari-control",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill safari-control","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fsafari-control\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]