> For the complete documentation index, see [llms.txt](https://tutorials.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.clause9.com/clause9-campus-exercises/exercises.md).

# Exercises

## Practice makes perfect!

That's why we have created some exercises to practice your Clause9 skills. Each exercise focuses on a specific topic. Some of them build further on the documents you automated in the course of the tutorial series; others will require you to create new clauses. You can pick and choose the exercises depending on which topic you would like to practice.

First step is to create a **new document** ‘Clause9 Campus Exercises’. All the exercises that don’t build further on the Consultancy Agreement, need to be added to this document.

Finished the [**Basic** Clause Author Tutorial](/basic/getting-started.md)? Complete module **1 - 2 - 3**.

Finished the [**Intermediate** Clause Author Tutorial](/intermediate/getting-started.md)? Complete module **4 - 5 - 6 - 7**.

{% hint style="info" %}
In this type of box, you will find a link to a specific topic on the help page. It may also contain some background information helping you to complete the exercise.
{% endhint %}

{% hint style="success" %}
This type of box contains useful tips when completing the exercises.
{% endhint %}

{% hint style="danger" %}
In this type of box, we want to point out possible issues you might face and give explanation on how to overcome them.
{% endhint %}

> In these quote boxes you will find the clause content that needs to be added in Clause9.

## Struggling with an exercise?

You can always check our [help page](https://help.clause9.com/). If you cannot find an answer, we invite you to check the [discussion forum](https://discuss.clausebase.com) to post a question or view questions from other users.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tutorials.clause9.com/clause9-campus-exercises/exercises.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
