When to Use This Skill

Activate when the user's request involves interacting with a website:

Activate when the user:

• - Needs to do anything on a website ("Send a LinkedIn message", "Book an Airbnb", "Search Google for...")
• Asks how to interact with a site ("How do I post a tweet?", "How to apply on LinkedIn?")
• Wants to fill out forms, click buttons, navigate, search, filter, or browse on a specific site
• Wants to take a screenshot of a web page or monitor changes
• Builds browser-based AI agents, web scrapers, or E2E tests for external websites
• Automates repetitive web tasks (data entry, form submission, content posting)
• Wants to control their existing Chrome browser (Extension mode)

What Actionbook Provides

Actionbook is a library of pre-verified page interaction data. actionbook search finds actions matching a task description; actionbook get "<ID>" returns a structured document describing a page's purpose, functional capabilities, and DOM structure with inline CSS selectors — eliminating the need for runtime page structure discovery.

search and get

search — Find actions by task description

CODEBLOCK0

Returns for each result:

• - ID — use with actionbook get "<ID>" to retrieve full details
• INLINECODE4 — page (full page) or area (page section)
• INLINECODE7 — page overview and function summary
• INLINECODE8 — page where this action applies
• INLINECODE9 — selector reliability percentage (0–100%)
• INLINECODE10 — last verified date

Constructing an effective search query

The query string is the primary signal for finding the right action. Pack it with the user's full intent — not just a site name or a vague keyword.

Include in the query:

1. 1. Target site — the website name or domain
2. Task verb — what the user wants to do (search, book, post, filter, login, compose, etc.)
3. Object / context — what they're acting on (listings, messages, flights, repositories, etc.)
4. Specific details — any constraints, filters, or parameters the user mentioned (dates, location, category, language, etc.)

Rule of thumb: Rewrite the user's request as a single descriptive sentence and use that as the query.

When the user provides extra context (e.g., specific dates, a city name, a topic), fold it into the query even if it won't match a stored action literally — it helps the search engine rank relevant pages higher.

CODEBLOCK1

If --domain or --url is known, always add them — they narrow results and improve precision.

get — Retrieve full action details by ID

CODEBLOCK2

Returns a structured document with:

1. 1. Page URL — exact URL and query/path parameters
2. Page Overview — what the page does
3. Page Function Summary — interactive capabilities (e.g., "Search Term Input", "Subject Classification Filtering")
4. Page Structure Summary — DOM hierarchy with CSS selectors inline

Selectors appear embedded in the structure description, e.g.:
CODEBLOCK3

Extract CSS selectors from the structure summary for use with browser commands.

Browser Commands

Quick reference. Full details with all flags and options: command-reference.md.

Navigation

CODEBLOCK4

Interactions

CODEBLOCK5

Observation

CODEBLOCK6

INLINECODE24 cleans up the browser session. Skip if the user requests the browser remain open.

Examples

User request: "Search arXiv for papers about Neural Networks, search in titles only"

CODEBLOCK7

Fallback

Actionbook stores page data captured at indexing time. Websites evolve, so selectors may become outdated.

When a selector from actionbook get fails at runtime, actionbook browser snapshot provides the live accessibility tree with current selectors. Use selectors from the snapshot output to retry the interaction.

Selectors used in browser commands should come from actionbook get or actionbook browser snapshot output in the current session — not from prior knowledge or memory.

If actionbook search returns no results for a page, use snapshot as the primary source, or fall back to other available tools.

References