> 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/ai-literacy-with-micro-bit-1.md).
# AI Literacy with micro:bit (1)
Exploring AI literacy through physical computing with the micro:bit
Explore what AI literacy means in practice through hands-on physical computing with the micro:bit. This session introduces practical ways to help learners understand, question and experiment with AI concepts by connecting them to real-world, tangible computing experiences.
{% hint style="warning" %}
**This is a 2-part session.**
* Please consider also attending part 2 in session C
{% endhint %}
{% hint style="info" icon="school" %}
**Lorna Gibson**
Dr Lorna Gibson is Head of Professional Development at the Micro:bit Educational Foundation.
In this role, she leads initiatives to support teachers in building their skills and confidence with micro:bit—designing and delivering training and professional learning that helps educators bring interactive computing, coding, digital creativity and AI literacy into the classroom.
Lorna is part of the Foundation’s Education Team, working globally to enable more equitable access to technology-rich learning.
{% 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/ai-literacy-with-micro-bit-1.md?ask=&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.