New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Actionbook Browser Action Manuals

by smallnest in smallnest/goclaw

Looks up action manuals with verified selectors for multi-step website tasks, then drives the browser with the actionbook CLI in a dedicated or an existing Chrome session.

MITAuto-check: warningsProductivity & Automation

Install Actionbook Browser Action Manuals

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add smallnest/goclaw --skill actionbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install smallnest/goclaw actionbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/smallnest/goclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/builtin_skills/actionbook .claude/skills/actionbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
actionbook
GitHub stars
598
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
942 words
Files
4 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Looks up action manuals with verified selectors for multi-step website tasks, then drives the browser with the actionbook CLI in a dedicated or an existing Chrome session.

  • Works in 3 steps: Get Action Manual → Execute with Browser (CDP mode — default) → (alt): Execute with Extension mode
  • Completing a multi-step task on a website, such as sending a message
  • SKILL.md covers When to Use This Skill, Browser Modes, How to Use and Action Manual Format, plus 7 more sections
  • Reaches arxiv.org and airbnb.com

What it does

Actionbook has the agent search for an action manual before touching a site. A manual lists the page URL, the page structure and the UI elements with CSS or XPath selectors, so multi-step tasks such as sending a LinkedIn message are done against known selectors instead of guessed ones. It also applies to building browser-based agents, writing scrapers and writing end-to-end tests for external sites.

Two browser modes exist. The default launches a dedicated browser through the Chrome DevTools Protocol, which suits clean environments, headless runs, CI/CD and profile-based isolation. Extension mode, switched on with --extension or ACTIONBOOK_EXTENSION=1, controls your already-open Chrome through a Chrome extension and WebSocket bridge, keeping its logins, cookies and tabs. The same actionbook browser commands work in both, and reference files cover authentication, the command set and extension troubleshooting.

When your agent uses it

  • Completing a multi-step task on a website, such as sending a message
  • Building a browser-based agent or scraper that needs reliable selectors
  • Writing end-to-end tests against an external website
  • Operating your already-open Chrome with its existing logins

Example prompts

  • “Search actionbook for how to run an advanced search on arXiv, then do it in the browser.”
  • “Use extension mode so I stay logged in, and fill out the expense form in my open tab.”
  • “Write an end-to-end test for the checkout flow on our staging site using verified selectors.”

Requirements

  • The actionbook command line tool
  • Chrome with the Actionbook extension for extension mode

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Get Action Manual
  2. Execute with Browser (CDP mode — default)
  3. (alt): Execute with Extension mode

What it can do on your machine

Read from SKILL.md and the folder at commit e05c79d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • arxiv.org
    • airbnb.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Actionbook Browser Action Manuals loads about 4.1k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 942 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:27
    wants to operate on their already-open Chrome (with existing logins, cookies, tabs)

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from smallnest/goclaw at commit e05c79d, republished under its MIT licence (© smallnest). 942 words, ~4,126 tokens.

Download SKILL.mdSave it as .claude/skills/actionbook/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
actionbook
description
This skill should be used when the user needs to automate multi-step website tasks. Activates for browser automation, web scraping, UI testing, or building AI agents. Provides complete action manuals with step-by-step instructions and verified selectors.

When to Use This Skill

Activate this skill when the user:

  • Needs to complete a multi-step task ("Send a LinkedIn message", "Book an Airbnb")
  • Asks how to interact with a website ("How do I post a tweet?")
  • Builds browser-based AI agents or web scrapers
  • Writes E2E tests for external websites
  • Navigates to any new page during browser automation
  • Wants to control their existing Chrome browser (Extension mode)

Browser Modes

Actionbook supports two browser control modes:

ModeFlagUse Case
CDP (default)(none)Launches a dedicated browser instance via Chrome DevTools Protocol
Extension--extensionControls the user's existing Chrome browser via a Chrome Extension + WebSocket bridge

When to use Extension mode:

  • The user wants to operate on their already-open Chrome (with existing logins, cookies, tabs)
  • The task requires interacting with pages that need the user's real session state
  • The user explicitly mentions their Chrome browser, extension, or existing tabs

When to use CDP mode (default):

  • Clean browser environment is preferred
  • Headless automation or CI/CD
  • Profile-based session isolation is needed

All actionbook browser commands work identically in both modes. The only difference is adding --extension flag (or setting ACTIONBOOK_EXTENSION=1).

How to Use

Phase 1: Get Action Manual
bash
# Step 1: Search for action manuals
actionbook search "arxiv search papers"
# Returns: area IDs with descriptions

# Step 2: Get the full manual (use area_id from search results)
actionbook get "arxiv.org:/search/advanced:default"
# Returns: Page structure, UI Elements with CSS/XPath selectors
Phase 2: Execute with Browser (CDP mode — default)
bash
# Step 3: Open browser
actionbook browser open "https://arxiv.org/search/advanced"

# Step 4: Use CSS selectors from Action Manual directly
actionbook browser fill "#terms-0-term" "Neural Network"
actionbook browser select "#terms-0-field" "title"
actionbook browser click "#date-filter_by-2"
actionbook browser fill "#date-year" "2025"
actionbook browser click "form[action='/search/advanced'] button.is-link"

# Step 5: Wait for results
actionbook browser wait-nav

# Step 6: Extract data
actionbook browser text

# Step 7: Close browser
actionbook browser close
Phase 2 (alt): Execute with Extension mode

Extension mode uses identical browser commands — just add --extension. But you must follow the full lifecycle below.

bash
# Step 3: Open URL in user's Chrome
actionbook --extension browser open "https://arxiv.org/search/advanced"

# Step 4-7: Same commands, just add --extension
actionbook --extension browser fill "#terms-0-term" "Neural Network"
actionbook --extension browser select "#terms-0-field" "title"
actionbook --extension browser click "#date-filter_by-2"
actionbook --extension browser fill "#date-year" "2025"
actionbook --extension browser click "form[action='/search/advanced'] button.is-link"
actionbook --extension browser wait-nav
actionbook --extension browser text

# Step 8: Cleanup (CRITICAL — see Extension Mode Lifecycle below)
actionbook --extension browser close    # release debug connection FIRST
actionbook extension stop               # then stop bridge server

Action Manual Format

Action manuals return:

  • Page URL - Target page address
  • Page Structure - DOM hierarchy and key sections
  • UI Elements - CSS/XPath selectors with element metadata
yaml
  ### button_advanced_search

  - ID: button_advanced_search
  - Description: Advanced search navigation button
  - Type: link
  - Allow Methods: click
  - Selectors:
    - role: getByRole('link', { name: 'Advanced Search' }) (confidence: 0.9)
    - css: button.button.is-small.is-cul-darker (confidence: 0.65)
    - xpath: //button[contains(@class, 'button')] (confidence: 0.55)

Action Search Commands

bash
actionbook search "<query>"                    # Basic search
actionbook search "<query>" --domain site.com  # Filter by domain
actionbook search "<query>" --url <url>        # Filter by URL
actionbook search "<query>" -p 2 -s 20         # Page 2, 20 results

actionbook get "<area_id>"                     # Full details with selectors
# area_id format: "site.com:/path:area_name"

actionbook sources list                        # List available sources
actionbook sources search "<query>"            # Search sources by keyword

Extension Setup & Management

Commands for managing the Chrome Extension bridge:

bash
actionbook extension install              # Install extension files to local config dir
actionbook extension path                 # Show extension directory (for Chrome "Load unpacked")
actionbook extension serve                # Start WebSocket bridge (keep running in background)
actionbook extension stop                 # Stop the running bridge server (sends SIGTERM)
actionbook extension status               # Check bridge and extension connection status
actionbook extension ping                 # Ping the extension to verify link is alive

Setup flow (one-time):

  1. actionbook extension install — extract extension files and register native messaging host
  2. Open chrome://extensions → enable Developer mode → Load unpacked → select the path from actionbook extension path
  3. actionbook extension serve — start bridge (keep running)
  4. Extension auto-connects via native messaging (no manual token needed in most cases). If auto-pairing fails: copy token from serve output → paste in extension popup → Save

Connection check before automation:

bash
actionbook extension status    # should show "running"
actionbook extension ping      # should show "responded"

Browser Commands

All browser commands below work in both CDP and Extension mode. For Extension mode, add --extension flag or set ACTIONBOOK_EXTENSION=1.

Navigation
bash
actionbook browser open <url>                  # Open URL in new tab
actionbook browser goto <url>                  # Navigate current page
actionbook browser back                        # Go back
actionbook browser forward                     # Go forward
actionbook browser reload                      # Reload page
actionbook browser pages                       # List open tabs
actionbook browser switch <page_id>            # Switch tab
actionbook browser close                       # Close browser
actionbook browser restart                     # Restart browser
actionbook browser connect <endpoint>          # Connect to existing browser (CDP port or URL)
Interactions (use CSS selectors from Action Manual)
bash
actionbook browser click "<selector>"                  # Click element
actionbook browser click "<selector>" --wait 1000      # Wait then click
actionbook browser fill "<selector>" "text"            # Clear and type
actionbook browser type "<selector>" "text"            # Append text
actionbook browser select "<selector>" "value"         # Select dropdown
actionbook browser hover "<selector>"                  # Hover
actionbook browser focus "<selector>"                  # Focus
actionbook browser press Enter                         # Press key
Get Information
bash
actionbook browser text                        # Full page text
actionbook browser text "<selector>"           # Element text
actionbook browser html                        # Full page HTML
actionbook browser html "<selector>"           # Element HTML
actionbook browser snapshot                    # Accessibility tree
actionbook browser viewport                    # Viewport dimensions
actionbook browser status                      # Browser detection info
Wait
bash
actionbook browser wait "<selector>"                   # Wait for element
actionbook browser wait "<selector>" --timeout 5000    # Custom timeout
actionbook browser wait-nav                            # Wait for navigation
Screenshots & Export
bash
# Ensure target directory exists before saving screenshots
actionbook browser screenshot                  # Save screenshot.png
actionbook browser screenshot output.png       # Custom path
actionbook browser screenshot --full-page      # Full page
actionbook browser pdf output.pdf              # Export as PDF
JavaScript & Inspection
bash
actionbook browser eval "document.title"               # Execute JS
actionbook browser inspect 100 200                     # Inspect at coordinates
actionbook browser inspect 100 200 --desc "login btn"  # With description
Cookies
bash
actionbook browser cookies list                # List all cookies
actionbook browser cookies get "name"          # Get cookie
actionbook browser cookies set "name" "value"  # Set cookie
actionbook browser cookies set "name" "value" --domain ".example.com"
actionbook browser cookies delete "name"       # Delete cookie
actionbook browser cookies clear               # Clear all

Global Flags

bash
actionbook --json <command>              # JSON output
actionbook --headless <command>          # Headless mode (CDP only)
actionbook --verbose <command>           # Verbose logging
actionbook -P <profile> <command>        # Use specific profile (CDP only)
actionbook --cdp <port|url> <command>    # CDP connection
actionbook --extension <command>         # Use Chrome Extension mode
# or: ACTIONBOOK_EXTENSION=1 actionbook <command>

Guidelines

  • Search by task description, not element name ("arxiv search papers" not "search button")
  • Use Action Manual selectors first - they are pre-verified and don't require snapshot
  • Prefer CSS ID selectors (#id) over XPath when both are provided
  • Fallback to snapshot when selectors fail - use actionbook browser snapshot then CSS selectors from the output
  • Re-snapshot after navigation - DOM changes invalidate previous state
  • Extension mode: follow the full lifecycle — pre-flight → connect → execute → cleanup (see Extension Mode Lifecycle)
  • Extension mode: verify extension is installed before starting bridge; prefer auto-pair over manual token
  • Extension mode: always run browser close before stopping the bridge to release the debug connection
  • Extension mode: the user's real browser is being controlled — avoid destructive actions (clearing all cookies, closing all tabs) without confirmation
  • Extension mode: L3 operations (some cookie/storage modifications) may require manual approval in the extension popup

Fallback Strategy

When Fallback is Needed

Actionbook stores pre-computed page data captured at indexing time. This data may become outdated as websites evolve:

  • Selector execution failure - The returned CSS/XPath selector does not match any element
  • Element mismatch - The selector matches an element with unexpected type or behavior
  • Multiple selector failures - Several selectors from the same action fail consecutively
Show full SKILL.md (372 more words)Show less
Fallback Approaches

When Action Manual selectors don't work:

  1. Snapshot the page - actionbook browser snapshot to get the current accessibility tree
  2. Inspect visually - actionbook browser screenshot to see the current state
  3. Inspect by coordinates - actionbook browser inspect <x> <y> to find elements
  4. Execute JS - actionbook browser eval "document.querySelector(...)" for dynamic queries
When to Exit

If actionbook search returns no results or action fails unexpectedly, use other available tools to continue the task.

Examples

End-to-end with Action Manual
bash
# 1. Find selectors
actionbook search "airbnb search" --domain airbnb.com

# 2. Get detailed selectors (area_id from search results)
actionbook get "airbnb.com:/:default"

# 3. Automate using pre-verified selectors
actionbook browser open "https://www.airbnb.com"
actionbook browser fill "input[data-testid='structured-search-input-field-query']" "Tokyo"
actionbook browser click "button[data-testid='structured-search-input-search-button']"
actionbook browser wait-nav
actionbook browser text
actionbook browser close
Extension mode: Operate on user's Chrome
bash
# Verify bridge is running
actionbook extension status

# Use the user's existing logged-in session
actionbook --extension browser open "https://github.com/notifications"
actionbook --extension browser wait-nav
actionbook --extension browser text ".notifications-list"
actionbook --extension browser screenshot notifications.png
Extension Mode Lifecycle (CRITICAL)

When using Extension mode, always follow this complete lifecycle: pre-flight → connect → execute → cleanup.

1. Pre-flight: Ask user about extension installation

Before any technical checks, ask the user whether they have the Actionbook Chrome Extension installed.

  • User confirms installed → proceed to Step 2 (Connect).
  • User says not installed → run the installation flow:
bash
# Install extension files locally
actionbook extension install
actionbook extension path
# → On macOS, copy to visible dir if needed:
#    cp -r "$(actionbook extension path)" ~/Document/actionbook-extension

Then guide the user to load it in Chrome:

  1. Open chrome://extensions → enable Developer mode
  2. Click "Load unpacked" → select the extension directory
  3. After user confirms loaded → proceed to Step 2

Limitation: The CLI can only verify that extension files exist locally. There is no way to detect whether Chrome has actually loaded the extension until a connection is attempted in Step 2.

2. Connect: Start bridge, auto-pair with retry

Start the bridge server and attempt auto-pairing. Retry up to 3 times before considering manual fallback.

bash
# Start bridge (run in background)
actionbook extension serve

# Attempt 1: Wait for auto-pairing via Native Messaging
sleep 3
actionbook extension ping
# → If ping succeeds → proceed to Step 3 (Execute)

# Attempt 2: If ping fails, wait longer and retry
sleep 5
actionbook extension ping
# → If ping succeeds → proceed to Step 3 (Execute)

# Attempt 3: Final retry
sleep 5
actionbook extension ping
# → If ping succeeds → proceed to Step 3 (Execute)

Only after all 3 auto-pair attempts fail, escalate based on the error:

  • "Extension not connected" → Ask user to verify the extension is enabled in chrome://extensions and retry
  • "Invalid token" → Only now provide the token from serve output for manual paste in the extension popup
  • Other errors → Check actionbook extension status for diagnostics

IMPORTANT: Do NOT expose the session token prematurely. The token is a last-resort fallback — most users will connect successfully via auto-pair within 3 attempts.

3. Execute: Browser automation
bash
actionbook --extension browser open "https://example.com"
# ... perform browser operations ...
4. Cleanup: Release debug connection, THEN stop bridge
bash
# Step 1: Release the debugging connection (MUST come first)
actionbook --extension browser close

# Step 2: Stop the bridge server
actionbook extension stop

# Step 3: Verify Chrome no longer shows "debugging" banner
actionbook extension status    # should show "not running"

WARNING: Skipping Step 1 and directly killing the bridge process will leave Chrome showing "Actionbook is debugging this browser". Always release the debug connection before stopping the bridge.

Extension mode: Troubleshooting
bash
# Bridge not running?
actionbook extension serve              # Start it

# Extension not responding?
actionbook extension ping               # Check connectivity

# Token expired? (idle > 30 min)
# Restart serve and re-pair in extension popup
actionbook extension serve              # Prints new token
Deep-Dive Documentation

For detailed patterns and best practices:

ReferenceDescription
references/command-reference.mdComplete command reference with all features
references/authentication.mdLogin flows, OAuth, 2FA handling, state reuse

© smallnest, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in internal/builtin_skills/actionbook of smallnest/goclaw.

  • SKILL.md
  • references/authentication.md
  • references/command-reference.md
  • references/extension-troubleshooting.md

Open the folder on GitHubat commit e05c79d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in smallnest/goclaw, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Actionbook Browser Action Manuals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Actionbook Browser Action Manuals compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Actionbook Browser Action Manuals this skillsmallnest/goclaw5981 repos~4.1kAutomated safety check: WarnMIT
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Cloudflare Browser Renderingcloudflare/moltworker9.9k—~742Automated safety check: PassApache-2.0
Chrome Devtoolseinverne/dotfiles1212 repos~1.6kAutomated safety check: NotesApache-2.0
Agent Browseroxylabs/agent-skills875—~3kAutomated safety check: PassMIT
Neo4ier/neo756—~1.8kAutomated safety check: PassNone

Similar skills

  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Cloudflare Browser Rendering

    cloudflare/moltworker

    Official

    Drives headless Chrome through Cloudflare Browser Rendering over a CDP WebSocket to take screenshots, navigate and scrape pages, and record multi-page videos.

    9.9k GitHub stars~742 tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check passed

  • Chrome Devtools

    einverne/dotfiles

    Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.

    121 GitHub starsUsed in 2 repos~1.6k tokens
    Data & AnalyticsAuto-check: notes

  • Agent Browser

    oxylabs/agent-skills

    Connects to Oxylabs remote agent browsers over the Chrome DevTools Protocol (CDP) with Playwright or Puppeteer.

    875 GitHub stars~3k tokensUpdated 8 days ago
    Productivity & AutomationAuto-check passed

  • Neo

    4ier/neo

    Browse websites, read web pages, interact with web apps, call website APIs, and automate web tasks.

    756 GitHub stars~1.8k tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check passed

  • Browser

    julianromli/opencode-template

    Minimal Chrome DevTools Protocol tools for browser automation and scraping.

    144 GitHub stars~475 tokensUpdated 8 mo ago
    Productivity & AutomationAuto-check passed

More from smallnest/goclaw

  • Crawl4AI Web Scraping

    smallnest/goclaw

    Scrapes sites, handles JavaScript-heavy pages and extracts structured data with Crawl4AI, through its crwl CLI or Python SDK, including schema-based extraction without an LLM.

    598 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Discord Actions for OpenClaw

    smallnest/goclaw

    Reference for OpenClaw's discord tool: sending messages, reactions, stickers, emoji uploads, polls, threads and moderation in Discord channels and DMs.

    598 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

  • Burner Phone Android Control

    smallnest/goclaw

    Controls an Android device over ADB in a loop of screenshot, vision analysis, tap and verification, so the agent acts on real on-screen coordinates.

    598 GitHub stars~436 tokensUpdated 6 mo ago
    Auto-check passed

  • Feishu Upload Image

    smallnest/goclaw

    Upload images to Feishu/Lark. An agent skill from smallnest/goclaw.

    598 GitHub stars~556 tokensUpdated 6 mo ago
    Auto-check passed

  • goclaw Skill Finder

    smallnest/goclaw

    Helps you find, install, update and remove skills in the goclaw agent framework, using the goclaw skills commands and outside skill sources.

    598 GitHub stars~1.2k tokensUpdated 6 mo ago
    Auto-check passed

Works with

Categories

Questions about Actionbook Browser Action Manuals

What does Actionbook Browser Action Manuals do?

Looks up action manuals with verified selectors for multi-step website tasks, then drives the browser with the actionbook CLI in a dedicated or an existing Chrome session. Actionbook has the agent search for an action manual before touching a site. A manual lists the page URL, the page structure and the UI elements with CSS or XPath selectors, so multi-step tasks such as sending a LinkedIn message are done against known selectors instead of guessed ones.

When should I use Actionbook Browser Action Manuals?

Actionbook Browser Action Manuals fits situations like: completing a multi-step task on a website, such as sending a message; building a browser-based agent or scraper that needs reliable selectors; writing end-to-end tests against an external website; operating your already-open Chrome with its existing logins.

How do I install Actionbook Browser Action Manuals in Claude Code?

Run `npx skills add smallnest/goclaw --skill actionbook -a claude-code`. Or copy the skill folder (internal/builtin_skills/actionbook in smallnest/goclaw) into .claude/skills/actionbook in your project. Claude Code loads it when a task matches its description.

How do I install Actionbook Browser Action Manuals in Codex?

Run `npx skills add smallnest/goclaw --skill actionbook -a codex`. Or copy the skill folder (internal/builtin_skills/actionbook in smallnest/goclaw) into .agents/skills/actionbook in your project. Codex loads it when a task matches its description.

Can I use Actionbook Browser Action Manuals in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add smallnest/goclaw --skill actionbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/actionbook, .gemini/skills/actionbook, .github/skills/actionbook and .opencode/skills/actionbook in your project.

What does Actionbook Browser Action Manuals need to run?

SKILL.md names no scripts, command-line tools or credentials: Actionbook Browser Action Manuals is instructions for the agent only. Our summary lists: The actionbook command line tool; Chrome with the Actionbook extension for extension mode.

Does Actionbook Browser Action Manuals access the network?

SKILL.md names 3 domains. In commands or code: arxiv.org, airbnb.com and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Actionbook Browser Action Manuals safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Actionbook Browser Action Manuals use?

Actionbook Browser Action Manuals is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Actionbook Browser Action Manuals use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Actionbook Browser Action Manuals?

Skills that share tags, products or a category with Actionbook Browser Action Manuals: Electron App Automation (vercel-labs/agent-browser, 44k stars), Cloudflare Browser Rendering (cloudflare/moltworker, 9.9k stars), Chrome Devtools (einverne/dotfiles, 121 stars) and Agent Browser (oxylabs/agent-skills, 875 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Actionbook Browser Action Manuals?

smallnest (a GitHub user) maintains it in smallnest/goclaw, which has 598 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on March 27, 2026.

Source: smallnest/goclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.