Skill Detail

Run block-based browser automation workflows with Automa

Use Automa when an operator needs repeatable browser workflows for form filling, scraping, screenshots, or scheduled web tasks through a browser-extension block builder.

Browser AutomationMulti-Framework
Browser Automation Multi-Framework Security Reviewed
⭐ 21.4k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill run-block-based-browser-automation-workflows-with-automa Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Automa browser extension for Chrome or Firefox
Install & setup
Install Automa from the Chrome Web Store or Firefox Add-ons, or build locally with pnpm install and pnpm build from the GitHub repository.
Author
AutomaApp
Publisher
Open Source Project
Last updated
Jun 15, 2026
Quick brief

Automa is an open-source browser extension for building browser automations by connecting workflow blocks. It is useful when an agent or operator needs a repeatable, inspectable browser task such as filling forms, scraping page data, taking screenshots, or scheduling recurring web checks without writing a custom Playwright or Selenium script.\n\nUse this skill when the workflow is bounded to browser-extension automation: define the steps as blocks, connect page actions and data extraction, test the run in Chrome or Firefox, and schedule or export the workflow when it should run repeatedly. The scope boundary is the reusable browser workflow itself, not a generic browser automation platform or a broad product card.

How it works

What this skill actually does

Inputs and prerequisites: Automa browser extension for Chrome or Firefox.

Setup notes: Install Automa from the Chrome Web Store or Firefox Add-ons, or build locally with pnpm install and pnpm build from the GitHub repository.

Source and verification boundary: use https://docs.extension.automa.site/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.