Gemini Skills Killed the Gems Menu — and the Slash Key

Last updated: October 4, 2026 · 4-minute read

Two years of muscle memory died quietly this week. Google announced that skills are replacing Gems in the Gemini app, and 9to5Google spotted the change already appearing for some users: typing the old / trigger in the prompt box now shows a migration notice — "/ is now @" — and opens a wider picker where skills sit first, with a shortcut to create new ones. Google also said skills will be free to use, which removes the subscription wall that kept casual users away from Gems. Small UI change on the surface. Underneath, Google is copying homework that the rest of the agent ecosystem already turned in.

Gems were personas. Skills are capabilities.

The distinction matters more than the naming shuffle suggests. A Gem was a person you talked to: a saved system prompt with a name and an avatar — "my SQL tutor", "my strict editor". A skill is a capability the model can load when a task needs it: instructions, scripts and reference material bundled behind a short description. Personas are static; capabilities compose.

That is exactly the path Anthropic walked with Claude: skills launched there in October 2025, and by December the format had opened into a cross-platform standard — the same SKILL.md file now readable by competing agents, which I covered in detail when the format's first malware wave hit its community marketplace. The agent-skills concept won on the merits: it beats re-pasting long prompts, it scales past the context window through progressive disclosure, and it turns agent know-how into something you can version and share. Google adopting the shape — and, per the migration notices, making skills free — is the format winning the platform war, not just the argument.

The '@' key is a small UX decision with big consequences

The slash key made sense when the box held commands. It fails when it holds an ecosystem: slash is already claimed by every Slack workflow, every Discord bot, every CLI reflex a user has. The @ symbol instead reads as addressing — point at a skill, a connector, a thing. The new picker reportedly lists skills first with a create shortcut, and separate reports indicate a broader reorganization in which existing surfaces get renamed toward "Connectors", plus a wider side-panel redesign rolling out.

For most users the change is invisible infrastructure. For the people who built workflows on Gems, the migration has one sharp edge: persona-style Gems and capability-style skills are not the same shape, and some prompts that leaned on a persona's character will need rewriting as task-scoped skills. The practical adjustment: wherever your muscle memory says "describe what I want you to be", think instead "describe what I want done" — then let the skill supply the method.

If your workflow leans on Gems

Practical migration notes, from the shape of the change. Inventory your Gems and sort them by what they actually do: the ones that encode a capability — "review PRs against our style guide" — translate cleanly into skills, because the body is instructions and the description becomes the router. The ones that encode a persona — a character voice, a persistent debating partner — have no skill equivalent, and the honest move is to convert them into a saved prompt template or wait to see whether Google's migration tooling carries them somewhere. Either way, export your Gem instructions now, before the picker moves them; the text is the asset, the container is disposable.

The convergence nobody should be surprised by

Step back and the picture is uniform across the industry. Anthropic defined the skill format and opened it. OpenAI shipped always-on agents with a plugin ecosystem reaching thousands of apps. Google moves its hundreds of millions of Gemini users onto the same capability model. Three companies, one conclusion: the future interface to AI is a toolbox you address explicitly, not a chat partner you configure forever.

My take: the skill model's real payoff arrives when skills become portable across all three platforms the way SKILL.md already is between agents. Google adopting the pattern — even through its own naming and its own picker — drags that outcome closer. The workflow advice that survives every migration is the same one I gave when the standard went cross-platform: invest in the descriptions, because descriptions are what route tasks to capabilities, on every platform, including this one.

The side panel and settings redesign is still rolling out in stages, so do not be surprised if your app shows the old behavior for a while. When the '@' arrives, the migration notice does the teaching for you.

More on the skills ecosystem: how SKILL.md went cross-platform, the knowledge-graph skill this site runs, and the MCP servers worth their keep in Claude Code. The rest of the agent coverage is in the blog.

---

Not affiliated with Google or Anthropic. Sources: 9to5Google (Abner Li, Oct 2, 2026), Google's skills-to-Gems migration announcements as reported there.