メニュー
Use Vercel Labs agent-browser for web tasks, screenshots, page inspection, OAuth/device flows, and UI verification when the active runtime exposes the CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use Armorer-managed Linear tools for issue lookup, PM coordination, status summaries, and approval-gated task updates.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
Act as the Armorer agent for end-to-end app setup and operations. Use Armorer commands first and verify before reporting success.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
| name | agent-browser |
| description | Use Vercel Labs agent-browser for web tasks, screenshots, page inspection, OAuth/device flows, and UI verification when the active runtime exposes the CLI. |
| runtime | agent-browser |
| requires_binary | agent-browser |
| capabilities | ["browser.open","browser.snapshot","browser.interact","browser.auth","browser.state"] |
Use the Vercel Labs agent-browser CLI when a task requires observing or operating a web page, including local Armorer UI testing, app setup pages, OAuth or device-auth flows, screenshots, form validation, and public web inspection.
Before running browser commands, load the canonical workflow guide from the installed CLI:
agent-browser skills get core
Do not invent browser commands. If agent-browser is unavailable, report that the runtime capability is unavailable.
agent-browser open, snapshot, find, click, fill, get, wait, and batch --json when visual state, page behavior, or a web login/setup flow matters.get: use agent-browser get text @e1, agent-browser get html @e1, agent-browser get attr @e1 href, or agent-browser get value @e1. Do not call agent-browser text ... or agent-browser html ...; those are not valid top-level commands.When this skill is enabled for an installed agent, the agent should use the Armorer-provided agent-browser runtime, session name, auth profile, action policy, and environment. Raw credentials stay in Armorer Vault; the agent may use only credential readiness/profile names surfaced by Armorer.
Installed agents must call Armorer browser tools such as armorer_agent_browser_run, armorer_agent_browser_links, and armorer_agent_browser_form_submit; they must not run raw terminal agent-browser commands, because that bypasses Armorer's profile lease, CloakBrowser runtime selection, policy checks, and observability.