> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/skills/running-skills-on-demand-vs-scheduled.md).

# Running Skills (on-demand vs scheduled)

**On-demand:**

* Click \[Run] on a skill in the sidebar
* Or ask in chat: "Run simulation on 200 tickets from last 60 days"

**Scheduled:**

* Set up via Automations > Scheduled jobs
* Options: Daily / Weekly / Monthly at a specific time (30-minute increments)
* Example: "Run simulation every Monday at 9am and email me a summary"
* Schedules can also be created via chat

**Skill outputs** are saved to OUTPUT > Skills > \[Skill Name] > \[Timestamp]. Each run creates a timestamped folder with AI-named markdown files.

{% hint style="info" %}
You can use the instructions to have your agent use a skill as part of an existing workflow! For example, at the end of every conversation run the "Knowledge Gap" skill and send the report to a Slack channel. 
{% endhint %}


---

# 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.eesel.ai/skills/running-skills-on-demand-vs-scheduled.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.