You can build a reusable brand Skill in Evo Researcher so your team produces consistent, on-brand customer outputs every time. You need administrator permissions to create and publish the Skill.
đNote: This feature is available to Advanced users on Evo Everywhere, and to all users on Evo Enterprise. It is not available to Base users on Evo Everywhere, or to users on the Standard tier. If you are unsure of your user type or tier, see understanding Evo tiers.
The communications available to Researcher depend on the Evo Comms connector configuration and your permissions.
Why create a branding Skill?
Every time a team member asks Evo Researcher to produce a customer update, report, briefing or proposal, they face the same problem: Evo Researcher does not know your organisation's brand unless you tell it. Without a branding Skill, that means repeating the same instructions in every prompt (logo placement, approved colours, tone of voice, terminology) and hoping the output is consistent each time.
A branding Skill solves this by encoding those rules once and making them reusable across every project and every user who has access to the Skill.
What this means in practice for your team:
Faster outputs. Users stop writing brand instructions from scratch. They ask for the document they need, and the Skill handles the style.
More consistent customer-facing material. Everyone working from the same Skill produces outputs that look and sound like they came from the same organisation, not from whoever happened to write the longest prompt.
Lower barrier for less experienced users. A colleague who is not a designer or a confident prompt writer can still produce a professional, on-brand output. The Skill carries the expertise.
Fewer review cycles. When brand rules are built into the Skill rather than applied manually at the end, outputs arrive closer to ready. Less time is spent correcting colours, fonts and terminology after the fact.
A shared standard. When a Skill is published at your organisation level, it becomes the agreed starting point for customer-facing work. Brand decisions are made once, not relitigated in every project.
A Skill contains the reusable instructions. Keep the brand guide, logos and other reference assets separately in a project or Data Space, then tell Researcher which approved sources to use.
Before you start
You will need:
Access to Evo Researcher with administrator permissions. You will need admin access to create and manage Skills.
A Researcher project in which you can test the Skill.
An approved brand guide or style reference.
Approved logo files, if the output needs a logo.
Your organisation's colours, fonts and tone-of-voice guidance.
One example of a good, on-brand output.
Step 1: Prepare the reference material
Collect the smallest useful set of approved references. A good starting set is:
The brand guide or a short brand summary.
The approved logo file.
The colour and typography guidance.
One example of a finished, on-brand output.
Any terminology or tone-of-voice guidance.
Upload the documents or assets to the project you are using, or place material needed across multiple projects in a suitable Data Space.
Step 2: Write the Skill instructions
You write the instructions directly, so there is no need to ask Researcher to draft them. Copy the example below and replace the bracketed placeholders with your own brand details.
Purpose: Ensure every output produced in this project reflects [Your Organisation] brand standards. Approved sources: Use only the brand references attached to this project. Do not invent or assume any brand detail. Brand rules: - Primary colour: [hex code, e.g. #003366] - Secondary colour: [hex code] - Logo: use the approved logo file attached to this project; place top-left on every page - Font: [font name], weights [e.g. 400 and 700] only - Do not use gradients, drop shadows, or unapproved colours Content rules: - Tone: [e.g. professional, plain-English, no jargon] - Always refer to the company as [Your Organisation], never by abbreviation unless approved - Do not include customer names, case studies, or claims not present in the approved references Output rules: - Default format: [HTML/PowerPoint/Word] - Include a header with the logo and a footer with [e.g. company name and page number] - Ensure sufficient colour contrast for accessibility Hard stops: - If a required brand asset is missing, stop and ask the user before proceeding - If two references conflict, flag the conflict and ask for a decision â do not guess - Never invent a logo, colour, font, statistic, or customer example Quality check before returning any output: - Logo present and correctly placed - Approved colours used throughout - Tone consistent with brand guidelines - No unapproved claims or invented content
Keep the instructions concise. Remove anything project-specific (a single customer name, a one-off deadline) before saving.
Step 3: Create the Skill
This creates an org-wide Skill, visible to everyone in your organisation. You need org admin access to complete this step.
Open Evo Researcher, then click Admin.
Under Management, click Skills.
Click + New skill.
Complete the following fields:
Name: What users see when they pick a Skill, for example '[Org Name] Brand Style'.
Description: One sentence explaining what attaching this Skill does, for example Applies approved visual, content and tone rules to customer-facing HTML outputs.
Instructions: Paste the instruction block you reviewed in Step 2.
Files (optional): Attach any supporting brand documents the AI may need to read on demand.
Click Publish.
Once published, any user in your organisation will see the Skill in the Attach skill list when configuring a project.
Step 4: Add the Skill to a project
Create a simple project instruction that tells Researcher when to use the Skill.
Open the project where you want to use it.
Click Instructions.
Add and save an instruction similar to this:
Use the "Customer Brand Style" Skill whenever I ask for customer-facing outputs, briefings, reports, proposals or adoption updates. Use only the approved brand references available in this project. If a required asset or brand rule is missing, ask before creating the output.
Under Skills, click Attach skill.
Select your newly created brand Skill.
The project instruction provides the trigger and context. The Skill provides the reusable brand rules.
Step 5: Test it with a real use case
Start with a small output that is easy to review. For example:
Create a one-page HTML customer update about [topic]. Use the "Customer Brand Style" Skill and the approved brand references in this project. Use the approved logo only. Include: - a clear title - a short executive summary - three key points - a next-steps section - a contact or call-to-action section Do not invent customer results, dates or product claims. Before returning the output, check the branding, terminology, readability and accessibility.
Review the result against the source material. Check:
Is the correct logo used, in an appropriate position and size?
Are the approved colours and fonts being used?
Does the tone sound like your organisation?
Are product names and other terms correct?
Is the layout readable on screen?
Has Researcher avoided unsupported claims and invented assets?
Does the output work for the intended customer audience?
Then test the Skill with a second output, such as a customer briefing or account review summary. A Skill is ready for wider use only when it works consistently across more than one format or scenario.
Step 6: Refine the Skill
If the same issue appears more than once, update the Skill rather than adding another long prompt to every project.
Useful refinements include:
Replacing vague instructions such as 'make it professional' with observable rules.
Adding an example of the desired heading or layout.
Stating which source takes priority when references conflict.
Adding a hard stop for missing or unapproved assets.
Narrowing the Skill to a smaller set of outputs.
Adding a final quality checklist.
Keep one-off customer or project requirements in the project instructions. Keep repeatable organisation-wide behaviour in the Skill.
Creating a shared Skill
Users can create personal Skills for their own work. An organisation-wide Skill requires your organisation administrator to create and publish it for wider use.
Before publishing a shared Skill, agree:
Who owns the brand rules.
Which references are authoritative.
Who can request changes.
How often the Skill will be reviewed.
Which output types it supports.
â ď¸Important: Do not publish a Skill based on an unapproved draft brand guide or a single person's preferences.
A simple Skill structure
Use this structure when reviewing or writing the final instructions:
Purpose: Explain what the Skill creates and who it is for.
Approved sources: Name the brand guide, asset location and examples Researcher should use.
Brand rules: Set out the approved logo, colours, fonts, layout, imagery and accessibility rules.
Content rules: Set out tone, spelling, terminology, headings and claims.
Output rules: State the supported output types and required sections.
Hard stops: List what Researcher must not invent or do without clarification.
Quality check: List the checks Researcher must complete before returning the result.