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

# Skills

> Author reusable slash commands that the agent can run on demand

## Overview

A **Skill** is a reusable prompt or automation you author in-app and invoke as a slash command. Skills let you capture project-specific workflows, conventions, and repeated instructions so the agent can run them on demand instead of you re-typing them.

Manage Skills in **Settings → Extensions → Skills**.

## What You Can Configure

| Field         | Description                                        |
| ------------- | -------------------------------------------------- |
| Name          | Display name for the skill                         |
| Description   | One-line summary                                   |
| Slash command | The trigger that runs it (e.g. `/myskill`)         |
| Argument hint | Optional placeholder describing expected arguments |
| Enabled       | Toggle the skill on or off                         |

## Sources

Skills are grouped by where they come from:

<CardGroup cols={3}>
  <Card title="Personal" icon="user">
    Skills you create for your own use across projects.
  </Card>

  <Card title="Project" icon="folder">
    Skills scoped to the current project.
  </Card>

  <Card title="Agents" icon="robot">
    Skills associated with agents.
  </Card>
</CardGroup>

## Using a Skill

<Steps>
  <Step title="Create the skill">
    In **Settings → Extensions → Skills**, give it a name, description, and slash command.
  </Step>

  <Step title="Enable it">
    Toggle the skill on so it appears in the composer.
  </Step>

  <Step title="Invoke it">
    Type its slash command in the composer, with arguments if it expects them.
  </Step>
</Steps>

<Tip>
  Skills pair well with the built-in triggers ([`/modernize`, `/analyze`](/features/slash-commands) and the `@tester` / `@documenter` generators) — Skills let you add your own slash commands on top.
</Tip>