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

# Skills

> Teach Pluvo how your organization works, so every analysis follows your definitions, conventions, and house rules.

## What it does

A skill is a standing instruction for Pluvo: how a metric is calculated, what counts and what does not, a pitfall to steer around, or context about your organization to always keep in mind.

The problem it solves is repetition. Instead of explaining in every conversation that revenue means recognized revenue net of refunds, or that intercompany accounts are excluded from rollups, you write it down once and Pluvo applies it going forward.

Skills are written by your team. Nothing runs when you save one, it becomes reference knowledge that Pluvo brings into its work.

## Writing a skill

<Steps>
  <Step title="Start a new skill">
    Open **Skills** and choose **New skill**. You get an authoring chat on the left and the skill itself on the right.
  </Step>

  <Step title="Describe what Pluvo should know">
    Tell the assistant what you want to teach it, such as a definition, a rule, or a pitfall in your data. It interviews you a question at a time and fills in a draft as you go. You can also type directly into the editor yourself.
  </Step>

  <Step title="Review what it proposes">
    When the assistant proposes wording, you see what changed and can **Accept** or **Reject** it. Nothing is written into your skill without your say.
  </Step>

  <Step title="Name it and set the scope">
    Give it a clear **Name**, then choose when Pluvo should use it. **Optional** means it is brought in when the question calls for it. **Required for everyone** means it is applied to every analysis your organization runs.
  </Step>

  <Step title="Activate it">
    Choose **Activate** to put it to work. Drafts are saved as you type but are not used until they are active.
  </Step>
</Steps>

<Tip>
  A good skill states the rule, the pitfall, and the boundary. For example: when an analysis involves revenue, revenue means recognized revenue net of refunds and never bookings, and intercompany accounts are excluded from all rollups.
</Tip>

## Turning skills on for yourself

Optional skills have an **Applied to me** switch, and it starts off. An optional skill only affects your work once you switch it on, and even then Pluvo brings it in when it is relevant to the question.

Skills set to required for everyone show as **Required** instead, with no switch, because they always apply.

<Note>
  Use **Required for everyone** sparingly, for genuine organization-wide rules. Requiring too many skills dilutes the quality of what Pluvo produces.
</Note>

## Managing your skills

The **Skills** list shows each skill with a short excerpt, whether it is **Active** or a **Draft**, its scope, whether it is applied to you, and when it was last updated and by whom. You can search skills and filter by status or scope.

Click a skill to read it in full and adjust its settings, or use its menu to **Edit skill**, **Deactivate** or **Activate** it, or **Delete skill**. Deleting is permanent and Pluvo stops using the skill immediately.

Skills are shared across your organization, so everyone can see them. Instructions can run up to 10,000 characters, and Markdown formatting is supported.

## Skills and Library

Skills and your **Library** both make Pluvo's answers better, from opposite directions:

* **Skills** are instructions you write about how your organization works.
* **Library** is structural knowledge about your data that Pluvo proposes and you approve.

Use skills for judgment and convention, and the Library for definitions, metrics, and queries.