The Death of the Persona: Why Google's Pivot to 'Skills' is a Quiet Admission of Failure

For the last two years, the race in generative AI has been framed as a battle of personalities. We were told that the future of productivity lay in 'personas'—specialized, branded AI assistants that could act as your nutritionist, your coding partner, or your career guide. Google leaned hard into this vision with the 2024 launch of 'Gems,' a feature designed to let users build custom AI assistants for specific tasks so they wouldn't have to repeat instructions.

But as reported by TechCrunch and 9to5Google, that vision is officially dead. Google has announced it is shutting down Gems, migrating them instead into a new format called 'skills.' Starting November 17, 2026, the curated personas that Google hoped would drive popularity for the Gemini AI app will be stripped of their identity and turned into utility functions.

In my view, this isn't just a rebranding exercise. It is a critical admission that the 'persona' model of AI is a friction point, not a feature.

When Google launched Gems, it provided pre-made options like a learning coach, a brainstorming assistant, and an editor. Users were encouraged to build their own—perhaps a vacation planner or a running coach—and share them with others. The goal was to create a library of distinct agents. But the reality of user behavior is that people don't want to manage a roster of AI personalities; they want the AI to simply *do the thing*.

By pivoting to 'skills,' Google is moving toward a model of invisible utility. A 'skill' doesn't pretend to be a coach; it is simply a capability. This shift suggests that 'teaching' an AI to be a specific character was an unnecessary layer of abstraction.

However, Google's execution reveals a lingering disconnect. According to TechCrunch, these new skills won't be integrated seamlessly into the natural language flow. Instead, users will have to enter a forward slash "/" within a task thread to select the specific skill they wish to employ.

This is a classic Google misstep. As TechCrunch notes, a slash-command interface is something engineers prefer, not 'regular folks.' While Google is moving away from the cumbersome branding of Gems, it is replacing it with a technical hurdle. It stands in stark contrast to the 'all-in-one' AI agent approach seen in competitors like Meta’s Muse and Instinct, where the utility is integrated and frictionless.

This pattern of erratic feature deployment is nothing new. TechCrunch points out that Google has a history of shuffling features and over-branding, citing the company's previous struggle with operating multiple different messaging and communication apps simultaneously. By giving every new AI feature its own icon and placement, only to merge or kill them later, Google creates a fragmented user experience.

Google claims that the transition to skills will be automatic, meaning users won't have to lift a finger to migrate their existing Gems. While this solves the immediate problem of data loss, it doesn't solve the identity crisis of the Gemini app.

If the goal of AI is to become an intuitive extension of human intent, then the 'persona' was always a distraction. The move to 'skills' is the correct strategic direction, but by hiding that utility behind a slash command, Google is proving once again that it struggles to translate technical capability into consumer-friendly design.