# What is unSkript?

<figure><img src="https://img.shields.io/github/stars/unskript/Awesome-CloudOPs-Automation?color=orange&#x26;style=for-the-badge" alt=""><figcaption></figcaption></figure>

<div><figure><img src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/unskript/Awesome-CloudOps-Automation/master/.github/images/runbookShield.json&#x26;style=for-the-badge" alt=""><figcaption></figcaption></figure> <figure><img src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/unskript/Awesome-CloudOps-Automation/master/.github/images/actionShield.json&#x26;style=for-the-badge" alt=""><figcaption></figcaption></figure></div>

{% embed url="<https://www.youtube.com/watch?v=uvMVAbXWKDU>" %}

### 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](https://docs.unskript.com/unskript-documentation/healthchecks) and  [Actions](https://docs.unskript.com/unskript-documentation/actions/actions). Combine Checks to form a [Suite](https://docs.unskript.com/unskript-documentation/healthchecks/create-a-healthcheck/create-a-healthcheck-folder) and Actions into interconnected steps in a [Remediation RunBook](https://docs.unskript.com/unskript-documentation/runbooks), 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="guides/getting-started" %}
[getting-started](https://docs.unskript.com/unskript-documentation/guides/getting-started)
{% endcontent-ref %}

{% content-ref url="runbooks/xrunbooks" %}
[xrunbooks](https://docs.unskript.com/unskript-documentation/runbooks/xrunbooks)
{% endcontent-ref %}

{% content-ref url="actions/actions" %}
[actions](https://docs.unskript.com/unskript-documentation/actions/actions)
{% endcontent-ref %}

### Fundamentals: Dive a little deeper

Learn the fundamentals of unSkript to get a deeper understanding of our main features:

{% content-ref url="fundamentals/jupyter-notebooks-101" %}
[jupyter-notebooks-101](https://docs.unskript.com/unskript-documentation/fundamentals/jupyter-notebooks-101)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.unskript.com/unskript-documentation/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
