chrome-tools

Links

• github.com/SDSLeon/lightcode
• https://poracode.com
• resources/plugins/chrome-tools/plugin.json (manifest)

Skills · 2

chrome-control

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.

signed-in-research

Gather information from pages that only load behind the user's own Chrome login, without touching anything else in their session.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

Category

Integrations & APIs. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

chrome · browser · automation

Related by publisher and keywords

• browser-toolsSDSLeon

  Browse, inspect, and test websites in Poracode's isolated in-app browser.

• computer-useSDSLeon

  Control desktop apps in the background and complete visual workflows.

• app-controlsSDSLeon

  Read and drive Poracode itself: threads, workspaces, terminal panes, git, pull requests, and schedules.

• subagent-delegationSDSLeon

  Delegate focused work to other installed agents and coordinate the results.

• terminalSDSLeon

  Read the Terminal panel attached to this worktree and report what it is printing.

• chrome-toolsPorabuild

  Work with the pages and signed-in sessions already open in Chrome.