TechCrunch is reporting that Google is adding a feature called Skills to the Chrome browser, allowing users to save AI prompts and replay them across different websites. The capability is built on top of Gemini, Google's AI assistant, which has been steadily expanding its footprint inside Chrome over the past year.
To understand why this is worth paying attention to, it helps to step back and look at what Google is actually trying to build. Chrome is not merely a browser at this point — it is the most-used piece of software on the planet, a platform in its own right, and the primary surface through which most people interact with the web. For years, Google's challenge has been figuring out how to make AI genuinely useful inside that surface rather than bolting it on as a novelty. Early Gemini integrations in Chrome were largely reactive: a user could ask a question, get a summary, or have text explained. Skills, if it works as described, represents a shift toward something more proactive and repeatable. The user is no longer just querying an AI; they are training a personal workflow layer that sits on top of the web itself.
The concept of reusable AI prompts is not entirely new. Power users of tools like ChatGPT and Claude have long assembled libraries of custom instructions, and third-party browser extensions have tried to offer similar functionality with varying degrees of success. What Google is doing differently is integrating this at the browser level, which carries significant implications. A browser-native feature has access to page context, login states, and browsing history in ways that a third-party extension simply cannot match at scale. The likely reading here is that Google wants Skills to become the default way people automate repetitive web tasks — the modern equivalent of bookmarks, but for actions rather than destinations.
This also fits a longer competitive pattern. Microsoft has been aggressively embedding Copilot into Edge, its own Chromium-based browser, and has used that integration as a genuine selling point in its effort to win back browser market share. Google has watched Edge grow, slowly but measurably, particularly in enterprise environments where Microsoft's bundled software has natural advantages. Skills looks like part of Google's answer: rather than trying to out-feature Copilot on a spec-by-spec basis, the strategy appears to be deepening the lock-in that comes with Chrome's scale. If a user's personalized AI workflows live in Chrome, switching browsers carries a real cost that it did not carry before.
For everyday users, the appeal is straightforward enough. Anyone who regularly performs the same multi-step task on the web — formatting a document a particular way, extracting specific information from a class of pages, drafting messages in a consistent voice — would benefit from being able to save that process once and recall it anywhere. The friction reduction is genuine. Whether people actually build up libraries of Skills, or whether the feature goes the way of many productivity tools and sits largely unused, is another question. Adoption of this kind of capability tends to be uneven; power users embrace it immediately while the broader population discovers it slowly, if at all.
For developers and publishers, the implications are more complicated. If users are running AI workflows across websites, they are increasingly interacting with page content through an abstraction layer rather than directly. That has consequences for advertising, for engagement metrics, and for the broader question of what a page visit actually means in an AI-mediated browsing environment. Publishers have already been grappling with AI summaries reducing click-through from search; a browser that can replay customized AI instructions against any page extends that same logic into the browsing session itself.
For Google's competitors in the AI assistant space, this is a reminder of the structural advantage that owning the browser provides. OpenAI, Anthropic, and others can build capable AI products, but they remain dependent on the browser to reach users. Google is the browser, for most of the world, and Skills is another demonstration of what that means in practice.
What to watch for next is whether Skills remains a Chrome-exclusive feature or whether Google eventually opens some form of it to the Android and ChromeOS ecosystems more broadly, which would extend its reach considerably. Also worth watching is how Microsoft responds within Edge and whether Apple makes any moves to deepen AI integration in Safari, which has so far taken a comparatively cautious approach. Finally, the regulatory environment around browser bundling and default AI services is still evolving in both the United States and Europe, and a feature that makes Chrome's AI layer feel indispensable to daily workflows is exactly the kind of development that tends to attract the attention of competition authorities already scrutinizing Google's market position.
