Skills

What this does for you: Turns tribal knowledge into a durable, brand-specific capability. A skill teaches one module something particular about this brand, the trigger for reaching for it, and exactly what to do when it fires. Without any skills, your agents run on the default set; skills are the customisation layer on top.

What's on the screen:

• A skill library filtered by module: Creative AI, Performance AI, Consumer AI, ORM AI: a skill belongs to one of them
• Active / Inactive state per skill, so you can stage something without switching it on
• Create skill and search
• An empty state that says it plainly: "Add a skill to teach one of your modules something specific to this brand, when to reach for it, and exactly what to do."

Why it matters commercially: This is the answer to "how do you handle our category's rules?" that doesn't depend on a prompt someone remembers to paste. A BFSI tenant can encode what a compliant creative looks like; an FMCG tenant can encode per-product claim rules; an ORM tenant can encode the escalation language for a specific complaint type. It converts a services conversation into a configurable product surface, and it's a genuine differentiator against point tools.

How to position it: Skills sit inside Brand Brain deliberately. They're brand knowledge, not module settings. The same graph that holds your products, palette and disclaimers also holds the instructions for how each agent should behave for you.

Be accurate on calls: Most tenants have zero custom skills and run on the defaults. Pitch this as the vertical/customisation mechanism, not as a library of prebuilt industry packs that ships pre-populated.

When to come here: During onboarding, once the graph is built and the brand's non-obvious rules are known. Whenever a repeated correction ("it keeps forgetting X") should become permanent.