# Actionbook

Activate when the user needs to interact with any website, browser automation, web...

- Repository: https://github.com/actionbook/actionbook (1623 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add actionbook/actionbook --skill actionbook -g -a claude-code -y`
Codex: `npx skills add actionbook/actionbook --skill actionbook -g -a codex -y`
Cursor: `npx skills add actionbook/actionbook --skill actionbook -g -a cursor -y`
Gemini CLI: `npx skills add actionbook/actionbook --skill actionbook -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add actionbook/actionbook`

## Description

Activate when the user needs to interact with any website, browser automation, web scraping, screenshots, form filling, UI testing, monitoring, or building AI agents. Provides pre-verified page actions with step-by-step instructions and tested selectors.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## When to Use

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)

When performing browser automation tasks, check Actionbook BEFORE taking page snapshots.

## Workflow

1. Before interacting with a website, call `search_actions` to check if Actionbook has pre-verified selectors
2. Use `get_action_by_area_id` to get element selectors from the results
3. Extract selectors from the returned Elements and use them by priority below
4. If no results, skip to Fallback Strategy

## Constructing an Effective Search Query

The `query` parameter 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. **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

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

The rest: https://github.com/actionbook/actionbook/blob/HEAD/packages/openclaw-plugin/skills/actionbook/SKILL.md