How to Create Gemini Gems for Your Recurring Work Tasks

What a Gemini Gem actually is

A Gem is Gemini plus a permanent set of instructions and, optionally, a permanent set of reference files. You open it, type the raw input, and it produces output in your format without being reminded who you are. Google ships several premade ones — Brainstormer, Coding partner, Writing editor — but the useful ones are the ones you build for your own recurring work.

The saving is not really in the typing. It is in the consistency. When you retype setup from memory each week, you forget a rule roughly one week in three, and the output quietly changes shape. A Gem does not forget.

Gems are worth building for a task when three things are true:

• You do it at least twice a month, on a predictable rhythm.
• The output has a fixed shape — a template, a length, a tone, a house style.
• The input changes but the instructions do not.

Everything else is better as a normal chat. A one-off competitor question does not need a Gem, and building one is procrastination wearing a productivity costume.

The Standing Brief Method explained

The reason most custom assistants degrade is that people write them like a chat message — a paragraph of friendly instructions with no structure. Before we get to how to create Gemini Gems click by click, here is the shape the instructions need. The Standing Brief Method we teach at PromptPeakAI treats a Gem as three separate layers, each of which prevents a specific failure.

Here is the part most guides get wrong. They tell you to invent your own markup tags and wrap everything in square brackets, as though Gemini were parsing code. It is not. Google’s own guidance on writing Gem instructions names four areas to cover — persona, task, context and format — which is very nearly the Logic System we use across every tool on this site: role, goal, context, format.

Use plain headings. Clarity does the work, not the brackets.

How to create Gemini Gems step by step

The mechanics of how to create Gemini Gems take about four steps. Gems are built in the Gemini web app on a computer — you can use them afterwards on your phone, but the building happens on desktop.

Go to gemini.google.com on a computer and open the left sidebar. You are looking for Explore Gems, which some accounts simply label Gems. That screen lists Google’s premade Gems and anything you have built. Click New Gem.

Name the Gem after the job it does, not the tool — Weekly Ops Report, not Report Helper. Then write the instructions. This is the whole article in one box, so give it real attention rather than a hurried sentence.

Use this scaffold and replace the bracketed parts. It maps directly onto the four areas Google’s documentation recommends covering.

ROLE
You are an experienced [job title] working in [industry or team].
You write for [who reads the output] who have [how much context they have].

GOAL
Every time I give you [type of input], produce [exact deliverable].

CONTEXT
Our team [relevant background in one or two lines].
The audience cares most about [priority] and has no patience for [what they skip].

FORMAT
- [Structure: sections, headings, table, bullet list]
- Length: [word or item count]
- Tone: [plain, formal, warm, direct]

RULES
- Never invent numbers, dates, names, or outcomes. If something is missing, write "NOT STATED" and continue.
- Do not use the words [banned word], [banned word], or [banned word].
- If my input is too thin to do this properly, ask me for the missing piece instead of guessing.

Two things about that scaffold are doing most of the work. The first is the never-invent rule, which turns a silent fabrication into a visible gap you can fill. The second is the banned-word list — negative constraints are the most underrated prompting technique, and a Gem is the ideal place for them because you only have to write them once.

There is a wand icon labelled Use Gemini to re-write instructions. It expands a rough sentence into a fuller brief, which is genuinely useful as a starting draft. Read every line it produces before you keep it — it adds friendly-sounding rules you did not ask for.

Under Knowledge, click Add files. You can upload from your device or pull from Google Drive. Drive access needs Keep Activity switched on and Google Workspace connected to Gemini Apps — if it is not connected, Gemini offers you the link at that moment.

Attach the template and one strong past example. That is usually enough. There is also a Disable knowledge citations option if you would rather the Gem not footnote your own files back at you in every reply.

Use the preview pane on the right and give it one genuine task — real input from real work, not a tidy test case. Check the output against your rules line by line. Fix the instruction that failed, not the output.

Then click Save. This catches people out constantly: previewing does not save your Gem, and closing the tab after a good preview loses the whole thing.

Four Gem blueprints for repeat work

These are complete standing briefs. Paste one into the Instructions box, swap the bracketed parts for your own details, and run the preview test before saving.

Meeting summary to actions

For anyone who leaves a meeting owning the write-up. Pairs well with our full workflow for turning a transcript into minutes.

ROLE
You are a senior operations specialist who writes meeting records for [department] leadership.

GOAL
Every time I paste a raw meeting transcript, produce a decisions-and-actions memo.

CONTEXT
Readers skim this on a phone between meetings. They need to know what was decided and who owes what.

FORMAT
- DECISIONS: bold each decision, one line each
- ACTIONS: a table with columns Owner, Task, Deadline
- OPEN QUESTIONS: bullet list
- Total under 300 words

RULES
- Cut greetings, scheduling chat, and side conversations entirely.
- Never assign an owner who was not named. Write "OWNER NOT STATED".
- Never invent a deadline. Write "NO DATE AGREED".

Difficult client replies

The Gem that saves the most emotional energy, not the most time. It handles the tone so you can handle the substance.

ROLE
You are a client communications editor for a [industry] business.

GOAL
I will paste an unhappy client message and my rough reply. Return a polished version of my reply.

CONTEXT
Our relationships are long-term and renewal-based. Sounding defensive costs us more than admitting a delay does.

FORMAT
- Open by naming their specific frustration in one sentence
- State what we are doing, as numbered steps with dates
- Close with one clear next contact point
- Under 200 words, no greeting boilerplate

RULES
- Never accept legal liability or use the words "fault", "negligent", or "compensation".
- Never promise a date I did not put in my draft.
- Keep my own voice. Do not make it more formal than I wrote it.

Weekly status report

The classic Friday-afternoon job. Attach last quarter’s best report as a knowledge file and this Gem will match its shape without being asked. Our standalone guide to weekly status reports covers the input side in more depth.

ROLE
You are a [department] manager writing the weekly report for [who receives it].

GOAL
I will paste rough notes, bullet points, and pasted updates from the week. Produce the finished report.

CONTEXT
Match the structure and tone of the example report in your knowledge files exactly.

FORMAT
- HEADLINE: one sentence on the week overall
- PROGRESS: what moved, with numbers where I gave them
- RISKS: red, amber or green, with a one-line reason each
- NEXT WEEK: three priorities maximum

RULES
- Use only the numbers in my notes. Never estimate or round to make a point.
- If a section has nothing in it, write "Nothing to report" rather than padding.
- No adjectives like "excellent", "significant", or "robust".

Process into an SOP

For turning the thing only you know how to do into something a colleague can follow.

ROLE
You are a documentation specialist who writes procedures for people doing a task for the first time.

GOAL
I will describe a process in messy spoken language. Produce a standard operating procedure.

CONTEXT
The reader has our normal system access but has never done this task. They will follow it without asking me questions.

FORMAT
- PURPOSE: one sentence
- BEFORE YOU START: access, files, or approvals needed
- STEPS: numbered, one action per step, naming the exact screen or button
- IF IT GOES WRONG: the two most likely failure points and what to do

RULES
- Never invent a menu name, button label, or system I did not mention.
- Where my description is ambiguous, list it under "NEEDS CONFIRMING" at the end.
- No introductory paragraph. Start at PURPOSE.

Knowledge files and your company data

Knowledge files are what separate a Gem from a slightly better prompt. They are also where the risk lives, so it is worth being deliberate rather than uploading whatever is on your desktop.

The privacy line that matters is not free versus paid. It is which account you are signed into. A personal Google account and a work or school Google account are governed by different terms, and your employer’s policy almost certainly draws its line there too.

If you want to keep richer source material available without pushing it into a Gem, notebooks in Gemini are the better home for it.

How to share a Gem with your team

This is where most articles are simply out of date. They will tell you Gems cannot be shared, or that sharing is an enterprise-only feature. Neither is true now.

Sharing runs on the same machinery as Google Drive, and Google’s documentation on sharing a Gem confirms it works from personal accounts as well as work ones. Open the Gem manager, click Share next to your Gem, and you get the interface you already know:

• Share to specific email addresses, or generate a link.
• Choose whether people can use the Gem or also edit it.
• Add an expiry date on someone’s access if you want to.
• Shared Gems land in a Drive folder, along with any files attached to them.

One caution before you press Share: everyone with access can read your instructions and open your knowledge files. If your brief contains internal context you would not email externally, strip it first. And on a work or school account, an administrator can switch Gem sharing off entirely — if the Share button is missing, that is usually why, not a bug.

Gems, Custom GPTs, or Claude Projects?

The honest answer is that all three do the same core job, and the deciding factor is boring: where your files already live.

If your team runs on Google Workspace, Gems win on the Drive connection alone and there is little point agonising over it. If you are on Microsoft or your documents live in email attachments, building a Custom GPT or setting up a Claude Project is the more sensible route. The instruction-writing skill transfers between all three unchanged, which is the actual point.

Where Gems still fall short

A Gem removes the setup. It does not remove you.

There is a newer capability worth knowing about but not building on yet: Gems from Google Labs, which are AI mini-apps created through Opal and shown under a separate heading in the Gem manager. They are web-only, English-only, personal accounts only, and your existing Gems cannot be converted into them. Interesting; not yet a work tool.

On the question people actually worry about — will anyone know you used a Gem — the output carries your rules, your template and your knowledge files, so it looks like your work because it is shaped by your judgement. What gives people away is publishing without reading, which was true long before any of this existed.

When your Gem ignores its instructions

Drift is normal and fixable. The trick is diagnosing which layer of the standing brief is missing rather than rewriting the whole thing in frustration.

The single most common cause is a rule buried mid-paragraph in a wall of friendly prose. A Gem’s instructions sit above anything you type in the chat, which is worth understanding properly — the instruction hierarchy explains why the same wording behaves differently in different places. Instructions that read like a chat message get treated like one.

Change one thing, re-run the identical test input, compare. Two changes at once and you learn nothing about either.

Build one Gem this week, not five. The instinct to systematise everything at once is the reason most people end up with a folder of assistants they never open. Get one working properly, use it four times, and you will know exactly what the second one should be — that is how a personal AI workflow library actually gets built.

None of this is gated behind a subscription, incidentally. Knowing how to create Gemini Gems is enough on a free account; the paid tiers raise your usage limits rather than unlocking the feature, and our breakdown of the Gemini plans has the detail if you are weighing it up.