browser-context

Reads open browser tabs and synthesizes their content into context for a query.

2|Updated Sep 25, 2011
One-click install
npx skills add https://github.com/pokutuna/dotfiles --skill browser-context-pokutuna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-context
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/browser-context
Command: npx skills add https://github.com/pokutuna/dotfiles --skill browser-context-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When researching a topic, relevant information is often scattered across many open browser tabs—meeting notes, documentation, library references. Manually reading and consolidating all of them is slow and error-prone. This Skill reads your currently open Chrome tabs, selects the ones relevant to your question, and builds a consolidated context summary. ## Core Features & Use Cases - Tab Discovery and Filtering: Lists all open tabs via the chrome-tabs MCP server and selects only those relevant to your query based on title and URL. - Parallel Tab Reading: Dispatches subagents to read multiple tabs in parallel, extracting key points, entities, and relationships aligned with your question. - Deep-Dive Follow-Up: Opens referenced pages in new tabs or re-reads tabs when the initial pass doesn't fully answer the question. - Use Case: You have a dozen meeting minutes and API reference pages open. Ask the Skill to summarize the decision history across the minutes, and it returns an answer plus a tab-by-tab index of where each fact lives. ## Quick Start Ask the assistant to read your open browser tabs and summarize the decision history across the meeting notes related to your current project.

Frequently Asked Questions about browser-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize content across multiple open browser tabs?

List open tabs with the chrome-tabs MCP server, filter relevant ones by title and URL, then read each tab's content in parallel using subagents. The results are merged into a single answer with a per-tab index of key points.

What tool reads Chrome tab content for AI assistants?

The chrome-tabs MCP server provides list_tabs, read_tab_content, and open_in_new_tab tools. These let an assistant enumerate open tabs, read page content by tab ID, and open new pages for deeper research.

Does this work with tabs whose titles don't match their content?

Yes. Tab titles can be stale or misleading, so selection also considers the URL, and ambiguous tabs are partially read to verify relevance before committing to a full read.

What happens if the open tabs don't answer my question?

The Skill re-reads relevant tabs for more detail or opens referenced pages in new tabs to dig deeper. If the query itself is ambiguous or empty, it asks the user to clarify what to investigate.

Can it handle a large number of open tabs?

Yes. It assumes many irrelevant tabs are open, filters by title and URL first, and reads selected tabs in parallel batches of a few subagents at a time to keep the workload manageable.