UpTrajectory Review

Google is retiring its Gemini Gems feature on November 17 and folding the concept into a broader system it calls Skills, according to TechRepublic. Gems were Google's answer to custom AI personas — reusable prompts and configurations that let users create a tailored assistant for a specific task, like drafting customer emails or generating reports. The shift to Skills appears to be more than a rebrand; it signals Google's attempt to make its AI assistant more modular and capable across its product ecosystem, though the full scope of what Skills will do beyond what Gems did is not clear from the announcement alone.

For small business operators who have built workflows around Gems, this is a forced migration with real friction. If you spent time configuring custom Gems for things like invoice generation, client onboarding scripts, or marketing copy drafts, you will need to understand how Skills differs, whether your existing configurations carry over, and what breaks in the transition. The mention of changes to age eligibility, Keep Activity, files, sharing, and supported tools suggests Google is tightening or restructuring several access points at once, which means the version of Gemini your team uses on November 18 may not behave the way it did on November 16.

What stands out here is the breadth of the change bundled into a single cutover date. Google is not just renaming a feature; it is simultaneously adjusting who can use it, how data is retained through Keep Activity, how files are handled, and what sharing looks like. That is a lot of surface area to change at once, and it raises the question of whether Google is prioritizing platform consistency over user continuity. We are skeptical that most small business users will find the transition seamless, especially if they rely on shared Gems across a team and the new sharing model introduces different permissions or access rules.

The downstream effects split users into two camps. Individual operators who used Gems lightly may barely notice the change, or may even find Skills more intuitive. Teams that embedded Gems into repeatable processes — especially those involving shared files, client data, or collaborative prompting — face a different risk: broken workflows, lost configurations, or unexpected changes in how their data is stored and surfaced through Keep Activity. There is also a cost in time. Someone on your team will need to audit what Gems exist, map them to whatever Skills replaces them, and retrain staff if the interface or logic shifts.

The practical move before November 17 is to inventory every Gem your business relies on, document what each one does, and test whether a Skill can replicate it before the deadline. If your team shares Gems, confirm whether sharing settings carry over or need to be rebuilt. Pay close attention to the Keep Activity and file handling changes, since those affect data retention and could complicate anything involving client records or proprietary templates. Google has a habit of sunsetting features with minimal fanfare, and this transition looks like another case where the burden of adaptation falls on the user, not the platform.

“Google begins moving Gemini Gems to skills Nov. 17, with changes to age eligibility, Keep Activity, files, sharing, and supported tools.” — TechRepublic

Takeaway: Audit every Gemini Gem your business uses before November 17 and confirm Skills can replicate them, especially shared team configurations and file-dependent workflows.