automating-chrome

Automate Chrome tab control on macOS using JXA and AppleScript.

63|12|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iBz-04/gloamy --skill automating-chrome-ibz-04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automating-chrome
Source: https://github.com/iBz-04/gloamy/tree/main/skills/automating-chrome
Command: npx skills add https://github.com/iBz-04/gloamy --skill automating-chrome-ibz-04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you control Chrome or Chromium-based browsers to open, navigate, and manage tabs automatically from macOS using JXA (JavaScript for Automation) and AppleScript dictionary discovery.

Core Features & Use Cases

  • Tab and window automation: Create tabs with URLs, read tab/window properties, and close tabs by URL patterns.
  • In-page interaction via DOM automation: Use execute() to run JavaScript for actions like clicking buttons and setting form values.
  • Reliable data extraction with tunneling: Extract page data using clipboard or localStorage patterns when execute() cannot return results directly.
  • Cross-browser dictionary guidance: Map common Chromium variants (Brave, Edge, Arc, Vivaldi, Chromium) by bundle/app names and verify dictionary availability in Script Editor.
  • Use Case: When you need to automatically collect titles or URLs from multiple pages and then clean up unwanted tabs, this Skill provides the workflow and recipes.

Quick Start

Ask the AI to automate Chrome to open a set of URLs, extract each page title using tunneling (localStorage or clipboard), and then close the tabs that match a provided pattern.

Frequently Asked Questions about automating-chrome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Chrome tabs on macOS using JXA?

JXA automates Chrome tabs on macOS by using AppleScript dictionary discovery to create tabs, read properties, and close tabs matching URL patterns. You can execute in-page JavaScript for DOM interactions like clicking buttons and setting form values.

Can I extract page data from Chrome when execute() cannot return results directly?

When execute() cannot return results directly in Chrome automation, you can extract page data using tunneling patterns. This involves routing data through the clipboard or localStorage to reliably retrieve information from the browser.

Does JXA browser scripting work with Chromium-based browsers like Brave, Edge, or Arc?

JXA browser scripting works with Chromium variants like Brave, Edge, Arc, and Vivaldi by mapping their bundle and app names. You must verify AppleScript dictionary availability for each browser variant in Script Editor before automating.

What's the best way to collect titles and URLs from multiple Chrome tabs and clean up unwanted ones?

The best way to collect titles and URLs from multiple Chrome tabs is using JXA automation. Open target URLs, extract page titles using localStorage or clipboard tunneling patterns, then close tabs matching your provided URL pattern for cleanup.

Why does Chrome automation with JXA require permission checks and AppleScript dictionary availability?

Chrome automation with JXA requires permission checks and AppleScript dictionary availability because macOS enforces security controls for scripting. Without correct browser name mapping and dictionary verification, scripts fail to control tabs or execute in-page JavaScript reliably.