Google's Gems Are Becoming Skills — Build Your First Reusable AI Assistant

If you built a Gemini Gem — a saved set of instructions that turned rough notes into polished output — Google is replacing Gems with skills. The idea is the same (save your instructions once, reuse them forever), but the mechanics are better: instead of opening a separate assistant from a side panel, you invoke a skill inside any chat by typing / followed by the skill's name. This guide explains what changed and walks through building your first skill from start to finish. No coding. No technical setup.

What a Skill Is — and What Changed From Gems

A skill is a named, reusable set of instructions that Gemini applies whenever you invoke it. Think of it as a saved prompt — with a name, a description, and rules — that you can call up inside any conversation instead of re-explaining everything from scratch.

The differences from Gems are all about where the instructions live and how you reach them:

The Project: A Weekly Report Writer Skill

Almost every professional writes some version of a weekly status report. It goes to a manager, a client, a team, or a stakeholder. The format is usually the same every week. The content changes, but the structure doesn't. And it takes 20–45 minutes to write properly — time that most people would rather spend on actual work.

This is a perfect skill because:

• The task is repetitive — it happens every week
• The format is consistent — same sections, same tone, same audience
• The input is messy — rough notes, bullet points, half-thoughts
• The output needs to be polished — clear, professional, structured

The skill built here takes rough weekly notes — bullet points, fragments, raw numbers — and transforms them into a polished, structured report with an executive summary, achievements, blockers, metrics, and next steps. Every week. In about two minutes instead of thirty.

Step 1: Open the Skills Manager

Go to gemini.google.com in your browser. On the sidebar, click Settings, then Skills. Near the top of the Skills page, click Create manually.

Google's skills page offers other starting points too — describing what you want in a chat and letting Gemini build it, starting from a template, or uploading a SKILL.md file — but Create manually gives you full control over the instructions.

Step 2: Name It and Write the Instructions

Give the skill a name and a short description — the description matters because it helps Gemini recognize when to apply the skill automatically. Then write the instructions. This is the core of the skill: what it does, how it formats output, what tone it uses, and what rules it follows. Good instructions produce consistently good output. Vague instructions produce inconsistent results.

Google's own guidance for effective skills boils down to three practices: define when to use it (describe the situations where the skill applies, so auto-invoke works), keep it concise (only the unique guidelines for the task), and provide examples (show the output you expect).

The instructions below follow a five-part structure — Role, Objective, Details, Examples, Sense Check — that covers the same ground. You can copy these directly:

That last section — WHEN TO USE — is the skill-era addition. With Gems you always opened the assistant yourself; with skills, this description is what lets Gemini offer or auto-apply the skill when it recognizes the task. Write it plainly.

Step 3: Add Reference Files (Optional)

If you have a report your manager loves, upload it as a reference file (text, PDF, or image) and add one line to the instructions: "Match the structure and tone of the uploaded sample report." A brand style guide or project brief works the same way. Google Drive files are coming in the following weeks — for now, upload from your device.

Step 4: Save It and Use It in Any Chat

Click Create at the top. Now the weekly workflow becomes:

1. Open any Gemini chat and type /Weekly Report Writer (or let Gemini suggest it when you paste your notes)
2. Paste or type your rough notes for the week
3. Review the generated report
4. Ask for adjustments ("make the executive summary shorter" or "move the API metric to the top")
5. Copy the final version into your email, chat app, or document

The entire process takes 2–5 minutes instead of 20–45 — and you can stack skills, so a writing-style skill plus the report skill can shape the same output together.

Step 5: Refine Over Time

A skill is not a set-and-forget tool. The best ones get refined over the first few uses as you notice patterns in the output that need adjustment.

After using the Weekly Report Writer for 2–3 weeks, you'll likely notice things like:

• The executive summary is too long or too short for your audience
• The tone is slightly too formal (or too casual) for your team culture
• You want a specific section your company uses (like "Client Updates" or "Budget Status")
• Certain types of notes consistently get misinterpreted

To fix these, open the skill from Settings > Skills and update the instructions. Each fix makes the skill more useful for your specific context. After 3–4 rounds of refinement, the skill will produce output that needs almost no editing.

One more thing worth knowing: because Gemini can apply skills automatically, check the WHEN TO USE description if a skill ever fires when you didn't want it. You can open the skill from Settings > Skills and deactivate it — Gemini will ask before turning it back on.

Five More Skills Worth Building

The Weekly Report Writer demonstrates the pattern. Here are five more skills that follow the same logic — repetitive task, consistent format, messy input, polished output:

Each of these follows the same build process: identify the task, define the structure, write clear instructions, test, refine.

The Takeaway

Skills are the simplest way to go from "using AI occasionally" to "using AI as a reliable part of your workflow." The difference is not the model's capability — it's the elimination of repetitive context-setting that makes one-off AI usage feel slow and inconsistent. And the skill model improves on Gems in the ways that matter: your instructions travel with you into any chat instead of living in a separate panel, they can combine, and Gemini can apply them unprompted.

The playbook is straightforward:

1. Find a repetitive task with a consistent format
2. Write clear instructions — define when to use it, keep them concise, include examples
3. Test with real inputs, not hypothetical ones
4. Refine the instructions over 2–3 uses based on what you actually had to fix
5. Attach reference files to ground the skill in your specific environment

A well-built skill doesn't just save time on one task. It changes the economics of how you work with AI — from a tool you use when you remember to, to an assistant that's ready every time you need it.

Sources

• Google Blog — Automate repetitive tasks with Skills (September 2026)
• Google Support — About the transition from Gems to skills