Google announced Chrome Skills on April 14, and a team of eight could have 24 saved prompts by the end of the month without anyone reading two of them side by side. The button is fine. The pile of unreviewed instructions behind it is the problem, so give each saved prompt an owner before anyone else runs it.
Key points
- What does Chrome Skills actually do? It turns a prompt you liked into a button.
- What goes wrong when a team shares saved prompts? They drift. A prompt that works for one person on one afternoon becomes a habit within a month, and Google says saved Skills follow you to any signed-in Chrome desktop device, so one built at home turns up at the office.
- Who checks what the button does? Google builds in one check. It says a Skill asks for confirmation before certain actions , with sending an email and adding a calendar event as its examples.
What does Chrome Skills actually do?
It turns a prompt you liked into a button. You write a request in Gemini in Chrome, such as pulling the key terms from a supplier page, save it from your chat history, and run it later by typing a slash or pressing a plus button.
It works on the page in front of you and any other tabs you select. Google also ships a library of ready-made Skills you can add and edit.
That is all it is. There’s no new model, and no data access that Gemini in Chrome didn’t already have. The change is repetition. A paragraph of typing becomes one click, so people will run it more often, on more pages, with less thought. It’s on desktop only (Mac, Windows and ChromeOS, with the Chrome language set to English-US), so a team can end up split between people who have it and people who don’t.
What goes wrong when a team shares saved prompts?
They drift. A prompt that works for one person on one afternoon becomes a habit within a month, and Google says saved Skills follow you to any signed-in Chrome desktop device, so one built at home turns up at the office.
Here’s our illustration, not a measurement. One person’s invoice-summary Skill says to flag anything over $5,000, another’s says $10,000, and a third doesn’t flag at all. All three people get different answers about the same supplier page, and each assumes the tool did it. Nobody did anything wrong. It’s like eight copies of a price list that were each edited once.
The cost shows up later, usually at a handoff. A new hire is handed a colleague’s saved prompts, trusts the output because it comes from a button, and never sees the wording that produced it. Nobody can say why the $5,000 threshold was chosen, because the person who chose it is on leave. A written owner and a date on each prompt turn that mystery into a two-minute question.
Staff adopt features like this faster than their supervisors notice, which is the gap our piece on workplace AI adoption describes. Inconsistent prompts are one of the ways that gap shows up, and our test of Gmail’s free AI summaries makes the case for trying Google’s built-in features on low-stakes work first.
Who checks what the button does?
Google builds in one check. It says a Skill asks for confirmation before certain actions, with sending an email and adding a calendar event as its examples. It also says Skills use the same safeguards as other Gemini in Chrome prompts, including automated red-teaming. That’s Google’s description of its own feature.
Administrators can switch Gemini in Chrome on or off through Google’s admin settings, though that page doesn’t mention Skills. A later dated note settles it: Google’s Workspace Updates blog said on May 6, 2026 that there is no admin control for Skills and that the feature is on by default for users with Gemini in Chrome.
Read that last point twice. If there’s no admin control and the feature is on by default, the only lever you have is a written rule your staff know about. That’s why this is an operations job and not an IT setting.
Notice what the confirmation covers. Actions. It doesn’t cover a wrong summary, a missed clause or a number pulled from the wrong tab, because reading a page and getting it wrong isn’t an action the browser needs to confirm. The person has to catch that, and a one-click workflow trains people not to look.
What should a Skill pass before it’s shared?
Three checks, each under ten minutes. Every Skill needs a named owner who fixes it when something changes, a test on one page where the right answer is already known, and a written list of outputs a person must read before anything is sent, filed or paid. Skip any of the three and the Skill isn’t ready to share.
- A named owner. One person is responsible for the wording and fixes it when a supplier changes their page layout.
- A test page. The owner runs it on one page where the right answer is already known, and writes the expected result next to the prompt.
- A human-click list. The owner writes down which outputs a person must read before anything is sent, filed or paid. Anything touching money, a customer or a contract goes on it.
A test page is simple. Say the Skill pulls payment terms from supplier pages. The owner picks one supplier page where the terms are known to be net 30, runs the Skill, and writes “expected: net 30, flags nothing” beside the prompt. When Google changes the model behind the feature or the supplier redesigns their site, the owner reruns the page and sees at once whether the answer moved. Without that, you find out when an invoice is paid late.
Run an audit first if staff are already saving prompts. Ask everyone to paste the prompts they reuse into one shared document, and treat it as an inventory, not an inquiry. You’ll find duplicates, and you’ll find two or three that touch money. Those become the first owned Skills. The rest can stay personal.
Keep the approved Skills in one shared document with the owner’s name and the date of the last test. A short list beats a library. If a Skill hasn’t been used in a quarter, delete it.
The permissions card in our OpenClaw strategy piece works for Skills too, since a browser assistant that acts on your behalf needs the same limits as any agent. If a Skill drives desktop work, our test-first look at GPT-5.4 computer use shows how to measure failures before you rely on it. Check which Gemini plan your Workspace includes before promising central control, because the admin options differ by plan.
That’s a lot of process for a convenience feature if all your team does is tidy meeting notes, and in that case skip it. A saved prompt is just a note until it touches a supplier, a customer or a payment. Then it’s a procedure with a fast finger on it, and procedures nobody owns tend to fail on a busy Friday. We’d loosen the rules if Google ships controls that let administrators see, lock and audit Skills centrally. Google’s launch post also doesn’t say what happens to saved prompts when an employee leaves, which is worth asking before the first departure.
On Monday, pick the two prompts your staff already reuse, name one person for each, and write down which outputs a human has to read first.
Saved prompts share the browser with Gemini, which raises a tab-sharing policy for Gemini in Chrome.
Frequently asked questions
What is Chrome Skills?
It’s a feature in Gemini in Chrome that lets you save an AI prompt and rerun it with one click, plus a library of ready-made prompts. Google announced it on April 14, 2026.
Does Chrome Skills work on phones?
Google’s announcement lists desktop only, rolling out on Mac, Windows and ChromeOS, with the Chrome language set to English-US.
Do I need rules for saved AI prompts?
For anything touching money, customers or contracts, yes. Give each Skill an owner, a test page and a list of outputs a person must read first.
Archive entry dated April 15, 2026, written and fact-checked on October 8, 2026. Sources are linked on the claims they support.
