Browser Automation logo

Browser Automation

OrganizationPopular
RightNow-AI
browser-automation

Playwright-based browser automation patterns for autonomous web interaction

Overview

PublisherRightNow-AI
Repositoryopenfang
Skill namebrowser-automation
Stars
18.2K
Forks
2.3K
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by RightNow-AI on GitHub. Read the source before you install it.

Installation

Install the Browser Automation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RightNow-AI/openfang.git /tmp/openfang
mkdir -p .claude/skills
cp -r /tmp/openfang/crates/openfang-hands/bundled/browser .claude/skills/browser-automation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser Automation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser Automation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser Automation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Browser Automation Skill

Playwright CSS Selector Reference

Basic Selectors

SelectorDescriptionExample
#idBy ID#checkout-btn
.classBy class.add-to-cart
tagBy elementbutton, input
[attr=val]By attribute[data-testid="submit"]
tag.classCombinedbutton.primary

Form Selectors

SelectorUse Case
input[type="email"]Email fields
input[type="password"]Password fields
input[type="search"]Search boxes
input[name="q"]Google/search query
textareaMulti-line text areas
select[name="country"]Dropdown menus
input[type="checkbox"]Checkboxes
input[type="radio"]Radio buttons
button[type="submit"]Submit buttons

Navigation Selectors

SelectorUse Case
a[href*="cart"]Cart links
a[href*="checkout"]Checkout links
a[href*="login"]Login links
nav aNavigation menu links
.breadcrumb aBreadcrumb links
[role="navigation"] aARIA nav links

E-commerce Selectors

SelectorUse Case
.product-price, [data-price]Product prices
.add-to-cart, #add-to-cartAdd to cart buttons
.cart-total, .order-totalCart total
.quantity, input[name="quantity"]Quantity selectors
.checkout-btn, #checkoutCheckout buttons

Common Workflows

Product Search & Purchase

1. browser_navigate → store homepage
2. browser_type → search box with product name
3. browser_click → search button or press Enter
4. browser_read_page → scan results
5. browser_click → desired product
6. browser_read_page → verify product details & price
7. browser_click → "Add to Cart"
8. browser_navigate → cart page
9. browser_read_page → verify cart contents & total
10. STOP → Report to user, wait for approval
11. browser_click → "Proceed to Checkout" (only after approval)

Account Login

1. browser_navigate → login page
2. browser_type → email/username field
3. browser_type → password field
4. browser_click → login/submit button
5. browser_read_page → verify successful login

Form Submission

1. browser_navigate → form page
2. browser_read_page → understand form structure
3. browser_type → fill each field sequentially
4. browser_click → checkboxes/radio buttons as needed
5. browser_screenshot → visual verification before submit
6. browser_click → submit button
7. browser_read_page → verify confirmation

Price Comparison

1. For each store:
   a. browser_navigate → store URL
   b. browser_type → search query
   c. browser_read_page → extract prices
   d. memory_store → save price data
2. memory_recall → compare all prices
3. Report findings to user

Error Recovery Strategies

ErrorRecovery
Element not foundTry alternative selector, use visible text, scroll page
Page timeoutRetry navigation, check URL
Login requiredInform user, ask for credentials
CAPTCHACannot solve — inform user
Pop-up/modalClick dismiss/close button first
Cookie consentClick "Accept" or dismiss banner
Rate limitedWait 30s, retry
Wrong pageUse browser_read_page to verify, navigate back

Security Checklist

  • Verify domain before entering credentials
  • Never store passwords in memory_store
  • Check for HTTPS before submitting sensitive data
  • Report suspicious redirects to user
  • Never auto-approve financial transactions
  • Warn about phishing indicators (misspelled domains, unusual URLs)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Browser Automation AI skill do?

Playwright-based browser automation patterns for autonomous web interaction

Why use Browser Automation on TypingMind?

Because you install it once and use it with any model. Browser Automation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Automation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RightNow-AI/openfang/tree/main/crates/openfang-hands/bundled/browser. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Browser Automation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Automation?

As many as you like. As long as a model supports skills, you can use Browser Automation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Automation AI skill free?

Yes. It is published on GitHub by RightNow-AI under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇