Skip to main content
Creating, editing, or deleting Skills requires the Admin role — including when a Skill is created through chat. Members can view and use the workspace’s Skills. See Roles and permissions.

Two ways Skills get written

Concord proposes

When Concord spots a recurring preference across your chats, for example a naming convention you keep correcting, it suggests a new Skill on the spot. Accept the suggestion and the next conversation already knows the rule.

You ask

Tell Concord to remember something and it writes the Skill for you.
  • “Remember to always use the format country / format / objective for line item names on this brand.”
  • “Remember to ask for confirmation before reallocating budget across IOs.”
  • “Always include CTR, viewability, and VCR in my weekly report.”
You can also create a Skill from scratch in Settings.

Creating a Skill yourself

Open Skills

Manage every Skill in your workspace.
1

Open Skills

From the sidebar, or Settings → Skills.
2

Click New skill

You are offered the starting points published to your workspace. Several of them open a conversation where Concord analyses your own account and writes the Skill for you — your naming conventions, your campaign structure, your reporting rules. Writing one by hand is one click away if none of them fits.
3

Name it and write the rules

Give the Skill a clear, topic-based name. Write the rules in plain English, the way you would explain them to a teammate.
4

Set the scope

Leave it workspace-wide, or narrow it to specific brands or advertising platforms.
5

Save

The Skill is live immediately. Concord uses it in the next chat that fits its scope.

Finding a Skill

Each row in the Skills list carries a one-line summary of what the Skill does, its scope, and when it was last updated. The search box filters the list by name and summary.

Skill examples

Naming convention:
QA checklist before launch:
Reporting defaults:
Brand-specific positioning:

Best practices

One topic per Skill. Smaller, focused Skills are easier for Concord to load only when they matter. Avoid a single mega-Skill with every rule. Be specific. Spell out exact thresholds, names, and formats. “Always use the brief budget” is clearer than “match the brief”. Cover what to do when info is missing. Tell Concord to ask, use a placeholder, or apply a default, so it doesn’t guess. Scope tightly. If a rule only applies to one brand, scope the Skill to that brand. Workspace-wide rules end up loaded everywhere. Disable rather than delete. Turning a Skill off keeps the history if you want to re-enable later.
The fastest way to bootstrap good Skills is to let Concord propose them as you work. Every accepted suggestion is one less thing to type tomorrow.