← Back to the Brail website

What is skills sync?

Part of: RunLast updated 6 November 2026

Skills sync keeps the same brand skills, from voice rules to sales-deck instructions, current in every tool that runs them, such as Claude, ChatGPT, Lovable and coding agents, from one versioned source.

Also called: sharing skills across tools, team skills sync.

Why it matters.

Skills are folders of instructions an agent loads when a task matches, built on the open Agent Skills format. As of November 2026, they're installed per tool and often per person, so a team quickly ends up with several versions of the same sales-deck skill on different laptops.

When a skill changes, every installed copy has to change with it, and nobody can easily see which copy each person is running. Keeping skills current from one versioned source, with a history of each change, means a fix made once reaches everyone, a bad change can be undone, and an old copy doesn't quietly keep producing the old result.

Example.

BeforeA team lead improves the LinkedIn skill and shares the new folder in Slack. Half the team installs it; the others keep using the version from two months ago.
AfterThe skill is updated once and approved. Every person's Claude, ChatGPT and coding agent runs the current version, the previous one can be restored if needed, and anyone still on an old copy is flagged.

How Brail handles it.

Brail keeps every skill your team runs, and the .md files inside it, as versioned files with a history and approval for changes, and keeps each one current in Claude, ChatGPT, Gemini, Lovable and coding agents, flagging any copy that falls behind. In Brail, playbooks are delivered as skills, with the shell, examples, assets and checks attached.

Questions people ask.

How do I share Claude skills with my team?
You can share the skill folder and have everyone install it, or upload it once for your organisation where the plan allows. The hard part is keeping everyone's copy current after the first change. See how to keep context and skills in sync across AI tools.
Do skills work outside Claude?
Agent Skills is an open format, and a growing number of agents and tools read it. Check each tool's documentation for what it supports.
Are skills the same as marketing playbooks?
A skill is the file format; a marketing playbook is what goes in it for one situation, such as a sales deck or a LinkedIn post: the instructions, shell, examples, assets and checks.
  • Sync brand across AI tools: You keep context and skills in sync across AI tools by keeping one versioned source, with the brand and its production context, examples of good work, playbooks delivered as skills, the brand kit and the design system, and connecting every tool to it instead of keeping a separate copy in each.
  • SKILL.md: SKILL.md is the file at the heart of an Agent Skill: a Markdown file with a name, a description of when to use it and instructions, which an agent loads only when a task matches.
  • Brand skills: Brand skills are instructions packaged for AI agents, usually as SKILL.md files, that teach an agent how to apply a brand.
  • Marketing playbook: A marketing playbook is a set of instructions for one situation, such as a sales deck, a LinkedIn post or a customer report.
  • Brand versioning: Brand versioning is giving every brand file, from messaging and pricing to logos and skills, a history, an owner, a draft or approved status and sign-off for changes, so agents only use approved versions.
  • Context sync: Context sync keeps the context every agent reads, such as positioning, audiences, messaging, proof points and pricing, on one current, versioned source across every tool and .md file, instead of separate copies pasted into each.
  • Brand sync: Brand sync keeps every tool and agent on the same, current version of a brand.

Read more.

Sources.