- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add OyadotAI/oya-browser --skill browser-agent -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add OyadotAI/oya-browser --skill browser-agent -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add OyadotAI/oya-browser --skill browser-agent -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add OyadotAI/oya-browser --skill browser-agent -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/OyadotAI/oya-browser/tree/HEAD/.agents/skills/browser-agentDel publicador
You have access to a real Chrome browser through Oya Browser MCP tools. The browser has real cookies, logins, extensions, sites see a real user, not a bot. You control it through structured commands, not raw HTML or CSS selectors.
The browser gives you pages as structured markdown with numbered interactive elements. You act by referencing element numbers:
[#9 input:text placeholder="Search"] → type(9, "query")
[#13 button "Google Search"] → click(13)
[#4 link "Images" → /images] → click(4)
You never write CSS selectors, XPath, or pixel coordinates (unless using coordinate tools for precise clicks). You analyze the page, read the markdown, and act by element ID.
Every browser task follows this loop:
analyze_page to see the page as markdown with numbered elementsCRITICAL: Always call analyze_page after navigation or significant interactions. Element IDs change between analyses. Never assume an old ID is still valid.
analyze_page(): Returns full page as markdown with [#id type "label"] annotations. Always start here.screenshot(): Capture visible viewport as PNG. Use when you need to verify visual state or when markdown isn't enough.read_elements(selector?, limit?): Lighter than analyze_page, returns element metadata without full markdown.navigate(url): Go to a URL. Wait for page load automatically.scroll(direction, amount?): Scroll "up" or "down" by N pixels (default 500). Returns updated page analysis.wait(selector, timeout?): Wait for a CSS selector to appear (max 10s default).click(element_id): Click an element by its ID from analyze_page. Scrolls element into view automatically.type(element_id, text): Clear field and type text into an input/textarea/contenteditable.press_key(key): Press Enter, Escape, Tab, ArrowDown, ArrowUp, Backspace, or any key.click_coordinates(x, y): Click at exact pixel position. Use with screenshot when element IDs don't work.mouse_move(x, y): Hover without clicking. Triggers tooltips, dropdown menus, hover states.double_click(element_id?, x?, y?): Double-click by element ID or coordinates. For text selection, file opening.keyboard_type(text): Type into whatever is currently focused. No element targeting.drag(from_x, from_y, to_x, to_y): Drag between two points. For sliders, drag-and-drop, range selection.list_tabs(): Show all open tabs with IDs.open_tab(url?): Open new tab, optionally navigating to URL.switch_tab(tab_id): Switch to a tab by ID.close_tab(tab_id?): Close a tab (default: active tab).pool_status(): Show connected browsers in the pool.analyze_page OutputThe output has two parts:
1. Header: metadata about the page:
---
url: https://example.com
title: Example
viewport: 1280x720
scroll: 0% (0px / 3200px)
elements: 47 total, 23 visible
---
2. Body: full page as markdown with inline element annotations:
# Welcome to Example
[#1 link "Home" → /] [#2 link "About" → /about] [#3 link "Login" → /login]
## Search
[#9 input:text placeholder="Search..."]
[#10 button "Search"]
## Results
- [#11 link "First result" → /result/1]
- [#12 link "Second result" → /result/2]
3. Element Index: grouped by visibility:
### Visible
[#9] input: Search...
[#10] button: Search
### Off-screen (scroll to reveal)
[#35] link: Footer link
Forms: Find the input elements, type into each, then click submit:
analyze_page → find [#5 input:email], [#6 input:password], [#7 button "Sign in"]
type(5, "[email protected]")
type(6, "password123")
click(7)
Dropdowns/Selects: Click to open, then click the option:
click(dropdown_id)
analyze_page → find the option elements that appeared
click(option_id)
Infinite scroll: Scroll down, re-analyze to see new content:
scroll("down", 800)
→ returns updated analysis with new elements
Modals/Dialogs: When a modal is open, analyze_page automatically scopes to the modal content. The header will say modal: "dialog name".
Pagination: Look for "Next", "More", or page number links in the element index.
LinkedIn:
data-urn attributes; the analyzer detects thesearia-hidden on main content; the analyzer handles thisX (Twitter):
data-testidReddit:
<shreddit-post>); the analyzer traverses shadow DOMHackerNews:
[#N button "upvote"][#N link "reply to username"][#N link "189 comments" on "Post Title"]Amazon:
data-asin and data-cel-widgetSometimes elements aren't detected or clickable by ID. Fallback strategy:
click_coordinates(x, y) → click at the pixel position you see in the screenshotmouse_move(x, y) → hover first to reveal hidden elements (dropdowns, tooltips)keyboard_type(text) → type into whatever is focused without targetinganalyze_page again.click_coordinates with screenshot.navigate again, or wait for a specific selector.analyze_page will scope to the modal. Dismiss it with Escape or clicking X.Control a real browser via Oya Browser MCP tools. Use this skill when the user asks you to browse the web, interact with websites, fill forms, scrape data, or automate browser tasks. Provides the ment
---name: browser-agentdescription: Control a real browser via Oya Browser MCP tools. Use this skill when the user asks you to browse the web…---# .agents/skills/browser-agent/SKILL.mdResumen general
Control a real browser via Oya Browser MCP tools. Use this skill when the user asks you to browse the web, interact with websites, fill forms, scrape data, or automate browser tasks. Provides the mental model and strategies for effective browser automation through structured markdown and numbered element IDs.
Preguntas frecuentes
Descarga .agents/skills/browser-agent/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/OyadotAI/oya-browser.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.