> For the complete documentation index, see [llms.txt](https://docs.unskript.com/unskript-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unskript.com/unskript-documentation/readme.md).
# What is unSkript?
Your SRE Co-Pilot: Find, Prioritize and Fix Production Issues
{% embed url="" %}
### Using unSkript
unSkript allows you to effortlessly convert existing scripts, API calls, SQL queries (and more!) into automated health checks and executable remediations using pre-built (and customizable) code blocks called [Checks](/unskript-documentation/healthchecks/what-is-a-healthcheck.md) and [Actions](/unskript-documentation/actions/actions.md). Combine Checks to form a [Suite](/unskript-documentation/healthchecks/create-a-healthcheck/create-a-healthcheck-folder.md) and Actions into interconnected steps in a [Remediation RunBook](/unskript-documentation/runbooks/xrunbook_list.md), and use the combination to increase resolve issue quickly, monitor cloud costs, and more!
unSkript xRunBooks are built in Python, and run on top of Jupyter Notebooks. With hundreds of drag & drop Actions, sometimes there is no coding required to build your automation. The unSkript framework provides teams unparalleled flexibility and usability to automate DevOps workflows. Built on top of open source - we are building an open ecosystem of Actions and xRunBooks to better serve every person in the DevOps community.
### Guides: Jump right in
With just a few steps, you can begin your RunBook automation journey:
{% content-ref url="/pages/EDEUQVEEEKYt7f0oJFAG" %}
[Getting started](/unskript-documentation/guides/getting-started.md)
{% endcontent-ref %}
{% content-ref url="/pages/mPIyRo9PXLWMt7nIwCWW" %}
[Creating RunBooks](/unskript-documentation/runbooks/xrunbooks.md)
{% endcontent-ref %}
{% content-ref url="/pages/9BhcAYuFHVaOxZIaB93c" %}
[Actions](/unskript-documentation/actions/actions.md)
{% endcontent-ref %}
### Fundamentals: Dive a little deeper
Learn the fundamentals of unSkript to get a deeper understanding of our main features:
{% content-ref url="/pages/wm0GaGSUNvE4RNyVoEQw" %}
[Jupyter Notebook 101](/unskript-documentation/fundamentals/jupyter-notebooks-101.md)
{% endcontent-ref %}
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.unskript.com/unskript-documentation/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
