Google Is Replacing Gemini Gems With Skills: What PH Businesses Should Do Now

If your team saved a few Gemini Gems for writing Facebook posts, answering customer questions or drafting reports, they're about to change. Google is replacing Gems with skills, and the rollout to the Gemini app starts tomorrow, October 13. Here's what's actually changing, the dates that matter, and how I'd move a small Philippine business, cooperative or office over without losing anything.

AI & Automation Lab

On September 30, Google published an update on its Workspace blog introducing skills in the Gemini app and in Workspace apps like Docs and Gmail, and explaining what happens next to Gems. In plain terms, a skill is a saved set of instructions you can call up whenever you prompt Gemini. That sounds a lot like a Gem, and it is, with three important differences.

First, skills work inside your normal chat instead of in a separate Gem conversation, and you can stack more than one in the same prompt. A "brand voice" skill plus a "Cebuano customer reply" skill, for example. Second, they work across most Workspace apps, not just the Gemini app. Third, Google built them on the open, Markdown-based SKILL.md format, so a skill you write once can be copied to or from other AI platforms that use the same standard. According to Android Headlines, you call a skill by typing a forward slash in the chat box, and Gemini can even suggest turning a prompt you keep repeating into a skill. Google's admin help page notes the "/" trigger will later become "@".

Here's a simplified example of how a small store in Bukidnon might use two skills together. This is an illustration I wrote, not a screenshot:

These come from Google's admin help page on the transition. The bars simply show how far along the transition each date sits, from the first rollout to the education cutoff:

A few details are easy to miss. Google says remaining Gems will be converted automatically, but they'll land as inactive drafts that the creator has to review and switch on. Names, descriptions, instructions and uploaded knowledge files carry over, and so do Drive sharing settings. Google also promises at least 30 days' notice before that auto-migration starts. Skills in the Gemini app and skills in Workspace don't sync yet, so if you want the same skill in both places you create it twice. Workspace skills are limited to users 18 and older on eligible editions (Business Starter, Standard and Plus; Enterprise editions; and certain AI add-ons). And in Workspace Studio you can no longer add an "Ask a Gem" step to new automations, though existing ones keep running until the cutoff.

If you use a personal Gmail account rather than Workspace, the picture is a bit less precise. Android Headlines reports that consumer Gems start phasing out in November and convert to skills automatically. Either way, the direction is the same: skills are the future, Gems are on the way out.

A lot of the small businesses, cooperatives, schools and LGU offices I work with in Bukidnon started using Gemini because it came bundled with Google Workspace or with their Gmail. Their Gems are usually simple: "write a Facebook post in our style," "summarize these minutes," "reply to this inquiry in Cebuano." Nothing breaks this week. But this is the right moment to tidy things up, for three reasons.

Your instructions become a reusable asset. Because SKILL.md is an open, plain-text format, a well-written skill is no longer locked inside one product. That's good for any office that might switch tools later, and good for developers who want to version-control instructions in Git alongside their code.

Stacking fits how Filipino teams actually work. Most of my clients write in two or three languages and serve very different audiences: members, buyers, parents, the LGU. Small single-purpose skills (tone, language, format, policy) that you can combine are easier to maintain than one giant Gem that tries to do everything.

It's a privacy checkpoint. Knowledge files you attached to Gems will follow you into skills. If anyone uploaded member lists, payroll sheets or customer records "just to make it smarter," the migration is your chance to remove them. Under the Data Privacy Act (RA 10173), you're still the one accountable for that personal data.

If you're starting fresh, these three are the ones I'd set up first for most clients:

Marketing

Brand Voice Skill

Your tone, words to avoid, hashtags and sign-off, so every post sounds like you.

Customer Service

Multilingual Reply Skill

Draft replies in English, Filipino or Cebuano using only your approved prices and policies.

Admin

Minutes & Report Skill

Turn meeting notes into a standard minutes or board-report format your office already uses.

A SKILL.md file is just a short header (a name and a description of when to use it) followed by plain instructions. Here are three starters. Switch tabs, copy one, and replace the bracketed parts with your own details. Check Google's skill builder for the exact fields it asks for when you paste them in.

---
name: store-voice
description: Use when writing Facebook posts, captions or announcements for [Store Name].
---

# [Store Name] brand voice

- Friendly, short sentences. Sound like a helpful neighbor, not an ad.
- Mention we are in [Barangay], [Town], Bukidnon when it helps.
- Never promise stock, delivery dates or discounts that aren't in the message.
- Prices only in PHP, written like this: ₱1,250.
- End with: "Message us on our official page only. We never ask for payment through personal accounts."
- No more than 3 hashtags.

---
name: cebuano-reply
description: Use when drafting a reply to a customer message that should be in Cebuano.
---

# Cebuano customer replies

- Reply in natural, polite Cebuano. Use "po" sparingly; match the customer's tone.
- Use ONLY prices and delivery fees from the attached price list. If an item
  or area isn't listed, say we'll confirm and ask for their exact barangay.
- Never ask for or repeat full card numbers, OTPs or passwords.
- Keep it under 80 words.
- Mark the draft "FOR STAFF REVIEW" at the top. A person sends the final message.

---
name: coop-minutes
description: Use when turning rough meeting notes into official minutes for [Cooperative Name].
---

# Cooperative minutes format

1. Header: meeting type, date, venue, time started, presiding officer.
2. Attendance: count only. Do not list member names unless the notes include
   an official attendance sheet, and never include contact details.
3. Agenda items in order, each with: discussion summary, motion, mover,
   seconder, and result.
4. Action items table: task, person responsible, deadline.
5. Time adjourned and "Prepared by: [Secretary]".
Flag anything unclear as [CHECK] instead of guessing.

Read the primary sources before you plan your migration. Dates can shift, and Google says it will post full migration details at least 30 days ahead:

My advice: don't panic and don't wait for March. This week, list your Gems. This month, rebuild the two or three your team uses daily as clean, small skills, and keep a copy of each SKILL.md. If you run AI-assisted workflows for a business in Bukidnon, you can see how I approach this kind of setup on my AI automation page for Quezon, Bukidnon or browse all my services.

Sources: Google Workspace Updates (Sept 30, 2026); Google Workspace Admin Help: About the transition from Gems to skills; Android Headlines (Oct 2026). Dates are Google's published targets and may change.