GEMINI OMNI PROMPTS

Blog / 6 min read · 2026-10-14

Gemini Skills vs Gems: Migrate and Stack Brand Prompts

Turn a Gemini Gem into reusable skills, combine brand voice with writing formats, and try a copyable SKILL.md example with rollout caveats.

gemini-skills gems brand writing

If your Gemini Gem mixes your brand voice, product facts, and newsletter format into one long instruction, Skills offer a useful opportunity to separate those jobs. Keep the voice reusable, change the format when needed, and supply current facts with each assignment.

This guide walks through that approach with a fictional stationery brand. The templates are original design examples, not account-tested Gemini outputs. Product details and navigation below come from Google’s documentation checked on October 14, 2026.

What changes from Gems to Skills?

Google describes Skills as saved instructions that work inside a regular Gemini conversation. You can combine several, invoke them explicitly, or let Gemini apply relevant activated skills. Google’s September announcement also describes reference-file support and a staged transition from Gems. Google’s Skills announcement

For a writing workflow, think in three layers:

Keep the brief outside the reusable instructions. Otherwise, yesterday’s launch date can quietly become tomorrow’s mistake.

Check your account before migrating

There is no single retirement date for everyone:

Documentation is not fully aligned: Gemini’s general Skills help still describes personal accounts, age 18+, and Keep Activity enabled, while Workspace’s dated update confirms the Gemini app rollout for Workspace users. A launch date does not guarantee your account already has access. Gemini Skills requirements

Move one useful Gem first

Choose a Gem whose results you already trust. Save its instructions, description, and knowledge files before changing anything. Early manual migration is optional: Google says it will automatically transition personal-account Gems and supported files when Gems are removed. Keep your working Gem while you test.

Google’s manual process copies the Gem’s details into a new skill. To move knowledge files, download the new skill, combine its SKILL.md with the files, and replace the skill with that package. Follow the current official migration steps, especially if your Gem uses attachments.

Then improve the design:

  1. Highlight instructions that should apply to every piece of brand writing.
  2. Move newsletter-only or caption-only requirements into separate skills.
  3. Remove expired offers, campaign dates, and product availability.
  4. Keep one previous brief and approved answer as a comparison case.

The current desktop help lists Customize → Skills, then Create → Create manually, or Upload for a file package. These are documented paths, not a claim that we tested your interface. Creation instructions

Copyable SKILL.md: a reusable brand voice

Save the following as SKILL.md inside a folder named harborline-voice. Harborline Paper is fictional; replace its voice rules with yours.

The YAML header follows the open format’s required name and description fields. The name matches the folder. This is a plain-text example without scripts or external dependencies. Agent Skills specification

---
name: harborline-voice
description: Apply Harborline Paper's calm, practical voice when drafting or revising its marketing copy.
---

# Harborline Paper voice

## Scope
Use for Harborline Paper marketing drafts and revisions.
Do not apply this brand voice to unrelated tasks.

## Voice
- Address the reader as "you" when useful.
- Prefer concrete benefits and familiar words.
- Keep paragraphs short. Avoid forced enthusiasm.
- Avoid "revolutionary," "game-changing," and "unlock."

## Factual boundaries
- Use only product facts supplied in the current brief or
  explicitly identified reference material.
- Never invent prices, reviews, certifications, materials,
  delivery promises, or environmental benefits.
- If sources conflict, flag the conflict before drafting.
- If a required detail is absent, ask or mark [NEEDS INPUT].

## Combining instructions
Let the selected format skill set the structure and length.
Never satisfy a format requirement by inventing a fact.
Flag unresolved instruction conflicts instead of guessing.

## Final check
Remove unsupported claims and banned phrases.
Return the requested draft, then a short verification note.
Draft only; do not publish or send anything.

For a first trial, use the text alone. Add reference files only after checking that you are allowed to upload them and that their contents are current.

Stack a format skill with the voice

Create a second skill named product-launch-blurb with this description: “Draft a short product-launch blurb when the user supplies a launch brief.” Use these instructions:

Return one headline of at most eight words, an 80–100-word
body, and one call to action. Use the selected brand voice.
The body word count excludes the headline, call to action,
and verification note. Base all claims on supplied facts.
If there are too few facts, ask for more rather than padding.

Select both skills, then paste this fictional test brief:

Draft a launch blurb for Harborline Paper.
Audience: people who keep a daily desk notebook.
Approved facts: A5 size, dot-grid pages, 160 pages, olive
cover, price $16, available online October 20, 2026.
CTA: View the notebook.
Do not imply that the paper is recycled or certified.

In Gemini chat, current help documents / or, with the updated shortcut, @ followed by a skill selection. Select the actual suggestions rather than assuming a typed name attached the skill. Using Skills

This separation lets you reuse the same voice for a different format without copying every tone rule again.

Test before replacing your working Gem

Run the same brief through the old Gem and the new combination. Check the output against five requirements:

  1. Price and date match the brief exactly.
  2. No recycled-paper claim appears.
  3. Headline and body meet their separate length limits.
  4. Tone is calm without becoming vague.
  5. Missing facts are flagged instead of invented.

Next, remove the price and request a price-led headline. The useful behavior is a question or placeholder. A confident invented price is a failed test. Save the instructions and results so later edits can be compared.

Two limits worth planning around

Skills currently do not sync between the Gemini app and Workspace apps; recreate them separately if you need both, once the relevant rollout reaches your account. Workspace migration guidance

Do not assume a migrated writing skill preserves every Gem tool. Google’s transition help currently lists limitations involving Canvas, Deep Research, and default tools such as Create video. Compatibility notes

Start with one voice, one format, and one repeatable test. The goal is a smaller set of instructions you can maintain and trust.