> 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-d-workshops/teaching-ai-literacy.md).

# Teaching AI Literacy

Baisics, ethics and resources

Advances in AI technology are transforming society and the ways we handle data, and are likely to inform future developments in education too. In this session you will get a chance to try out some hands-on activities, including ""unplugged"" activities that don't require access to any AI tools. Topics include the basics of how AI works, ethical and sustainability issues around AI, critical thinking, and how AI can be used to support learning in different subject areas.

Find out about the high quality, cross-curricular resources for teaching with and about AI in Secondary and Upper Primary developed by Teacher Associates in the Centre for Teaching Excellence’s Digital and AI Hub and by Teachers in Residence with the Teaching Responsible AI Literacy in Schools (TRAILS.Scot) project in collaboration with Scottish Government, Education Scotland and Qualification Scotland.

{% hint style="info" icon="school" %}
**Kate Farrell and Dr Jasmeen Kanwal**

Data Education in Schools team

University of Edinburgh
{% 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-d-workshops/teaching-ai-literacy.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.