> ## Documentation Index
> Fetch the complete documentation index at: https://docs.concord.ad/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Skills

> Skills are a new form of memory in Concord: short, named units that capture how your team works.

## What Skills are

Skills are a new form of memory for Concord. Each Skill is a short, named unit that captures one of your team's recurring rules: how you label brands, the way you set up a TrueView line item, your QA checklist before launch, the columns you always want in a report.

Save them once and Concord pulls in the right ones the moment they become relevant, so you stop typing the same thing in every chat.

Unlike a single opaque memory blob, every Skill stands on its own. You can read it, edit it, scope it, or turn it off without touching the rest.

## How Skills work

<Steps>
  <Step title="A Skill is created">
    Either you write one in Settings, Skills, or Concord proposes one when it spots a recurring preference in your chats.
  </Step>

  <Step title="Concord loads the right ones on demand">
    When you start a conversation, Concord picks the Skills relevant to the brand and the question. Workspace Skills always apply; brand Skills only kick in for that brand.
  </Step>

  <Step title="The conversation already knows the rule">
    No need to repeat it in every chat. Edit or disable the Skill any time and the change is live in the next message.
  </Step>
</Steps>

## Workspace-wide or brand-scoped

Each Skill applies to either your whole workspace or a chosen set of brands.

**Workspace-wide.** Concord uses the Skill on every brand and every chat. Use this for rules that should always apply: company-wide naming conventions, governance, default report formats.

**Brand-scoped.** The Skill is only loaded when Concord is working on one of the selected brands. Useful when only some clients follow a given playbook, or when a brand has unique constraints.

When a brand-scoped Skill conflicts with a workspace one, the brand Skill wins.

## Built-in Skills

Concord ships a small set of built-in Skills that load automatically, so platform-specific behavior is correct out of the box.

| Skill           | What it covers                                                                       |
| --------------- | ------------------------------------------------------------------------------------ |
| DV360 specifics | Mandatory fields, bid strategies, TrueView and Demand Gen rules, current limitations |
| Meta specifics  | ODAX objectives, Advantage+ levers, allowed optimization goals, creative scenarios   |
| Skill creation  | How Concord writes new Skills when you ask it to remember something                  |

You don't need to recreate these. They are read-only and always on.

## Skills vs instructions

Workspace and brand [instructions](/features/instructions/workspace-instructions) are always part of the conversation. Skills are loaded on demand, so you can keep many of them without bloating every chat.

Use **instructions** for the few rules that should always apply, no matter what the conversation is about.

Use **Skills** for everything else: playbooks, checklists, platform-specific habits, anything you reach for in only some situations.

<Tip>
  Treat Skills like a teammate's playbook. The more focused each Skill is, the easier it is for Concord to pick the right one at the right moment.
</Tip>