Why Doesn't Gemini Use Your Skill Automatically?
Usually it's the description. Gemini decides whether a skill applies from its name and description alone, before it reads any instructions. Write one or two third-person sentences, and include "Use when..." with specific situations. Also check that the skill is active.
Paste this into a chat, with your skill's current text: Here is a Gemini skill. Name: [name] Description: [description] Instructions: [instructions] Rewrite it to these rules: - Name: starts with an action verb, lowercase with hyphens, no words like helper, tools or data. - Description: 1 to 2 sentences in the third person, stating what it does, then "Use when..." with 3 specific situations. Under 1,024 characters. - Instructions: written for a type of task, not one result. Add an output template, a short "common mistakes" section, and tell Gemini to ask me when information is missing. Then list 3 prompts that should trigger it, and 2 similar ones that shouldn't.
- Start the name with an action verb
- Say what it does, in the third person
- Add "Use when..." with real situations
- Vague names with helper, tools or data
- "I can help you with recipes"
- Go past 1,024 characters
Try it now
- 1Go to Customize > Skills, open the skill, and copy its description. If it's off, click More, then Activate.
- 2Run the prompt above in a chat, then paste the new text into the Description and Instructions fields and click Save.
- 3In a new chat, try the 3 prompts that should trigger it, without naming the skill.
- 4You'll know it worked when it fires on those 3 and stays quiet on the 2 that shouldn't.
Use it when
When a skill works if you call it with / but never fires alone, or fires on the wrong tasks. Also use it when two skills overlap, so that Gemini keeps picking the wrong one.
Skip it when
If you always call the skill by name, then a perfect description matters less, and it's the instructions you should work on. And don't turn one skill into a catch-all with a long list of situations. Split it into two, since Google says to keep descriptions focused.
Why it works
Google's guide says a generic description can stop a skill being used when needed. Its rules: start the name with an action verb, avoid vague words such as "helper", "tools" or "data", and write the name in lowercase with hyphens. Open the description with what the skill does, in the third person, not "I can help you" or "You can use this to". Stay within the limit of 1,024 characters. Only active skills are used automatically. If a skill is off and you ask for it by name, Gemini asks whether to turn it back on.
Example
Google's own example is a recipe skill. Its name, plan-meal-from-recipe, says what it does. Its description says it categorizes recipes, scales portions and builds grocery lists, then says to use it when saving a recipe, adjusting servings or creating a shopping list. A prompt like "I need this for six people" can match that, while the name recipe-data and "I can help you with recipes" gives Gemini much less to go on.
Going further
Match how tightly you direct the skill to the job. Google says creative tasks can have general guidance, while strict ones, such as copying financial data into an exact layout, need step-by-step instructions. Its advice is to treat a skill as a cheat sheet, not a manual, with checklists for long tasks to avoid skipped steps. Put long reference material in an attached file, since Gemini opens files only when needed, and keep the instructions short.
Common mistakes
- Writing the description in the first person. Google's guide specifically says to avoid "I can help you".
- Writing instructions for one result, such as a single meal plan, rather than for a type of task.
- Leaving out what to do with missing information, so Gemini guesses. Tell it to ask.
- Forgetting that a deactivated skill never fires automatically. Check its state before you rewrite anything.
Sources
Checked 6 November 2026. Products change often, so confirm details with the vendor.