Gems: agents with Workspace in their bones.
Gems are Google's answer to Custom GPTs — custom agents with system prompts, instructions, and access to your Workspace data. A Custom GPT is a tool you bolt onto ChatGPT; a Gem lives inside the Google ecosystem. Building a good one is two things: sharp instructions, and telling it when to reach into Workspace.
Instructions, plus knowing when to look.
The difference between a useful Gem and a useless one is the same as a Custom GPT — instruction quality. But Gems add a second lever Custom GPTs don't have: native Workspace access. The skill is wiring it so the Gem pulls context exactly when it helps, and not when it doesn't.
A tool you bolt onto ChatGPT. Knows only what you upload.
Lives in Workspace. Can search Drive, read Gmail, check Calendar — when you tell it to.
Four sections that hold up.
Same dependable shape as a strong Custom GPT prompt. Here's an "Email triage" Gem in the pattern:
You triage email so I never have to read one in full.
Categorize [Action]/[Reply]/[Read]/[Skip]; suggest a specific next step; draft a 3–5 sentence reply in my voice; flag deadlines.
[2–3 of my real replies] — direct, short sentences, no AI tells.
No "Hope this finds you well"; don't suggest meetings unless asked; drafts only — never reply on my behalf.
Tell it when to reach into Workspace.
This is what makes a Gem more than a Custom GPT: instructions that say when to pull context. For each trigger, pick the source the Gem should reach — and notice when the answer is "don't reach at all."
Vague Gem, vague output.
For each section, pick the line that makes a sharper Gem — specific about what to do, and what not to.
Skills are coming for Gems. On September 30, 2026 Google added skills to Gemini chat: reusable instructions you can build from a conversation, that Gemini runs automatically when a prompt matches, and that can be stacked together. Google's release notes say skills will eventually replace Gems, with existing Gems migrated automatically when Gems is retired. Skills launched for users 18+ globally with a phased rollout, so you may not see them yet; Gems still work today. Everything on this page about scoping sources and sharing carefully carries over.
Scope access narrowly — specific folders/accounts, not everything. And every team Gem needs an owner with a quarterly review; an ownerless shared Gem goes stale and starts misleading people. Name it clearly ("Acme Sales Gem v2") and note who owns it.
Build one Gem you'll use this week
Pick a task you do 3+ times a week. Write it with the four-section pattern, wire 1–2 Workspace triggers (scoped narrowly), and use it five times this week — refining the instructions based on what's not working, not theory.
What you can do now
- Use the four-section pattern: Identity, What you do, Voice, What you don't do
- Wire Workspace triggers — and skip the lookup when general knowledge is enough
- Scope Workspace access to specific folders/accounts, not all of Drive
- Give every team Gem an owner with a quarterly review
- Iterate on instructions from real use, not theory