> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/session-b-workshops/short-puzzles-big-thinking.md).

# Short Puzzles, Big Thinking

An introduction to Bebras

The Bebras challenge is made up of short, puzzle-style tasks that build computational thinking. It’s open to all young people aged 6 to 19.

In this hands-on session, you’ll:

* Try tasks for yourself to see what your learners will experience
* Find out how to take part in the Bebras challenge and where to find free resources
* Discover ideas for using tasks in your classroom or club

You’ll leave knowing what Bebras tasks look like, how to take part in the challenge, and how to use the tasks with your learners.

{% hint style="info" icon="school" %}
**Harriet Page**

Learning Manager

Raspberry Pi Foundation
{% 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 by asking a question.

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

```
GET https://upskilling.stacs.scot/conference26/session-b-workshops/short-puzzles-big-thinking.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.