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

# Skills

> Extend the agent with domain-specific expertise using reusable knowledge packages that follow the agentskills.io specification.

export const Availability = ({tags = []}) => {
  const tagColor = {
    invite: "purple",
    beta: "gray",
    "private-preview": "purple",
    vscode: "blue",
    jetbrains: "orange",
    vim: "gray",
    neovim: "gray",
    cli: "green"
  };
  return <div className="flex items-center space-x-2 border-b pb-4 border-gray-200 dark:border-white/10">
      <span className="text-sm font-medium">Availability</span>
      {tags.map(tag => <Badge key={tag} size="sm" color={tagColor[tag] || "gray"}>
          {tag}
        </Badge>)}
    </div>;
};

<Availability tags={["jetbrains", "beta"]} />

## About Skills

Skills are reusable knowledge packages that extend the agent with domain-specific expertise — deployment guides, debugging playbooks, framework best practices, and more. Each skill is a self-contained `SKILL.md` file that provides specialized instructions the agent can draw on during conversations.

Skills follow the [agentskills.io](https://agentskills.io) specification, ensuring compatibility across AI tools.

<Note>
  Skills are available as a Public Beta opt-in from the Settings page in JetBrains IDEs 0.428.8+. They are also being rolled out server-side for Community (Vanguard) tier users.
</Note>

## Creating a Skill

Each skill lives in its own named directory containing a `SKILL.md` file:

```
.augment/skills/
  ├── python-testing/
  │   └── SKILL.md
  ├── api-design/
  │   └── SKILL.md
  └── deploy-guide/
      └── SKILL.md
```

### SKILL.md Format

Each `SKILL.md` file must include YAML frontmatter with a `name` and `description`, followed by markdown content with instructions:

```markdown theme={null}
---
name: deploy-guide
description: Step-by-step deployment procedures for our production infrastructure
---

# Deployment Guide

## Pre-deployment Checklist
1. Run all tests with `npm test`
2. Verify environment variables are set
3. Check database migrations are up to date

## Deploying to Production
...
```

### Frontmatter Fields

| Field         | Description                            | Requirements                                                                        |
| :------------ | :------------------------------------- | :---------------------------------------------------------------------------------- |
| `name`        | Skill identifier                       | 1–64 characters, lowercase alphanumeric and hyphens only, must match directory name |
| `description` | What the skill does and when to use it | 1–1024 characters                                                                   |

### Skill Name Requirements

Skill names must:

* Be 1–64 characters long
* Use only lowercase letters, numbers, and hyphens
* Not start or end with a hyphen
* Not contain consecutive hyphens
* Match the directory name containing the `SKILL.md` file

**Valid names**: `python-testing`, `api-design`, `deploy-guide`
**Invalid names**: `Python-Testing`, `api_design`, `-deploy`, `my--skill`

## Skill Modes

Skills can operate in one of three modes:

| Mode         | Behavior                                       |
| :----------- | :--------------------------------------------- |
| **Auto**     | Injected into every conversation automatically |
| **Manual**   | Available on demand via the `/` slash menu     |
| **Disabled** | Loaded but not active                          |

Use **Auto** for skills you always want available (e.g., project conventions). Use **Manual** for specialized skills you only need occasionally (e.g., deployment playbooks). Set skills to **Disabled** to temporarily deactivate them without removing the files.

## Skill Locations

Skills are discovered from multiple locations in order of precedence:

| Location                       | Scope     | Description                                      |
| :----------------------------- | :-------- | :----------------------------------------------- |
| `~/.augment/skills/`           | User      | Available in all workspaces (highest precedence) |
| `<workspace>/.augment/skills/` | Workspace | Project-specific, can be version controlled      |
| `~/.claude/skills/`            | User      | Compatible with Claude Code                      |
| `<workspace>/.claude/skills/`  | Workspace | Compatible with Claude Code                      |
| `~/.agents/skills/`            | User      | Industry-standard location                       |
| `<workspace>/.agents/skills/`  | Workspace | Industry-standard location                       |

When multiple skills with the same name exist in different locations, the skill from the higher-precedence location is used.

## Getting Started

<Steps>
  <Step title="Create the skills directory">
    ```bash theme={null}
    mkdir -p .augment/skills/my-skill
    ```
  </Step>

  <Step title="Create the SKILL.md file">
    Create `.augment/skills/my-skill/SKILL.md`:

    ```markdown theme={null}
    ---
    name: my-skill
    description: Custom skill for my project workflow
    ---

    # My Custom Skill

    Add your domain-specific guidance, examples, and instructions here.
    ```
  </Step>

  <Step title="Use the skill">
    The skill will be discovered automatically. Use the `/` slash menu to invoke manual skills, or set the mode to Auto for always-on skills.
  </Step>
</Steps>

## Best Practices

1. **Focus each skill on a single domain** — keep skills modular and specific
2. **Include concrete examples** — provide code samples and commands
3. **Write clear descriptions** — help the agent understand when to apply each skill
4. **Version control workspace skills** — commit `.augment/skills/` to share with your team
5. **Use Auto sparingly** — only for skills that are relevant to every conversation

## See Also

* [agentskills.io Specification](https://agentskills.io/specification) — Official skill format specification
* [Skills in Auggie CLI](/cli/skills) — Using skills with the CLI