Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

agent-browser

Estrellas1

Forks0

Actualizado25 de abril de 2026 a las 11:20

Browser automation CLI for agents. Use for opening pages, clicking, filling forms, taking screenshots, reading DOM snapshots, testing local harnesses, or connecting to AFNM/Electron DevTools sessions.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

lemon07r

lemon07r/ElderGPT-Spirit-Ring

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

Explorador de archivos

11 archivos

SKILL.md

readonly

name	agent-browser
description	Browser automation CLI for agents. Use for opening pages, clicking, filling forms, taking screenshots, reading DOM snapshots, testing local harnesses, or connecting to AFNM/Electron DevTools sessions.

Agent Browser

Use agent-browser when browser or Electron UI evidence is needed. Prefer project-specific UI skills first (craftbuddy-ui-validation or spirit-ring-ui) so you know which harness or DevTools target to use.

Activate When

Testing a local browser harness
Capturing screenshots or accessibility/DOM snapshots
Clicking through UI flows or forms
Connecting to an Electron app via Chrome DevTools Protocol
Collecting visual evidence for regressions

Core Workflow

agent-browser open http://127.0.0.1:4173
agent-browser snapshot -i
agent-browser screenshot

For Electron/AFNM DevTools sessions, launch the app with --remote-debugging-port=9222, then connect or target that port according to the command reference.

Rules

Prefer stable selectors and accessible text over pixel coordinates.
Capture a snapshot before and after key interactions.
Keep screenshots local to the repo's ignored temp/output path unless the task asks for committed assets.
Do not make live Electron testing mandatory when a project harness or runtime oracle can answer the question.
Never put credentials, session tokens, or private screenshots in commits.

AFNM Notes

CraftBuddy UI work should usually use bun run ui:harness:build and bun run ui:harness:serve before agent-browser.
ElderGPT UI work should use its committed harness for overlay/session/settings checks.
Installed-client AFNM testing is opt-in and must follow the repo's live-testing skill/docs, including disable_steam cleanup.

References

references/commands.md — CLI command reference
references/session-management.md — sessions and target reuse
references/snapshot-refs.md — interpreting snapshots
references/video-recording.md — recordings when needed
references/authentication.md — auth/session patterns
references/proxy-support.md — proxy setup
references/profiling.md — performance profiling
templates/ — reusable command snippets

Más de este repositorio

mismo repositorio

spirit-ring-runtime

lemon07r/ElderGPT-Spirit-Ring

ElderGPT Spirit Ring runtime integration skill. Activate for game-state extraction, context normalization, ModAPI snapshots/subscriptions, proactive hooks, read-only boundaries, runtime oracle checks, or src/integration changes.

2026-04-271

spirit-ring-ai-client

lemon07r/ElderGPT-Spirit-Ring

ElderGPT Spirit Ring AI client skill. Activate for OpenAI-compatible or Anthropic endpoint handling, streaming, timeout/error behavior, model limits, context compaction, secrets handling, or src/ai changes.

2026-04-251

spirit-ring-ui

lemon07r/ElderGPT-Spirit-Ring

ElderGPT Spirit Ring UI skill. Activate for persistent overlay, chat panel, settings UI, injected Consult Spirit Ring button, harness validation, session management, pointer isolation, or src/ui changes.

2026-04-251

Agent Browser

Activate When

Testing a local browser harness

Capturing screenshots or accessibility/DOM snapshots

Clicking through UI flows or forms

Connecting to an Electron app via Chrome DevTools Protocol

Collecting visual evidence for regressions

Core Workflow

agent-browser open http://127.0.0.1:4173 agent-browser snapshot -i agent-browser screenshot

For Electron/AFNM DevTools sessions, launch the app with --remote-debugging-port=9222, then connect or target that port according to the command reference.

Rules

Prefer stable selectors and accessible text over pixel coordinates.

Capture a snapshot before and after key interactions.

Keep screenshots local to the repo's ignored temp/output path unless the task asks for committed assets.

Do not make live Electron testing mandatory when a project harness or runtime oracle can answer the question.

Never put credentials, session tokens, or private screenshots in commits.

AFNM Notes

CraftBuddy UI work should usually use bun run ui:harness:build and bun run ui:harness:serve before agent-browser.

ElderGPT UI work should use its committed harness for overlay/session/settings checks.

Installed-client AFNM testing is opt-in and must follow the repo's live-testing skill/docs, including disable_steam cleanup.

References

references/commands.md — CLI command reference

references/session-management.md — sessions and target reuse

references/snapshot-refs.md — interpreting snapshots

references/video-recording.md — recordings when needed

references/authentication.md — auth/session patterns

references/proxy-support.md — proxy setup

references/profiling.md — performance profiling

templates/ — reusable command snippets