> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/agents/skills.md).

# Skills

Create reusable instructions that teach Agents how to perform repeatable work consistently across your account or workspace.

Skills let you define reusable instructions for Agents instead of repeating the same guidance in every prompt. A skill can describe a process, methodology, output standard, or other set of instructions that you want Agents to follow when performing relevant work.

See also [Agent Projects](https://docs.countercyclical.io/agents/projects) and [Context](https://docs.countercyclical.io/agents/context).

Skills can exist at either the **account** or **workspace** level. Account skills are available to you across workspaces, while workspace skills are shared with Agents operating in that workspace.

### Accessing Skills

You can access skills directly from the Agents composer or manage them from Settings.

From the **Agents** page, open the **Agent Skills** menu to see the skills currently available to you. The menu separates skills into two scopes:

* **Account skills** — reusable skills associated with your account.
* **Workspace skills** — reusable skills shared across the current workspace.

If no skills exist in a scope, the menu displays an empty state.

Select **Manage Account Skills** or **Manage Workspace Skills** to open the corresponding Skills settings page.

### Account and Workspace Skills

The two skill scopes determine where a skill is available and who it is intended to serve.

**Account skills** belong to your account. Use them for personal methodologies, preferences, recurring workflows, or instructions you want available when using Agents across your workspaces.

**Workspace skills** belong to the workspace. Use them for shared processes, research standards, investment methodologies, formatting conventions, or other instructions that should be available to Agents working with members of that workspace.

Keeping these scopes separate lets you maintain personal reusable instructions without mixing them with organization-wide operating standards.

### Managing Skills

To manage skills, go to [**Settings › Account › Agents › Skills**](https://dashboard.countercyclical.io/settings/account/agents/skills) or [**Settings › Workspace › Agents › Skills**](https://dashboard.countercyclical.io/settings/workspace/agents/skills).

The Skills page displays the reusable skills available in that scope. You can search existing skills or select **Create Skill** to add a new one.

If no skills have been created, the page displays an empty state prompting you to create reusable instructions for Agents.

### Creating a Skill

Select **Create Skill** to open the skill editor.

Each skill contains the following fields:

| Field           | Description                                                                          |
| --------------- | ------------------------------------------------------------------------------------ |
| **Name**        | The human-readable name shown when browsing and selecting the skill.                 |
| **Key**         | The skill's unique identifier. The key cannot be changed after the skill is created. |
| **Description** | A brief explanation of what the skill does.                                          |
| **Content**     | The actual instructions Agents should follow when using the skill.                   |

The description is optional. The content field supports Markdown, so instructions can use headings, lists, examples, and other structure when useful.

When creating a key, use something concise and recognizable. Because the key becomes the skill's permanent identifier, choose a name that will remain meaningful even if you later refine the skill's description or instructions.

### Composing Skill Instructions

A skill works best when its content describes the behavior you want rather than only the outcome.

For example, a due-diligence skill might define which sources should be consulted, how conflicting evidence should be handled, what calculations should be performed, and how conclusions should be presented. A memo-writing skill might instead specify required sections, terminology, citation expectations, and formatting conventions.

For more reliable results, make the instructions explicit about important requirements while leaving the Agent discretion where judgment is useful.

### Referencing Other Skills

Skill content supports references to other skills using:

`/<key>`

This lets one skill build on reusable instructions already defined elsewhere rather than duplicating them.

For example, a broader investment-review skill could reference separate skills covering source standards, valuation methodology, or memo formatting.

When composing skills this way, keep each underlying skill focused on a stable responsibility. This makes the instruction set easier to maintain and reuse.

### Using Skills with Agents

Skills available to the current scope appear in the **Agent Skills** menu in the Agents composer.

You can use skills to provide established procedures or context for a particular Agent request. This is useful when the same operating standard applies across many different tasks: instead of restating the procedure each time, use the relevant skill and focus your prompt on the work you want completed.

The menu distinguishes account and workspace skills so you can see where each instruction set comes from.

### Choosing the Right Scope

Use an **account skill** when the instruction primarily reflects how you personally want Agents to work. Use a **workspace skill** when the instruction represents a shared organizational process or should be consistently available to other members of the workspace.

For example, personal writing preferences are generally better suited to an account skill, while a firm's investment-committee memo standard is generally better suited to a workspace skill.

### Updating Skills

As your processes change, update the corresponding skill rather than reproducing revised instructions in individual Agent prompts.

Changes to a skill affect how that reusable instruction is applied going forward. When making material changes to a widely used workspace skill, review the full instruction set to ensure older assumptions or conflicting requirements have not been left behind.

### Deleting Skills

Delete skills that are no longer part of your workflow or that have been replaced by another reusable instruction set.

{% hint style="warning" %}
**Check References Before Deleting a Skill**

Before deleting a skill, consider whether other skills reference its key. Because skills can reference one another, removing a dependency may affect instructions that rely on it.
{% endhint %}

### Best Practices

Keep skills focused enough to be reusable. A single skill that attempts to govern every aspect of an Agent's behavior is generally harder to maintain than several skills with clear responsibilities.

Use stable, descriptive keys; put durable procedures in skill content rather than individual prompts; separate personal standards from workspace-wide standards using the appropriate scope; and review generated instructions before saving them.

For shared workspace skills in particular, write instructions as operating standards rather than assumptions about a single task. This makes the skill useful across a broader range of Agent work while keeping execution consistent.

#### Related Pages

{% content-ref url="/pages/eupdSSvcRiIp9s9QkHBZ" %}
[Context](https://docs.countercyclical.io/agents/context.md)
{% endcontent-ref %}

{% content-ref url="/pages/Y4cgFnb6MdXOEYWqzLwJ" %}
[Projects](https://docs.countercyclical.io/agents/projects.md)
{% endcontent-ref %}

{% content-ref url="/pages/SEBcQQoACGG4eLh49Wda" %}
[Agents Overview](https://docs.countercyclical.io/agents/agents-overview.md)
{% endcontent-ref %}
