> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/labs/free-apps/colibri/colibri-visualiser.md).

# Colibri Visualiser

The Colibri Visualiser turns a Colibri exercise export into an **interactive flowchart**, so you can see the  full branching logic at a glance. Use the Visualiser to quickly check every step, choice, and ending in your self-paced exercise.

<figure><img src="/files/bI9azPEVsXec1h0SYl19" alt=""><figcaption></figcaption></figure>

### How to use it

1. In the landing page of your Editor, export your Colibri exercise as a `.txps` file

<figure><img src="/files/spWKxY9h0pFeU990Ia7P" alt=""><figcaption></figcaption></figure>

2. Upload that file to the Visualiser

<figure><img src="/files/D0Kyf1HYaJcEYJMNRPKX" alt=""><figcaption></figcaption></figure>

3. Review the generated flowchart, following each branch from start to ending
4. Go back into the Editor to fix anything the flowchart might reveal e.g. a missing connection

### What you'll see

<figure><img src="/files/zjZbRrefnijRxKH3fD9G" alt=""><figcaption></figcaption></figure>

* Every step in your exercise, connected in the order players experience them
* All choices and the branches they lead to, so you can trace exactly how a decision changes the path
* Every ending, and which routes through the exercise lead to it
* Whether the step is a question, narrative, or action type

{% content-ref url="/spaces/kKsE69Z3PsghYNFs2oFd/pages/1zsS6ECv35GAuRvPE5K0" %}
[Row Types](/colibri/getting-started/core-concepts/row-types.md)
{% endcontent-ref %}

### When to use it

The Visualiser is most useful as a check, not a building step:

* **After drafting with the Colibri Skill for Claude**, to confirm the generated branching matches what you intended before you import it
* **Partway through manual authoring**, once a scenario has grown nuanced enough that it's hard to hold the whole structure in your head
* **Before publishing**, as a final sense-check

### What next?

Once you're happy with the branching, head back to the Editor to publish and deliver the exercise.&#x20;

{% hint style="info" %}
If you're building a new exercise, use the Colibri Skill for Claude to generate:
{% endhint %}

{% content-ref url="/pages/ZlB5ho8v4TwHrhIvKCw4" %}
[Colibri Skill for Claude](/labs/free-apps/colibri/colibri-skill-for-claude.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocs.conducttr.com/labs/free-apps/colibri/colibri-visualiser.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.