Skip to main content
A Brand Skill is a portable folder of instructions, references, and assets for one brand. It lets another agent or application work from the brand that lives in Bloom instead of reconstructing that context for every task. SKILL.md is the entry point: it tells an agent which supporting files matter. This example was generated by Bloom from Verso Coffee, a fictional demo brand owned by Bloom. It is an unmodified production export, not a template. Its supporting filenames, content, and assets are specific to Verso; other Brand Skills will differ.
A Brand Skill contains one brand’s identity. The optional Bloom Skill teaches an agent how to use Bloom.

Download the example Brand Skill

Download the unmodified production export shown below, then extract it as one folder.

Inside the folder

This is how the Verso example is organized. Every guidance filename is shown; repeated asset filenames are collapsed to one example.
SKILL.md
references
brand-imagery.md
brand-voice.md
color-palette.md
merchandise.md
product-lineup.md
typography.md
ui-components.md
assets
manifest.json
This ZIP contains nine brand images, ten font files, and one favicon. Those counts describe Verso, not a fixed Brand Skill schema. Keep the folder together: its Markdown uses relative paths to reach the references and packaged assets.
  • SKILL.md is the entry point. It states the brand’s core rules and routes each task to the right reference files.
  • references/ separates focused guidance so an agent can load only what the task needs.
  • assets/manifest.json records the packaged image and font paths, descriptions, roles, and usage.
  • assets/images/, assets/fonts/, and assets/favicon/ keep the source material available locally.

Selected contents

These excerpts show the route an agent follows: start with SKILL.md, then load the focused reference files needed for the task. brand-voice.md is one example of that second layer.

SKILL.md

Every Brand Skill starts here. The entry point identifies the Skill, states its most important rules, and routes work to the supporting files:

references/brand-voice.md

For a writing task, SKILL.md routes the agent here for focused voice guidance. Other tasks route to other references:

Use it with an agent

A Brand Skill makes the same brand context reusable beyond Bloom. Instead of restating the brand in every prompt, extract the ZIP, give the folder to your agent, and ask for something concrete: Write
Design
Review
The agent starts with SKILL.md, then follows its routes to the guidance and assets needed for that request. For example, the email calls for voice and product guidance, while the landing page also needs imagery, color, and typography.

Use your own brand

Use a Brand Skill through either Bloom interface: