Chrome Skills: How to Save Gemini Prompts as One-Click Tools (Complete Guide)

Chrome Skills launched on April 14, 2026 as part of Gemini in Chrome. The pitch is simple: any prompt you find yourself typing more than twice should be saved as a Skill and triggered with a single click. The library ships with 50+ pre-built Skills across Learning, Research, Shopping, Writing, and Productivity, and you can save your own. This guide covers how to actually use it -- setup, the workflows worth saving first, the multi-tab feature most readers miss, and the limits to plan around.

For the curated review of the pre-built library specifically, see All Pre-Built Chrome Gemini Skills, Reviewed by Category. For where Chrome Skills fits in Google's broader AI stack, see our Gemini stack guide.

Key Takeaways

• Open the Skills picker by typing / in the Gemini side panel.
• Manage the library at chrome://skills/browse -- the URL alone is worth bookmarking.
• Free, desktop-only, English (US) for now. No mobile, no other languages at launch.
• Skills run on the active tab by default -- select multiple tabs to run one Skill across all of them.
• Save any chat as a Skill from the chat history; edit any pre-built Skill to fit your workflow.
• The killer pattern is multi-tab aggregation -- prices, summaries, classifications across many tabs in one click.

Setup: 30 Seconds to Your First Skill

You almost certainly already have everything you need. The check:

1. Chrome desktop (Windows, macOS, or ChromeOS), updated to the latest version.
2. Browser language set to English (US). System Settings does not matter -- this is Chrome's own language setting at chrome://settings/languages.
3. Signed into a Google account in Chrome.

Open the Gemini side panel: click the sparkle icon in the top-right corner of Chrome, or use the keyboard shortcut. The panel slides out from the right edge.

To run your first Skill: type / into the prompt box. The Skills picker appears with your most recent and most popular pre-built Skills. Click any one. The Skill runs against the page you currently have focused.

To browse the full library: navigate to chrome://skills/browse directly, or click the compass icon inside the Skills picker. The library lays out all pre-built Skills by category with a search box.

That is the entire setup. There is no install step, no extension, no configuration file.

Save Your Own Skill From Any Prompt

The most underused feature: any prompt you have already run can be saved as a Skill from the chat history.

The flow:

1. Run a normal Gemini prompt in the side panel: "Extract every email address from this page into a markdown list."
2. After Gemini answers, click the menu icon (three dots) on your prompt in the chat history.
3. Choose "Save as Skill".
4. Name it ("Extract Emails"), optionally edit the prompt to be more general ("Extract every email address from the active page into a markdown list, sorted alphabetically"), and save.

Your new Skill lands in the library and is available from the / picker forever after. The next time you need to extract emails from a page, you click once instead of typing the prompt.

The non-obvious move: edit the prompt before saving to make it more reusable. The prompt you ran was specific to one page; the Skill should work on any page. Add words like "the current page" or "the active tab" to anchor it. Add output format hints ("as a markdown list", "as a bulleted list", "as a CSV") so the Skill produces consistent output every time.

Edit Pre-Built Skills to Fit Your Style

Every pre-built Skill in the library is editable. This matters more than it sounds. The defaults are reasonable, but your team probably has conventions the defaults do not match. The fix is two clicks:

1. Open chrome://skills/browse.
2. Find the pre-built Skill you want to adapt.
3. Click "Customize" (or the pencil icon).
4. Edit the underlying prompt.
5. Save -- it replaces the original in your library.

Examples of useful edits:

• "Summarize this article" → add "in 5 bullet points, under 100 words total, in second-person voice".
• "Translate this page" → specify the target language and the dialect.
• "Extract action items" → specify your team's task format ("for each action item: assignee, deadline, priority").
• "Find similar products" → add "from these specific retailers: ...".

This pattern -- start with a pre-built Skill, edit the prompt to match your conventions -- is faster than writing a Skill from scratch and produces better-shaped prompts because the Library defaults handle the boilerplate.

The Multi-Tab Killer Feature

Most readers run Chrome Skills against one tab at a time. The feature that makes Skills genuinely powerful is multi-tab execution: select multiple tabs first, then trigger a Skill, and it runs against all of them with combined output.

How to do it:

1. Select multiple tabs in the tab strip with Ctrl-click (Windows/Linux) or Cmd-click (macOS). Selected tabs get a slightly highlighted background.
2. Open the Gemini side panel.
3. Type / and pick a Skill (or run a custom prompt).
4. Confirm "Run on N selected tabs" when prompted.
5. The Skill runs against each tab's content and returns a single combined response.

This is what changes Chrome Skills from a productivity feature to a workflow primitive. Real patterns this enables:

• Price comparison across 10 product tabs. Run "Extract product name, price, shipping cost, and availability into a markdown table." Get a single table in seconds. Beats a spreadsheet.
• Summarize 5 article tabs. "Summarize each tab in 3 bullets, then write a one-paragraph synthesis comparing them." Reading time goes from 30 minutes to 3.
• Classify 8 ticket pages. "For each tab, classify as bug / feature request / question / spam, and extract the customer name."
• Compare 4 candidate resume pages. "Compare these candidates on years of experience, technical depth, and apparent culture fit."

Most pre-built Skills support multi-tab implicitly. Custom Skills usually do too -- the Skill operates on "the page" or "the tabs", and Gemini infers the right scope.

The First Five Skills to Save (For Most Readers)

Pick from these five if you are not sure where to start. Each one earns its keep within a week of saving.

1. "Summarize for a busy reader." Custom prompt: "Summarize this page in 5 bullets, no bullet longer than 15 words, in second-person voice. End with a one-sentence verdict on whether it is worth reading the full piece."
2. "Extract structured data." Custom prompt: "Find every {entity type} on this page and return them as a markdown table with columns: {column 1}, {column 2}, {column 3}. Where you have to infer a value, mark it as (inferred)." Replace {...} per use.
3. "Compare across selected tabs." Custom prompt: "For each selected tab, identify the same key dimensions and return a single comparison table with one row per tab and one column per dimension." Pair with multi-tab selection.
4. "Draft a Slack message about this." Custom prompt: "Draft a Slack message I could post to my team about the contents of this page. Include a one-line summary, the most important point, and a relevant link if one is present. Keep it under 80 words and in casual voice."
5. "Cite as a source." Custom prompt: "Generate a citation for this page in {APA / Chicago / MLA / your format} format, with all the metadata you can extract from the page. If author or date is missing, mark it as (unknown)."

Run each one a few times against different pages, refine the prompt based on what does and does not work, and re-save. Within a week you have five buttons that match your real work.

Where Chrome Skills Wins (and Where It Does Not)

Skills wins clearly:

• Repeatable web-content workflows. Anything you do the same way against different web pages is a Skill candidate.
• Multi-tab aggregation. No other AI productivity tool ships a "run this prompt on all selected tabs" primitive at this level of polish.
• Low-friction prompt automation for non-power-users. A teammate who would never write a custom Gemini prompt will happily click a Skill button. The Library's pre-built Skills cover most everyday patterns.
• Browser-as-source-of-truth workflows. Skills lives where the content already is.

Skills does not win:

• Anything that needs to chain across apps. Skills runs against the page; it does not drive Mail, Slack, or Calendar. For cross-app workflows, see Perplexity Personal Computer or Codex computer use.
• Long agentic tasks. Skills produce one response per click. For multi-step workflows that need planning and tool use, Gemini CLI, Claude Code, or Codex are the right shape.
• Anything outside the browser. Skills lives in Chrome. If your work is in native apps, it is the wrong tool.
• Non-English (US) workflows. At launch Skills is gated to English (US). Other languages and locales are coming but the date is unspecified.

Limits and Privacy

A few practical things to know before you go heavy:

• Per-Skill prompt size. Skills work best with prompts under ~500 words. Longer prompts can be saved but the side-panel UI gets unwieldy.
• Output length. Gemini in Chrome's responses are typically capped lower than the standalone Gemini app. For very long outputs, run the prompt in the standalone Gemini app instead.
• Page contents go to Google's servers to generate the response, the same as any other Gemini interaction. The standard Gemini privacy terms apply: free-tier interactions can be used to improve Google's services unless you opt out at myactivity.google.com/product/gemini.
• Skills are tied to your Google account, not your device. They sync across Chromes you sign into.

Where Chrome Skills Goes Next

A few patterns worth watching over the rest of 2026:

• Multi-language rollout. English (US) is launch-only; Google has signaled broader language support but no timeline.
• Mobile. No mobile Skills support at launch, despite Gemini being available in Android Chrome. This is the obvious gap.
• Sharing Skills. Right now Skills are personal. A team share / team library would meaningfully raise adoption -- watch for it.
• Skill chaining. A "run this Skill, then this Skill on the output" feature would unlock significantly more sophisticated workflows. Not announced yet, but a natural next step.

For most readers in April 2026, the right move is: spend an hour exploring the pre-built library, save the three patterns you find yourself wanting most often, and run them daily for a week. The workflows that stick will reveal themselves quickly. Anything you find yourself typing repeatedly is a Skill waiting to be saved.