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

# Skills

> Procedures Ordyn follows when the symptoms match.

A skill is a runbook: a set of steps Ordyn follows when an investigation matches a symptom you describe. Use them to encode how your team debugs a class of problem.

## Writing a skill

From the **Skills** page, create a skill with:

* **Title.** For example, "Redis connection pool exhausted".
* **Symptom description.** A short description of when this applies. This is what Ordyn searches against, so describe the symptom, not the fix.
* **Steps.** What to query, check, or do, in Markdown. Each step can have a title.

When an investigation's symptoms match, Ordyn follows the steps and cites what it found at each one.

## Create one from Slack

You can also ask Ordyn in Slack to write or change a skill. It merges your request into the existing steps and confirms what changed.

```text theme={null}
@Ordyn add a skill for Redis pool exhaustion: check connection count against max clients, then look for a deploy in the last hour
@Ordyn update the checkout latency skill to check the payments provider status page first
```

## What to put in a skill

* The metric or log query that confirms the diagnosis.
* Which dashboard or service to look at first.
* Known false positives and how to rule them out.
* The usual fix, and when not to apply it.

Skills are searchable from the page. Ordyn also builds up runbooks from investigations that reached a verified resolution, so common problems get faster over time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.