Skills in Chrome is the kind of feature that looks small on a release note and quietly rewrites how a team spends its afternoons. That is exactly why Anuj wanted to talk about it. “Most AI productivity loss isn’t dramatic,” he says. “It’s not a failed project or a bad model. It’s the same person typing the same prompt for the fourth time that week and not even noticing they’re doing it.” Skills in Chrome attacks that invisible tax directly — you save a prompt once, and run it on any page, or across several tabs, with a single click.
The problem nobody logs as a problem
Anuj’s starting point is blunt: the friction Skills in Chrome removes is friction most professionals have stopped counting.
“Think about what actually happens,” he explains. “You write a genuinely good prompt — something that pulls pricing, features and integrations off any product page in a clean structure. It works. You’re pleased with yourself. Then tomorrow it’s a new tab, a new page, and you type the whole thing again from memory. Or worse, you go digging through three weeks of chat history looking for the version that worked.”
For a product manager comparing five vendors, that is five identical prompts across five tabs. For a procurement lead, a legal reviewer, a competitive analyst — anyone whose job is running the same analysis against different inputs — Anuj estimates it adds up to hours every single week. “Nobody puts ‘retyping prompts’ on a timesheet,” he says. “So nobody fixes it. That’s what makes it expensive.”
Anuj’s real argument: this is workflow memory, not a shortcut
Here is where Anuj pushes past the obvious. He argues that treating Skills in Chrome as a copy-paste convenience badly undersells it.
“A saved prompt isn’t a shortcut. It’s a documented process,” he says. “The moment you name something ‘Vendor Snapshot’ and save it, you’ve turned one person’s good instinct into an asset the whole team can run. That’s the shift. You’ve moved from individual cleverness to repeatable output.”
That reframing matters for anyone leading a team. Anuj points out that most organisations rolling out AI have an adoption gap, not an access gap — everyone has the tool, a handful of people use it well, and that skill never travels. “Skills in Chrome is one of the first browser-native features that lets the good prompt travel,” he says. “Your sharpest analyst builds the Skill. Everyone else runs it. That’s how AI literacy actually spreads inside a company — through shared artefacts, not through another training deck.”
How it works, and how to get it
Access is straightforward: open Chrome, click the Gemini sidebar icon, and sign in with your Google account. It’s free, available on Mac, Windows and ChromeOS in English-US, and has been rolling out since April 2026.
The workflow Anuj demonstrates is the vendor-evaluation example, and it takes five steps:
- Open the Gemini sidebar and run your prompt on any vendor page — “Summarise pricing, core features, and integrations from this page.”
- At the end of the chat, click Save as Skill and name it “Vendor Snapshot.”
- Open all five vendor tabs.
- In the sidebar, type
/, select “Vendor Snapshot,” and add the remaining tabs with +. - Hit run.
Structured summaries across all five tabs, instantly. “Twenty minutes becomes ninety seconds,” Anuj notes. “But the number I care about is the second run, and the fiftieth. The saving compounds.”
The three things Anuj thinks genuinely stand out
Ask him what separates Skills in Chrome from every other prompt-saving workaround, and he lists three.
Multi-tab execution. “This is the headline and people are underrating it. One prompt, five tabs, one click. No other browser-native AI tool is doing this today. It changes research from a sequential task into a parallel one — and comparison work is where knowledge workers lose the most time.”
Workflow memory built into the browser. Skills sync automatically across every signed-in Chrome device. “Your process follows you from the office laptop to the home machine. You stop rebuilding your own toolkit every time you switch hardware.”
Privacy-first design. Confirmation prompts appear before any sensitive action — sending emails, creating calendar events. “This is the part that decides whether a compliance team says yes,” Anuj says. “Agentic features die in enterprises when there’s no confirmation layer. Google building the checkpoint in from day one is a deliberate signal to IT, and it’s the right one.”
Anuj’s one caution
He isn’t uncritical. “The risk with Skills in Chrome is the same risk as with any saved template — you stop questioning the prompt,” he warns. “If your Vendor Snapshot skill asks the wrong three questions, you’ll now get the wrong answer five times faster and with more confidence. Review your Skills quarterly. Treat them like documentation, because that’s what they are.”
He also suggests starting narrow. “Don’t try to save twenty Skills in week one. Find the single prompt you’ve typed more than five times. Save that one. Get the habit, then expand.”
Anuj’s key points at a glance
- The productivity leak is repetition nobody measures — Skills in Chrome makes it visible by removing it.
- A saved Skill is a documented process, not a shortcut; it turns individual skill into team capability.
- Multi-tab execution is the genuine differentiator — comparison research goes from sequential to parallel.
- Cross-device sync means your workflow, not just your prompt, follows you.
- Built-in confirmation prompts are what make this enterprise-viable, not just clever.
- Audit your Skills regularly — a bad prompt saved is a bad answer scaled.
The bottom line
Anuj’s summary is characteristically direct: “Everyone’s waiting for AI to transform their work with some enormous leap. Meanwhile Skills in Chrome quietly hands back four hours a week to anyone doing repeatable research. Take the four hours. That’s the transformation — it just doesn’t look like one from the outside.”