New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Chrome Control

by Porabuild in Porabuild/Poracode

Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

Apache-2.0Auto-check passed

Install Chrome Control

skills CLI
$ npx skills add Porabuild/Poracode --skill chrome-control -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Porabuild/Poracode chrome-control --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/chrome-tools/skills/chrome-control .claude/skills/chrome-control && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chrome-control
GitHub stars
114
Token cost
~691 tokens
SKILL.md length
347 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

  • Works in 6 steps: Call chrome.status first. If the… → Call chrome.enable once before browser… → Inspect with chrome.snapshot or… → …
  • Existing authentication
  • SKILL.md covers Workflow, Boundaries and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Chrome Control is an agent skill from Porabuild/Poracode. Use the user's real Chrome tabs and signed-in sessions for visible browser workflows. Use when existing authentication, open tabs, cookies, or extensions matter; prefer a purpose-built connector for semantic service operations unless the user explicitly asks for Chrome.

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • Existing authentication
  • Extensions matter
  • Prefer a purpose-built connector for semantic service operations unless the user explicitly asks for Chrome

Example prompts

  • “/chrome-control”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Call chrome.status first. If the extension is disconnected, ask the user to connect it rather than switching surfaces silently.
  2. Call chrome.enable once before browser actions. Use the background Poracode workspace by default; call chrome.attach only when the user…
  3. Inspect with chrome.snapshot or chrome.find before clicking or typing. Prefer returned element refs and use fill for replacement versus…
  4. Page commands share the in-app browser names and arguments: snapshot, find, fill, type, click, press, wait, perform. Batch known actions…
  5. Include a condition wait at the end of a batch for asynchronous changes and verify the returned observation. After navigation, wait for…
  6. Call chrome.disable before asking the user for input, waiting on an external event, or finishing.

What it can do on your machine

Read from SKILL.md and the folder at commit bffd89d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chrome Control loads about 691 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 347 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~691

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Porabuild/Poracode at commit bffd89d, republished under its Apache-2.0 licence (© Porabuild). 347 words, ~691 tokens.

Download SKILL.mdSave it as .claude/skills/chrome-control/SKILL.md (or your agent's skills folder).
name
chrome-control
description
Use the user's real Chrome tabs and signed-in sessions for visible browser workflows. Use when existing authentication, open tabs, cookies, or extensions matter; prefer a purpose-built connector for semantic service operations unless the user explicitly asks for Chrome.

Chrome Control

Use Poracode's chrome MCP when a task depends on the user's current Chrome tabs, authenticated sessions, or installed extensions. If a purpose-built connector can complete a semantic service operation, prefer it unless the user explicitly requested Chrome or visual interaction is part of the task.

Workflow

  1. Call chrome.status first. If the extension is disconnected, ask the user to connect it rather than switching surfaces silently.
  2. Call chrome.enable once before browser actions. Use the background Poracode workspace by default; call chrome.attach only when the user asked to operate an existing tab.
  3. Inspect with chrome.snapshot or chrome.find before clicking or typing. Prefer returned element refs and use fill for replacement versus type for appending.
  4. Page commands share the in-app browser names and arguments: snapshot, find, fill, type, click, press, wait, perform. Batch known actions with {steps:[{action:"fill",ref:"@e1",text:"Ada"},{action:"click",ref:"@e2"},{action:"wait",text:"Saved"}]}. perform stops on failure and returns one compact snapshot (observe:"none" omits it). Split at decisions, new targets, and navigation; never replay completed steps after partial failure. Keep every action scoped to the requested site and task. Do not explore other tabs or signed-in content for extra context.
  5. Include a condition wait at the end of a batch for asynchronous changes and verify the returned observation. After navigation, wait for and verify the resulting URL, text, control state, or screenshot.
  6. Call chrome.disable before asking the user for input, waiting on an external event, or finishing.

Boundaries

  • Treat tabs, cookies, storage, and signed-in content as sensitive user data. Do not read cookies unless the task requires it and Chrome data access is enabled.
  • Never attach to an unrelated existing tab merely because it is already authenticated.
  • A successful tool call is not proof that the website accepted the action; verify the visible result.
  • Confirm the exact target and payload before purchases, submissions, messages, deletions, account changes, or other irreversible actions unless already authorized.

Output

Report the target site or tab, what changed, and the final visible evidence. State whether the background workspace or an existing user tab was used, and identify any action left pending for confirmation.

© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/plugins/chrome-tools/skills/chrome-control of Porabuild/Poracode.

Open the folder on GitHubat commit bffd89d

Compare with similar skills

Chrome Control next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chrome Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chrome Control this skillPorabuild/Poracode114—~691Automated safety check: PassApache-2.0
Session Handoffsickn33/agentic-awesome-skills47k—~1.8kAutomated safety check: NotesMIT
Sessionanthropics/claude-for-legal9.6k3 repos~478Automated safety check: PassApache-2.0
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Session Handoffdavila7/claude-code-templates32k2 repos~1.6kAutomated safety check: PassMIT
Read Sessionasgeirtj/system_prompts_leaks69k—~2.4kAutomated safety check: PassCC0-1.0

Similar skills

  • Session Handoff

    sickn33/agentic-awesome-skills

    A skill your agent uses when context approaches capacity, before /clear or /compact, when switching tasks, or when ending a coding session: produces a structured handoff artifact for the next session.

    47k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Session

    anthropics/claude-for-legal

    Official

    Run a focused N-question study session on a subject — MBE, essay, or flashcards.

    9.6k GitHub starsUsed in 3 repos~478 tokens
    EducationAuto-check passed

  • Session History Search

    slopus/happy

    Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Session Handoff

    davila7/claude-code-templates

    Creates comprehensive handoff documents for seamless AI agent session transfers.

    32k GitHub starsUsed in 2 repos~1.6k tokens
    Agent WorkflowsAuto-check passed

  • Read Session

    asgeirtj/system_prompts_leaks

    Locate and read Muse Code's OWN session logs — the current session or a prior one.

    69k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Document Signing

    asgeirtj/system_prompts_leaks

    Review documents for signature or prepare a signing packet; verify fields and recipients while keeping sending and signing under explicit user authorization.

    69k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

More from Porabuild/Poracode

All 21 skills in this repo

  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    114 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    114 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    114 GitHub stars~745 tokensUpdated today
    Auto-check passed

  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    114 GitHub stars~718 tokensUpdated today
    Auto-check passed

  • Provider Chat Smoke

    Porabuild/Poracode

    Smoke test real Poracode provider chat threads and ACP sessions end to end.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Questions about Chrome Control

What does Chrome Control do?

Use the user's real Chrome tabs and signed-in sessions for visible browser workflows. Chrome Control is an agent skill from Porabuild/Poracode. Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

When should I use Chrome Control?

Chrome Control fits situations like: existing authentication; extensions matter; prefer a purpose-built connector for semantic service operations unless the user explicitly asks for Chrome.

How do I install Chrome Control in Claude Code?

Run `npx skills add Porabuild/Poracode --skill chrome-control -a claude-code`. Or copy the skill folder (resources/plugins/chrome-tools/skills/chrome-control in Porabuild/Poracode) into .claude/skills/chrome-control in your project. Claude Code loads it when a task matches its description.

How do I install Chrome Control in Codex?

Run `npx skills add Porabuild/Poracode --skill chrome-control -a codex`. Or copy the skill folder (resources/plugins/chrome-tools/skills/chrome-control in Porabuild/Poracode) into .agents/skills/chrome-control in your project. Codex loads it when a task matches its description.

Can I use Chrome Control in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Porabuild/Poracode --skill chrome-control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-control, .gemini/skills/chrome-control, .github/skills/chrome-control and .opencode/skills/chrome-control in your project.

What does Chrome Control need to run?

SKILL.md names no scripts, command-line tools or credentials: Chrome Control is instructions for the agent only.

Does Chrome Control access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Chrome Control safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Chrome Control use?

Chrome Control is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chrome Control use?

About 691 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chrome Control?

Skills that share tags, products or a category with Chrome Control: Session Handoff (sickn33/agentic-awesome-skills, 47k stars), Session (anthropics/claude-for-legal, 9.6k stars), Session History Search (slopus/happy, 24k stars) and Session Handoff (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chrome Control?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.