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

# Skills

> Install and use Propel skills (beta) for Codex, Claude Code, and Cursor.

<Note>
  Skills are in beta. We're actively improving setup and review automations, so you may see some changes along the way. Feedback welcome!
</Note>

Use Propel skills to run reviews, fix findings, and triage pull request comments with consistent automation.

## Available skills

<table>
  <thead>
    <tr>
      <th style={{ width: "38%" }}>Skill</th>
      <th>What it does</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <code>carl</code> (Coding Agent Review Loop)
      </td>

      <td>
        Continuously runs Propel code review, fixes valid comments, and re-reviews until no comments remain.
      </td>
    </tr>

    <tr>
      <td>
        <code>propel-address-pr-comments</code>
      </td>

      <td>Addresses Propel AI comments in a GitHub pull request review.</td>
    </tr>

    <tr>
      <td>
        <code>propel-code-review</code>
      </td>

      <td>Runs async diff-based code reviews with the Propel Review API and retrieves comments and feedback.</td>
    </tr>
  </tbody>
</table>

## Before you install skills

Set `PROPEL_API_KEY` in your environment.

Create a Review API token from [Review API Tokens](https://app.propelcode.ai/administration/settings?tab=review-api-tokens\&scopes=reviews:read,reviews:write).

```bash theme={null}
export PROPEL_API_KEY="rev_..."
```

To persist this value in your shell profile:

```bash theme={null}
# bash
echo 'export PROPEL_API_KEY="rev_..."' >> ~/.bashrc && source ~/.bashrc

# zsh
echo 'export PROPEL_API_KEY="rev_..."' >> ~/.zshrc && source ~/.zshrc
```

<Note>
  If you skip this step, the skill may prompt you to generate a token when it runs.
</Note>

## Install by coding agent

<Tabs>
  <Tab title="Codex">
    Run this command in Codex:

    ```text theme={null}
    $skill-installer propel-gtm/propel-code-skills
    ```
  </Tab>

  <Tab title="Claude Code">
    Run these commands in Claude Code:

    ```text theme={null}
    /plugin marketplace add propel-gtm/propel-code-skills
    /plugin install propel-code-review@propel-code-skills
    ```
  </Tab>

  <Tab title="Cursor">
    Cursor supports skills through folders that contain `SKILL.md`.

    Project-scoped install (recommended):

    ```bash theme={null}
    mkdir -p .cursor/skills
    cp -R plugins/propel-code-review/skills/propel-code-review .cursor/skills/
    cp -R plugins/carl/skills/carl .cursor/skills/
    cp -R plugins/propel-code-review/skills/propel-address-pr-comments .cursor/skills/
    ```

    User-scoped install:

    ```bash theme={null}
    mkdir -p ~/.cursor/skills
    cp -R /path/to/propel-code-skills/plugins/propel-code-review/skills/propel-code-review ~/.cursor/skills/
    cp -R /path/to/propel-code-skills/plugins/carl/skills/carl ~/.cursor/skills/
    cp -R /path/to/propel-code-skills/plugins/propel-code-review/skills/propel-address-pr-comments ~/.cursor/skills/
    ```
  </Tab>
</Tabs>

## Prompt your agent to use the skills

For a diff review automation:

```text theme={null}
Use `propel-code-review` to review the diff from base branch to HEAD, then report any findings before final output.
```

For an automatic review and fix loop:

```text theme={null}
Use `carl` to repeatedly run `propel-code-review` and address valid comments until none remain.
```

For PR-specific finding triage:

```text theme={null}
Use `propel-address-pr-comments` to find the open PR for the current branch, fetch Propel findings, ask which comments to address, and apply fixes for selected findings.
```

## Next steps

1. Open [Commands](/features/commands) to run your first review commands.
2. Open [Knowledge base](/features/knowledge-base) to add reusable team rules.