> 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/skills.md). # What skills are A **skill** is a saved, repeatable playbook the AI can run on your studio. Instead of re-typing a multi-step analysis every time, you (or anyone on your team) just ask for it by name and the AI runs the whole thing the same way every time. Think of a skill as a recipe. *"Find members at risk of leaving"* isn't one question — it's a series of steps (pull recent attendance, compare to each member's normal pattern, rank by how far they've slipped, draft the outreach). A skill bundles those steps so they run consistently and you don't have to remember them. ## Three kinds of skill * **Free built-in skills** — a curated library we ship and keep current, covering the questions most studios ask. Included with every workspace. See [The built-in library](/skills/library.md). * **Skills you build yourself** — playbooks you create for the way *your* studio works, and **share with your team** so everyone's AI runs them the same way. Listing them on the marketplace for other studios is rolling out over time. See [Build your own & share with your team](/skills/build-your-own.md). * **Skills you get from the marketplace** — paid add-ons you choose for your studio. **Studio Ignition**, our flagship staged diagnostic, is the headline one, with more added over time. See [Studio Ignition](/skills/studio-ignition.md). All three live in one place: your **Skills** page in the operator app ([app.kula.digital](https://app.kula.digital)) — a marketplace and builder where you browse what's included, add paid skills, and author your own. ## Where skills show up Skills appear inside your AI assistant. In Claude you'll find them as ready prompts you can pick, and you can always just ask for one in plain English: > *"Run the at-risk members skill for the last 30 days."* Because skills travel with your studio (not with one assistant), the same skill works whether you ask in Claude today or another assistant tomorrow — and everyone connected to your studio sees the same set. ## Why they're worth it * **Consistency.** The analysis runs the same way every time, so you're comparing like with like week to week. * **Speed.** One ask instead of ten. * **Shared know-how.** The best way you've found to look at your studio becomes something your whole team can run — it doesn't live only in your head. ## Next * [The built-in library](/skills/library.md) — what ships free, and how to run one. * [Studio Ignition](/skills/studio-ignition.md) — the paid, staged diagnostic add-on. * [Build your own & share with your team](/skills/build-your-own.md) — turn your best questions into a reusable skill. --- # 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/skills.md?ask=&goal= ``` `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.