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

# Managing Skills

> Create, manage, and evolve Skills in Gradial — encode your team's institutional knowledge so every agent executes with consistent expertise on every task.

<Info>
  Skills must be activated for your organization. Contact your Gradial account team to get started.
</Info>

Skills are the primary way to encode your organization's institutional knowledge and make it available to every agent, on every run. Where Rules define the standards every output must meet, Skills define how your team does its best work — the processes, patterns, and expertise that make the difference between consistent and excellent.

***

## Skill Builder

Create and manage skills in the **Skills** section of the left sidebar. The Skill Builder provides a rich, document-style editor for authoring skills directly.

### Creating a skill

1. Navigate to **Skills** in the left sidebar
2. Click **New Skill**
3. Give the skill a clear, descriptive name (e.g., "Campaign Landing Page Structure" or "Product Voice & Terminology")
4. Write the skill content — describe the process, pattern, or expertise you want the agent to apply
5. Set the scope (see below)
6. Save and activate

### Writing effective skills

Skills work best when they describe *how* to do something well, not just what to avoid. Good skills read like guidance from your most experienced team member:

* Describe the approach, not just the outcome
* Include examples of what "good" looks like
* Reference specific patterns, structures, or voice guidelines your team has developed
* If a workflow has steps that matter, spell them out

<Tip>
  A good signal that guidance belongs in a Skill rather than a Rule: if you're writing something that describes *how* to do work well rather than a standard every output must meet, it belongs in a Skill.
</Tip>

***

## Scope and versioning

Every skill is scoped to control where it applies:

| Scope            | What it covers                                                                                                                                  | Who can create       |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| **Workspace**    | Applies within the specific workspace where it was created — right for team-specific processes, regional workflows, or product-line expertise   | Any workspace member |
| **Organization** | Applies to all agents across the entire organization — right for universal brand voice, company-wide process standards, or cross-team expertise | Org admin or owner   |

To promote a workspace skill to org-wide, an admin can change the scope from the skill's settings.

### Version history

Full version history is maintained for every skill. You can see what changed, when, and who made the change. If a change doesn't perform as expected, you can roll back to any previous version.

***

## Agentic skill development

Grady can build and refine skills from the work it does. As agents complete tasks, they identify patterns worth encoding as reusable skills and propose them for your review.

This means your Marketing Brain grows from real work — not just what you've thought to write down. The agent captures the judgment that's hard to articulate but easy to recognize once you see it in a well-executed task.

To review proposed skills:

1. Go to **Skills** in the left sidebar
2. Look for skills with **Proposed** status
3. Review the proposed skill content
4. Edit if needed, then **Activate** — or dismiss if it doesn't apply

***

## Best practices

**Start specific, then generalize.** Begin with skills for the tasks you run most often. Once you see patterns across tasks, generalize those into broader organizational skills.

**Name skills for what they do.** "Hero section structure for product pages" is more useful than "Page skills." Agents match skills to tasks by name and description, so specificity improves targeting.

**Iterate based on output.** When agent outputs consistently miss the mark in a specific way, that's a signal your skill needs refinement. Use the version history to track what you changed and whether it helped.

**Skills and Rules work together.** Rules set the floor — the non-negotiables. Skills build on top of them. A skill that duplicates a rule adds noise. Use skills for the expertise layer, rules for the standards layer.

***

## Related

* [Learning System →](/docs/marketing-brain/learning-system) — how the Marketing Brain works
* [Managing Rules (Legacy) →](/docs/marketing-brain/managing-rules-legacy) — if your organization used Rules before Skills