A Gemini Gem is a saved set of instructions and optional reference material that guides Gemini’s replies to a recurring conversational task. A marketing team, for example, could use a Gem to review drafts against an audience definition, tone guide, and claims policy. A Gem is not, by itself, a tool for updating a CRM, sending an email, or changing another external system.
Timing matters: as of November 14, 2026, Google says personal-account Gems for users age 18 or older become read-only on November 17, 2026, then are removed from Gemini Apps on December 17, 2026. Google says Gems will transition automatically to skills. Workspace business, enterprise, and nonprofit accounts are scheduled for March 2027, and education accounts for June 2027. Check Google’s Gems-to-skills transition guide for the current schedule and file-transfer conditions.
This makes Gems useful as a short-term conversational configuration and as a maintenance task. Create or review one when you need consistent guidance and reference material, but preserve important files and retest the resulting skill before relying on it.
What Gemini Gems do, and what changes next
A Gem gives Gemini reusable response guidance. Its instructions and Knowledge can provide context for a task without requiring you to repeat the same setup in every conversation. Google says skills can be invoked in any chat, may be recognized automatically, and can be stacked. That behavior is different from simply opening one saved Gem, so important Gems deserve a review before the relevant account transition date.
You must be signed in to Gemini Apps to create or use Gems. Availability can vary with account type, age, country, language, and administrator settings. Google also says Gems do not currently work with Gemini Live. Use a Gem when the recurring need is consistent conversational guidance or reference material. If the requirement is to change an external system, design and verify that action separately.
Use a Gem to standardize how Gemini responds. Use a separately verified workflow to decide whether another system should change.
Create a Gem in the Gemini web app
Google documents custom Gem creation in the web app. Gems can also be used in Gemini’s web and mobile apps. To create one, open gemini.google.com, sign in, open the sidebar, choose Gems, then choose New Gem. Enter a name and instructions, optionally add Knowledge, preview the Gem with a prompt, and choose Save. If Gems is not visible, follow Google’s documented Settings and help route rather than relying on a menu path that may have changed. See Google’s official Gems guide for current steps.
Write instructions that define the job, audience, boundaries, response format, and when Gemini should ask for clarification. For a hypothetical marketing-brief reviewer, the instructions could say: Review the supplied draft for the stated audience and tone. Flag claims that lack evidence in the supplied material. Do not invent sources. Return a concise review with missing evidence and suggested revisions. Ask a question if the audience or claims policy is unclear.
Gemini can rewrite or expand instructions, but review the revision before saving. Preview the Gem with three distinct prompts: a typical request, a request with missing context, and a request outside the intended scope. Use the results to revise the instructions. Preview is a practical test of behavior, not a formal accuracy, compliance, or deterministic-output test.
Add Knowledge files and check what will transfer
Gem Knowledge can include uploaded files, Google Drive files, and NotebookLM notebooks, subject to account, administrator, file-type, storage, and usage limits. For Drive files, Google requires Keep Activity to be enabled and Google Workspace to be connected to Gemini Apps. Google says a linked Drive file uses its most recent version and that later changes are reflected in the Gem.
Check access and source provenance before relying on a file, especially when the material is important or sensitive. A linked file can change, lose access, or contain information that does not answer the user’s question. Do not upload confidential or regulated material without checking the applicable Google account, Workspace, and organizational data-governance terms.
Google’s skills transition guide sets a 100 MB total file limit and says some Knowledge files will not transfer. It lists GitHub files, audio, video, legacy Microsoft Office formats, and archives among excluded types. If the limit is exceeded, Google may remove the largest files first. Personal-account users who need potentially unsupported files should download them before December 17, 2026, then inspect the converted skill and retest important prompts.
- Inventory each Gem’s uploaded files, Drive sources, and NotebookLM notebooks.
- Check file formats and total size against Google’s 100 MB skills limit.
- Confirm that Drive files have the required activity and Workspace settings, and that the user still has access.
- Download files that may not transfer before the relevant deadline, then inspect the skill and rerun prompts that depend on those sources.
Use, edit, share, copy, or delete a Gem
Open a Gem from Gemini to use it in a chat. To edit one, go to My Gems, select it, make changes, and use the current save or submit control. Google’s current desktop instructions say Submit; labels can vary by release or interface.
Google documents sharing Gems and conversations made with them. A shared Gem is added to the recipient’s My Gems after the recipient opens and interacts with it. Before sharing, check that its instructions and Knowledge are suitable for that recipient.
To delete a Gem, use its options menu and confirm deletion. The reviewed Google help page does not specify whether related chats or public links are retained, so do not assume either outcome. Zapier’s guide reports a Make a copy option, but the reviewed Google help page does not confirm that workflow. Treat it as an interface option to check, not a guaranteed Google feature. Before deleting or replacing a Gem, preserve any instructions and Knowledge files you still need.
A Gem is not an automation engine
A Gem is a reusable instruction configuration, not a verified execution layer for writing to another application. Zapier lists Gemini as an MCP-compatible client, but that does not establish that a Gem itself can call Zapier tools. Zapier MCP connects a compatible client to available Zapier tools and connected apps. The client must support Streamable HTTP, and specific actions, account access, permissions, plan conditions, and task use must be checked.
Zapier currently advertises 9,000+ apps and 40,000+ actions through MCP. That is a product claim, not a guarantee that a particular action is available to your account. Verify the target application, action, required fields, permissions, and approval route before exposing a tool. Do not describe MCP as an event-trigger system unless a separate trigger mechanism has been verified.
For an AI-assisted write, use AI for ambiguous language, drafting, or candidate-field extraction. Use ordinary rules for required fields, allowed values, permissions, thresholds, target identity, and duplicate controls. For high-impact changes, external messages, deletion, or financial actions, require a person to approve the proposed action.
Gemini’s support as an MCP client is not proof that a Gem can execute an external action. Verify the client and specific tool separately, expose only the actions needed, and put an approval gate before consequential writes.
If a separately verified external write is approved, distinguish the source request, tool-call attempt, destination mutation, and audit event. Store a request identifier, source reference, tool name, target record identifier, normalized mutation data, result status, timestamp, and reviewer decision at the appropriate grain. Do not use only date, user, and application as a deduplication key.
When concurrent retries could create duplicates, use a destination-supported unique constraint or transactional upsert. A lookup-then-create check can race. If the destination offers no reliable uniqueness control, route possible duplicates to a person instead of claiming they are prevented. For help designing a separately scoped workflow, see Zapier automation consulting or AI agent design and implementation.
Hypothetical example: review a marketing brief before publication
Keep the Gem’s job to reviewing and structuring a draft. The editor, not the Gem, decides whether it is ready to publish. The following is an illustrative operating pattern, not a Google or Zapier template.
Input: a draft, intended audience, tone rules, claims policy, and optional Knowledge files. AI job: identify unsupported claims, classify the draft against the supplied rules, and suggest revisions. Validation: a deterministic publication check blocks handoff when required evidence is missing or a mandatory disclaimer is absent. Destination: the Gemini conversation for review; any CMS or email action is a separate approved workflow. Exception owner: the editor resolves ambiguity and evidence gaps.
A compact output contract could look like this:
{
"source_request_id": "req_2026_00127",
"status": "review_required",
"missing_evidence": [
"Source needed for the performance claim"
],
"approved_claims": [],
"rejected_claims": [
"Claim conflicts with the supplied policy"
],
"revision_notes": [
"Add a source or remove the performance claim"
],
"requires_editor_approval": true
}The source_request_id identifies the review request, not a CRM contact, tool call, or destination mutation. If the editor later approves a CMS update, create a separate tool-call record and destination-event record. If a retry occurs, preserve the original request identifier and use a destination-enforced unique constraint or transactional upsert for the intended mutation where supported. Otherwise, send the possible duplicate to review.
These fields are illustrative implementation guidance. The editor resolves the evidence gap and approves the draft. Only then should a separately verified CMS or email action be considered. Record the source reference, destination record ID, reviewer, and outcome so the team can trace what was approved and where it went.
Frequently asked questions
Can I create or edit a Gem on mobile?
Google documents custom Gem creation, editing, and deletion as web-app tasks. Gems can be used in Gemini’s mobile app. See Google’s mobile Gems guidance for the current distinction.
Can a Gem use a Drive file that changes?
Google says a linked Drive file uses its most recent version and that later changes are reflected in the Gem, provided the required Drive and Gemini settings are in place. Access and source changes should still be checked when the file matters.
Can I use a Gem with Gemini Live?
No. Google says Gems do not currently work with Gemini Live.
Will all my Knowledge files become part of a skill?
Not necessarily. Check the 100 MB limit and excluded file types in the transition guide, preserve files you need, and inspect the skill after conversion.
Does deleting a Gem delete its chats or public links?
The reviewed Google help page explains how to delete a Gem but does not specify what happens to related chats or public links. Check the current account behavior and preserve anything you need before deleting.