Google Turns Gemini Prompts Into Persistent Browser Tools, Narrowing the Gap With Dedicated AI Assistants
Google has launched "Skills" inside Chrome, a feature that lets users save custom Gemini prompts as reusable, one-click actions directly within the browser.
10. Google Turns Gemini Prompts Into Persistent Browser Tools, Narrowing the Gap With Dedicated AI Assistants
Google has launched "Skills" inside Chrome, a feature that lets users save custom Gemini prompts as reusable, one-click actions directly within the browser. Users can either build their own saved prompts or pull from a Google-curated library of premade Skills, effectively turning ad hoc AI interactions into persistent productivity shortcuts. The move embeds Gemini more deeply into Chrome's interface rather than treating it as a sidebar chatbot requiring fresh instruction each session.
This matters because it directly attacks the primary friction point that limits casual AI adoption: the need to re-engineer prompts repeatedly for recurring tasks. Power users at companies like OpenAI and Anthropic have long relied on custom instructions, GPTs, and Projects to solve this exact problem, but those solutions live inside dedicated apps. By anchoring Skills to Chrome itself, Google reaches the much larger population of users who never leave the browser for a standalone AI tool. Microsoft is the clearest loser here, as Copilot's browser integration in Edge has been its main differentiator for Gemini-adjacent users; a polished Skills library makes that advantage thinner. For Google, the win is behavioral lock-in: every saved Skill is a small thread tying a user's workflow to Chrome and, by extension, to Gemini's model consumption.
The broader signal is that the browser is becoming the primary battleground for AI habit formation, not the standalone chatbot interface. Google, Microsoft, and increasingly Opera and Arc are racing to make their browsers the layer where AI behavior gets encoded and recalled. Skills fits a pattern where the model matters less than the workflow surface it inhabits, and the vendor who owns the browser owns the prompt memory. That structural advantage compounds over time in ways that API-level competition cannot easily replicate.