Your brand rules need one home, not a copy in every AI tool

Skills in Google Workspace are copies, and copies drift. Here is how to keep one brand standard and a short, dated pointer in every AI tool.

November 18, 2026 2 minutes
Your brand rules need one home, not a copy in every AI tool

Google began rolling out skills across Workspace on 9 November. A skill is a reusable set of instructions that tells Gemini to follow your team’s rules, templates and reference files. It is a good feature, but each skill is a copy, and copies drift.

Our view is that your brand standard should live in one place. Each tool’s skill should then be a short, dated pointer back to it.

We build an AI marketer, so we have a stake in this.

What Google actually shipped

Skills can be built from scratch, started from a template, or written as SKILL.md files in Workspace Studio. Gemini can then apply a skill on its own when it seems relevant, or you can call one with an @mention.

Skills can be invoked in Gmail, Docs, Slides, Drive and Chat. They are not yet available in Sheets or Meet, and they support English only. Rollout started on 9 November for Rapid Release domains and starts on 30 November for Scheduled Release domains, and it is gradual.

Admins can switch skills off at domain, organisational unit or group level. They can also audit skill activity through Workspace Studio log events in the Admin console.

Google’s September launch post said teams can start from a template for brand-consistent emails and files. So brand rules are an intended use, not a stretch.

Sharing a skill makes a copy

Here is the detail that matters. When you share a skill from Workspace Studio, each recipient gets their own independent copy. Later edits to your original do not change copies already saved.

Workspace skills also do not sync with skills in the Gemini app. Because both use the SKILL.md format, Google says you can copy the instructions across by hand.

This is a sensible design. Independent copies let people adapt a skill to their own work without breaking anyone else’s.

For a brand standard, it means a change to your tone rules has to be made in every copy. Someone has to remember to do that.

Skills are one more place brand rules live

Most teams already keep brand rules in several places. There is the PDF guideline, a wiki page, a prompt saved in someone’s notes, and a brief sent to a freelancer. There may also be a custom assistant that someone built earlier.

That is our own observation, not survey data. Each new tool adds another home.

The rules start identical, then someone fixes a phrase in one copy late on a Friday. Weeks later the Gmail skill and the Slides skill can disagree about whether you say “customers” or “members”.

Nobody did anything wrong. That is simply how copies behave.

One home, many pointers

You can fix this without buying anything. Treat the skills as short derivatives of one canonical standard.

  1. List every place your brand rules live today: documents, saved prompts, skills, custom assistants and agency briefs.
  2. Pick one canonical document. Give it a named owner and a last-updated date at the top.
  3. Write each rule with a one-line reason. A tool that knows why can handle a case the rule did not cover.
  4. Give each tool only what it needs. The email skill gets the email tone rules, the slides skill gets the layout and wording rules, and each one carries the canonical date.
  5. When the canonical document changes, update every copy the same day and note it in a change log.
  6. Once a quarter, give the same brief to each tool and compare the results side by side. Drift shows up quickly when the outputs sit next to each other.

The canonical document does not need to be fancy. One page is enough: voice rules, phrases to avoid, claims you can and cannot make, and three example sentences. That is easier to copy accurately than a forty-page PDF.

Keep a person in the approval step throughout. A shared standard reduces drift, but it does not replace a reviewer who can say no.

How Mavic approaches it

In Mavic, the brand standard is the Brand DNA saved for each brand workspace. Mavic reads it on every generation, and the brand’s facts are passed to the agents on each call. We say Mavic always works from your brand, rather than that it remembers it.

So there is one place to change a rule, and the next piece of work follows it. A team running several brands keeps a separate Brand DNA for each. With Tandem, one brief is split across specialist agents, and each of them works from the same saved Brand DNA.

There are limits. The ban list is a strong nudge, not a hard filter, so words can still slip through, especially in long documents.

Brand DNA also only governs work made in Mavic. Anything drafted in Gmail or Docs still follows whatever skill sits there, which is why the steps above still apply. Nothing in Mavic goes live without your approval.

Where copied skills are fine

Not every skill needs a canonical parent. A personal skill for summarising long email threads, or a small team’s skill for meeting notes, can live and drift without harm.

Ask two colleagues what your brand sounds like. If each can point to a different skill as proof, you have a drift problem. Fix it before the next tool arrives.

Sources

×

Request a Demo

Tell us about your business so we can tailor your demo experience.







    We'll review your request and send you a personalised demo or recording within 24 hours.

    ×

    Get AI Tool Evaluation Toolkit

    Enter your email to unlock this free resource. No spam - just the download link.


      We respect your privacy. Unsubscribe anytime.

      Top