> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/skills.md).

# Skills

- [What skills are](https://docs.kula.digital/skills/skills.md): Saved, repeatable playbooks the AI can run on your studio — the ones we ship, and the ones you build yourself.
- [The built-in library](https://docs.kula.digital/skills/library.md): The free skills we ship with every studio, and how to run one.
- [Studio Ignition](https://docs.kula.digital/skills/studio-ignition.md): The paid, staged diagnostic add-on from the Skills marketplace — add it once and your studio unlocks the full runbook plus the skill set that runs it against your data.
- [Build your own & share with your team](https://docs.kula.digital/skills/build-your-own.md): Turn the way you analyse your studio into a reusable skill, then publish it so your whole team's AI runs it the same way.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kula.digital/skills.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
