Chrome Gemini Skills Library: What Google Documents, and How to Decide What to Pin

Chrome's Gemini Skills library at chrome://skills/browse shipped with Gemini in Chrome on April 14, 2026. This page covers what Google actually documents about the pre-built library, what it has never published, and a framework for deciding which Skills earn a permanent slot in your / picker.

That framing is deliberate. A pre-built Skill library is a moving target: Google adds to it without announcement, what you see depends on your account and region, and the counts and category lists in circulation trace to no Google source. A page that prints a fixed inventory is out of date the week after it publishes.

For setup and the editing flow, see our Chrome Gemini Skills complete guide. For Chrome Skills' place in Google's broader AI surfaces, see the Gemini stack overview of tool definitions, plugin patterns, and Chrome Skills.

Key Takeaways

• Google publishes no Skill count and no category list. Chrome's help page says only that "several skills" are built in. The chrome://skills/browse page on your own machine is the only accurate inventory.
• Skills are not read-only. Google's launch post says a Skills prompt "will ask for confirmation before taking certain actions, such as adding an event to your calendar or sending an email."
• Multi-tab is documented, and it is the reason to care. A Skill "will run on the page you're viewing, along with any other tabs you select."
• Every pre-built Skill is editable, and that is the documented intent: "if you want to customize it to better fit your needs, you can edit the Skill and update the prompt."
• Managed and Enterprise accounts are gated. Skills are unavailable on them unless an administrator turns the feature on, which decides whether a team rollout is even possible.
• Pin three to five Skills, not twenty. The value is depth of reuse, and reuse is the one thing a bigger library does not buy you.

What Google Actually Documents

Everything in this table is quoted or paraphrased from a Google-owned page, re-checked on August 13, 2026. Sources are listed at the end.

Two of Google's own example Skills, from the launch post, are a fair sample of the library's flavour: "Want to break down the ingredients of a product you're viewing online? Or select the perfect gift from multiple options by cross-referencing your budget with the recipient's interests? We wrote Skills that do these things and more."

What Google Has Never Published, and Why the Numbers Disagree

Two claims travel with this feature and neither survives a check against a Google source.

A count. No Google page states how many pre-built Skills ship. Not the launch post, not the Chrome help page, not the Chrome Enterprise help page. Figures like "50+" appear in secondary coverage and in aggregator posts, and none of them cite Google for the number.

A closed category list. The lists in circulation do not agree with each other, which is the tell:

Both of the two most detailed accounts end with an open set ("and other categories", "and more"), and they do not overlap cleanly: recipes and budgeting appear in one and not the other. Any page presenting an exhaustive five-category taxonomy with a Skill count per category is describing one browser on one day, not a published structure.

The practical consequence: read your own library rather than a list of it. Open chrome://skills/browse, use the search box, and treat any external inventory as an out-of-date snapshot.

Skills Can Act, Which Changes the Evaluation

The most common thing written about Chrome Skills, including on an earlier version of this page, is that Skills only read the page and cannot do anything. That is wrong, and it is wrong in the direction that matters for safety.

Google's launch post says a Skills prompt "will ask for confirmation before taking certain actions, such as adding an event to your calendar or sending an email." So the model to hold is not "this feature can only summarize", it is "this feature can act, and a confirmation prompt is what stands between the model's plan and the action". Google also says Skills "are built on Chrome's foundation of security and privacy" and use "the same safeguards we apply to prompts in Gemini in Chrome."

If you are evaluating Skills for a team, that confirmation step is the control worth understanding, and the managed-account gate above is the switch that decides whether the question arises at all.

Requirements, as Currently Documented

Chrome's help page lists these to use Gemini in Chrome, and they gate Skills with it:

• Sign in with a personal Google Account
• Use a Chromebook Plus, Mac, or Windows computer
• Use the latest version of Chrome
• Chrome language set to English (United States)
• Be 13 or older, or the applicable age in your country
• Be in a supported region

Note the drift worth catching: the April launch post said the rollout covered "Mac, Windows and ChromeOS", while the current help page specifies a Chromebook Plus. If you are on an older Chromebook, check the help page rather than the launch coverage. Skills remains desktop-only; no Android or iOS support has been announced as of August 13, 2026.

A Framework for Deciding What to Pin

Since the library's contents change and cannot be usefully enumerated here, the durable part is how you decide. Four questions to run any Skill through:

1. Will I use this prompt more than three times this month? If no, do not pin it. Type the prompt when you need it.
2. Does the default prompt match my conventions? If no, edit it. Google's own framing is that editing is the intended path, not a workaround.
3. Does it benefit from multiple tabs? Skills that aggregate across selected tabs use the one primitive that has no clean equivalent elsewhere. Single-tab Skills are competing with typing.
4. What is the failure mode, and would I notice? Skills with a structured output format (table, list) fail visibly. Skills with prose output can hide a bad run.

A Skill that earns "yes" on the first two and produces table or list output on the fourth is worth pinning. Most pre-built Skills pass the first question and fail the second, which is why the editing flow is the part of this feature to actually learn.

Pin three to five, not twenty. The library's size is not the constraint; your ability to remember what you saved is.

Prompt Patterns Worth Adapting

These are example prompts written for this page to illustrate the shape a well-formed Skill takes: an anchor to the current page or tabs, an explicit output format, and a rule for missing values. They are starting points to edit, not measured recommendations.

Summarize for a busy reader

Summarize this page in 5 bullets, no bullet longer than 15 words, in
second-person voice. End with a one-sentence verdict on whether the
full read is worth it.

Compare across selected tabs

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. Add a final row summarizing the consensus across tabs.

Extract structured data

Find every [entity type] on this page and return a markdown table with
one row each. Where you have to infer a value, mark it (inferred);
where it is absent, write (none).

Draft a message about this page

Draft a Slack message I could post to my team about this page. One-line
summary, the most useful detail, and the link. Under 80 words, casual
voice, no preamble.

The pattern to copy across all four: anchor the scope ("this page", "each selected tab"), name the output format, and say what to do when data is missing. Prompts written that way produce consistent output on every run, which is the entire point of saving one as a Skill rather than retyping it.

Where the Library Goes Next

Three things are undocumented rather than ruled out, and each is worth re-checking rather than assuming:

• Sharing. No team-share or import feature is documented, and the managed-account gate suggests Google is treating organizational deployment as an admin question first.
• Languages and platforms. English (US) and desktop are the documented boundaries. Google has not published a timeline for widening either.
• Library growth. Google adds Skills without announcement, so the only reliable way to know what is available is to re-browse chrome://skills/browse every few weeks.

Sources

Every claim above was re-checked on August 13, 2026 against these pages:

• Google, "Turn your best AI prompts into one-click tools in Chrome", April 14, 2026: https://blog.google/products-and-platforms/products/chrome/skills-in-chrome/
• Google Chrome Help, "Customize your Gemini in Chrome experience": https://support.google.com/chrome/answer/16988996
• Chrome Enterprise and Education Help, "Prompting": https://support.google.com/chrome/a/answer/17031594
• 9to5Google, April 14, 2026, cited only for its description of the library's categories: https://9to5google.com/2026/04/14/gemini-in-chrome-skills/
• TechCrunch, April 14, 2026, cited only for its description of the library's categories and the English (US) requirement: https://techcrunch.com/2026/04/14/google-adds-ai-skills-to-chrome-to-help-you-save-favorite-workflows/

chrome://skills/browse and chrome://skills/yourSkills are browser-internal pages and cannot be fetched or archived, so the library's contents are not verifiable from outside your own Chrome profile. That is why this page describes what Google documents and how to evaluate what you find, rather than printing an inventory.