convez.ai
MCP Server
jin7933827109

chrome-tabs-skill

jin7933827109/chrome-tabs-skill

Ver no GitHub
InicialPluginScore · de 0 a 100

Claude Code skills for managing Chrome tabs via the mcp-chrome MCP server

Instalação

$npx convez-ai jin7933827109/chrome-tabs-skill

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

Chrome Tabs — Claude Code skills for managing your browser tabs

License: MIT

English | 简体中文

A set of Claude Code Agent Skills that let Claude see, search, classify, group, reorder, and review the tabs open in your real Chrome — by talking to it in plain language ("list my tabs", "把相关 标签编成组", "梳理今天的标签 / 工作复盘").

They run on top of the mcp-chrome MCP server, which bridges Claude to a live Chrome via a browser extension.

Before — a messy strip:

before: scattered tabs

After one prompt ("sort my tabs and group them") — clustered, ordered, and wrapped into named, colored tab groups:

after: sorted into colored groups

Local only. These skills drive your own Chrome on your own machine via 127.0.0.1. They work in a local Claude Code session — not on web claude.ai.

How it works

  Claude Code  ──MCP──▶  chrome-mcp-server (mcp-chrome)  ──native msg──▶  Chrome extension  ──▶  your tabs
                              listens on 127.0.0.1

The MCP server exposes tools to list / switch / close / open / read / screenshot / bookmark tabs. It has no tool to reorder or group tabs — so this skillset adds a small privileged engine that runs chrome.tabs.move / chrome.tabs.group as JavaScript inside the extension's own page (where the chrome.tabs API is in scope). See skills/chrome-tabs/engine.md.

The engine is battle-tested against the API's sharp edges — e.g. chrome.tabs.group silently moving tabs into the wrong window unless you pin createProperties.windowId (we hit it, so you don't have to).

The skills

A hub skill handles the simple stuff and routes the heavier jobs to four focused sub-skills:

SkillWhat it does
chrome-tabs (hub)List / switch / close / open / read / screenshot tabs, close duplicates, bookmark-and-close, and route to the sub-skills below.
chrome-tabs-classifyBucket open tabs by project / topic / page type, count them, flag duplicates. The shared first step for the others.
chrome-tabs-groupCluster related tabs into native Chrome tab groups, with names and colors (chrome.tabs.group + chrome.tabGroups.update).
chrome-tabs-reorderSort the tab strip so related tabs sit together (chrome.tabs.move).
chrome-tabs-reviewDaily tab review / work retrospective — what you touched today, what's mid-task, what's tab debt.

Optional: companion-skill bridge

Tabs are pointers. If your session also carries domain-native skills — a cloud-doc reader (e.g. the Feishu/Lark suite), a task manager, a calendar connector — the skills hand off instead of scraping: deep-read the docs behind your tabs, turn the daily review into a report or tomorrow's tasks, set a morning reminder whose description carries a thread's links. Detection rules and handoff contracts: skills/chrome-tabs/integrations.md. Everything still works with no companions present.

Quickstart

First set up the MCP server (Node ≥ 20, Chrome, the mcp-chrome extension) and connect Claude to it — see docs/SETUP.md. Then install the skills, either way:

Option A — as a plugin (one command, namespaced as chrome-tabs:*):

/plugin marketplace add jin7933827109/chrome-tabs-skill
/plugin install chrome-tabs@chrome-tabs-skill

Option B — copy into your personal skills dir (bare skill names):

git clone https://github.com/jin7933827109/chrome-tabs-skill.git
cd chrome-tabs-skill
bash scripts/install-skills.sh        # copies skills/* into ~/.claude/skills/

Restart Claude Code so it loads them, then just talk to Claude — see docs/USAGE.md for example prompts.

Updating

  • Plugin install: /plugin marketplace update chrome-tabs-skill, then reinstall/update the plugin.
  • Script install: git pull && bash scripts/install-skills.sh, restart Claude Code.

Requirements & limits

  • Requirements: local Claude Code, Chrome/Chromium, Node ≥ 20, the mcp-chrome bridge + extension (connected).
  • Single MCP client at a time — and the green popup ≠ your session is alive. "Service running" only means the native server process is up; after hours of idle, the first call failing is normal — it heals on a plain retry. If it keeps failing, reconnect the extension (Disconnect → Connect). SETUP has the safe /ping probe and a curl to confirm the stuck-slot case.
  • Group naming/coloring is one opt-in away. By default the extension grants tabs but not tabGroups, so new groups start untitled. Add "tabGroups" to the extension's manifest.json and reload, and Claude sets each group's title and color from code (that's how the screenshot above was made); without it, Claude hands you the name to apply with a right-click → Rename group. See the engine doc.
  • Tool names drift across mcp-chrome versions (older builds shipped a search_tabs_content semantic search; current ones don't). The skills trust the live tool list and fall back gracefully.
  • "Today" is inferred (from each tab's last-active time) — see the review skill for the honest caveats.

Credits & license

Built on top of hangwin/mcp-chrome (the MCP server + extension are theirs). These skills and docs are released under the MIT License.

Ver o original no GitHub

Bom para

Relacionados