Agent skill · AI & Agents

browser-intent

Execute a natural-language browser intent via page-agent (browser_act) when the target is easier to describe than to select — degrades gracefully when page-agent or an OpenAI-compatible LLM provider isn't configured

rUv71,307★ · +1,002/wk · 3 repos on radarProfile →
claude-codecodexcan modify filesMIT
Install
npx skills add ruvnet/ruflo --skill browser-intent --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: mcp__plugin_ruflo-core_ruflo__browser_actmcp__plugin_ruflo-core_ruflo__browser_openmcp__plugin_ruflo-core_ruflo__browser_snapshotmcp__plugin_ruflo-core_ruflo__browser_closemcp__plugin_ruflo-core_ruflo__aidefence_has_piimcp__plugin_ruflo-core_ruflo__aidefence_is_safeBashRead
Path: plugins/ruflo-browser/skills/browser-intent/SKILL.md
Open the folder on GitHub →
Where it comes from
Source: ruvnet/ruflo
Stars: 67,015 · +629 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Browser Intent Natural-language layer on top of the low-level `browser_*` selector tools. Where `browser-extract` and `browser-form-fill` compose selector-based primitives (`browser_click`, `browser_fill`, `browser_snapshot`), `browser-intent` lets the caller say what they want ("Click the login button", "Fill the search box with cats and submit") and delegates execution to [page-agent](https://github.com/alibaba/page-agent) — in-page injected JS that turns the DOM into text and drives an LLM tool-call loop against it. ## When to use - The target element is easier to describe in words than to select reliably (dynamic class names, ambiguous structure, A/B-tested markup). - A one-shot interaction where writing out a selector chain isn't worth it. - Prefer `browser_click` / `browser_fill` / `browser_snapshot` directly when you already know the exact selector or ref (`@e1`) — `browser_act` adds LLM latency + cost that a direct selector call doesn't. ## Steps 1. **Call `browser_act`** with a `task` string, and optionally `url` (navigates first) and `session` (default `"default"`): ``` mcp__plugin_ruflo-core_ruflo__browser_act({ task: "Click the login button", url: "https://example.com

What's inside
Steps it walks through
  1. When to use
  2. Steps
  3. Provider requirements (why this degrades so often)
  4. Caveats
More from ruflo
All skills →
About this skill
What does the browser-intent skill do?

Execute a natural-language browser intent via page-agent (browser_act) when the target is easier to describe than to select — degrades gracefully when page-agent or an OpenAI-compatible LLM provider isn't configured

How do I install it?

Run `npx skills add ruvnet/ruflo --skill browser-intent --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going