Skip to content
Heidelberg AI
Curriculum
Heidelberg AI
Desk
Search the whole curriculum
Search
‹
☰
Course index
Journeys
Learn by Level
List
Matrix
All books
Compare the outcome you want, then open a book. Filter by level and track.
Level
All levels
L01 · User
L02 · Power user
L03 · Builder
L04 · Integrator
L05 · Operator
Track
All tracks
T01 · Foundations & judgement
T17 · Structure & understand
T02 · Chat & assistants
T03 · Prompting & context
T09 · Create media
T15 · AI in research
T18 · AI for lab data
T04 · Your documents & knowledge
T05 · Automation
T06 · Build apps
T07 · Agents
T21 · Delegate desk work
T20 · AI harnesses
T08 · Write code
T19 · Share & review code
T10 · Data & analysis
T14 · Connect your tools
T11 · Run your own AI
T12 · Security, privacy & governance
T13 · Adoption & enablement
T16 · Choose tools
Sort
Curriculum order
Shortest reading time
All books
Not started
In progress
Completed
Progress is saved in this browser only.
21 books
Clear filters
Foundations & judgement
1
T01-L02
Check AI Output Before Your Team Relies on It
A corrected team deliverable (a brief, a summary, an FAQ or a caption) with a check note: source title, version and date, each material claim with its quote and location or marked unknown, and any arithmetic written out. It passes when a colleague traces three claims you didn't pick to the source without asking you.
Power user
15 min read
Chat & assistants
1
T02-L02
Set Up Projects a Colleague Can Pick Up
A project for one real team job, with instructions, source files and a dated decisions file whose master copies sit in a shared folder, and a colleague's continuation in a fresh chat. It passes when the continuation follows the current decision, not an old one, and the colleague needed nothing from you beyond the project and its folder.
Power user
15 min read
Prompting & context
1
T03-L02
Build a Context Packet Your Team Can Rerun
A context packet for one real team question: the fixed prompt, the question, the labelled sources with versions and the exact quotes the answer rests on, plus a before and after run showing which source made the difference. It passes when a colleague reruns the packet in a fresh chat and gets the same answer with the same quotes.
Power user
15 min read
Your documents & knowledge
1
T04-L02
Curate a Document Set Your Team Can Ask
A shared document set with its written rule and source register, answering three test questions (a current rule, an exception, and one the set can't answer) with citations that open to the right passage, plus one answer a colleague has used in real work. It passes when every document in the set appears in the register as current and a colleague can find the person who keeps it current.
Power user
15 min read
Automation
1
T05-L02
Put AI in the Middle of a Workflow, and Check Every Answer
A published n8n workflow with a model step, a check step, a shared review table and, if anything leaves the team, an approval step; plus a one-page note naming the reviewer and deputy, the monthly cost estimate and the spend limit. It passes when a colleague feeds in one normal item and one broken answer and the broken one lands in the review table, not in the team's list.
Power user
13 min read
Build apps
1
T06-L02
Build a Small Shared Tool From a Prompt, and Test It With a Colleague
A live Base44 app used by at least one colleague, plus a half-page note: the screens and fields, the access and permission settings as set, the colleague's test with one allowed and one refused action, the CSV export opened in a spreadsheet, and the account holder and deputy. It passes when a signed-out visitor sees no data and the colleague's test matches the note.
Power user
15 min read
Agents
1
T07-L02
Hand a Task to an Agent, and Check What It Did
The finished table or brief, plus a half-page delegation note: the card as given, the folder used, what the agent did and where you stepped in, your spot checks and the colleague's, and who signed it off. It passes when every value in the result names its source file, and the colleague's blind check of five values finds them all in the sources.
Power user
15 min read
Write code
1
T08-L02
Get a Script Your Colleague Can Rerun, Without Being a Developer
A shared Git repository with the script, a README, a known-answer test file and its expected output; it passes when a colleague, on their own computer and using only the README, gets exactly the expected output from the test file, and gets a clear refusal with a line number from one broken row.
Power user
18 min read
Create media
1
T09-L02
Keep One Look Across Your Team's Images
A shared style-kit folder (style sheet, three references with their sources, prompt frame, template, label line) plus five finished images from it, one made by a colleague; it passes when a third person can't pick out the colleague's image and finds no reference without a recorded source.
Power user
17 min read
Data & analysis
1
T10-L02
Clean a Messy Export Once, So Your Team Can Refresh It
A shared workbook that cleans the export with recorded steps, plus its rules sheet and check block, refreshed on a second month's file by a colleague; it passes when rows in equal clean rows plus flagged rows plus removed duplicates, and the colleague explains one flagged row from the workbook alone.
Power user
17 min read
Run your own AI
1
T11-L02
A Local Model Your Tools Can Call
One tool installed through Heidelberg AI Desk (Open WebUI or n8n) that gets its answers from LM Studio's local server, plus a check sheet of five examples with known answers; it passes when all five come out right with the network switched off, and your three lines name the address, the model and the task.
Power user
15 min read
Security, privacy & governance
1
T12-L02
Clean the Copy, Label the Result, Spot the Trap
A cleaned working copy for one real team task, with a method note and an AI-use note. It passes when a second reader who hasn't seen the original can't single anyone out, one result the task needs (a count, a grouping) comes out the same from the copy as from the original, and the AI-use note is still attached in the document where the result ended up.
Power user
15 min read
Adoption & enablement
1
T13-L02
Show a Colleague AI on Their Own Task, in 30 Minutes
A one-page demo record from a session with a real colleague: their task, the material and tool, the timed draft and check, the change they requested, the objection raised, and their own choice; it passes when the session took 30 minutes or less, the result was checked in front of them, and the choice is in their words.
Power user
14 min read
Connect your tools
1
T14-L02
Brief Your Team From the Shared Drive, Through a Connector
A brief built through the connector, plus a short note: the site or folder you scoped it to, the list of cited files with their dates, which of them the recipient can open, what you corrected, and how you switched the connector off. It passes when the recipient opens three cited files at random and finds each claim, and no cited file is one they can't open.
Power user
14 min read
AI in research
1
T15-L02
Record an AI Step So a Co-Author Can Rerun It
A shared folder for one AI-assisted step (input with checksum, prompt version, run record, raw outputs of at least two runs, comparison) plus a co-author's rerun from the folder alone; it passes when the co-author's rerun is compared on the rule you set beforehand and the Methods sentence states the agreement and what couldn't be fixed.
Power user
16 min read
Choose tools
1
T16-L02
Choose Tools Your Team Can Use, and Afford
A one-page tool decision for the team: the workload, a monthly cost estimate for a normal and a busy month from the vendor's dated prices, the cap and alert that are actually set, a named admin and deputy, and the trial result; it passes when a colleague can recompute the estimate from the page and the vendor's price page.
Power user
16 min read
Structure & understand
1
T17-L02
Frame a Problem Your Team Agrees On
A one-page problem statement for a real request in your team, with who, what's hard, a useful result, a test and a list of what's out of scope, which passes when two colleagues have read it and signed it with no open objection.
Power user
15 min read
AI for lab data
1
T18-L02
Predict a Protein Structure and Read Its Confidence Honestly
One AlphaFold Server prediction with its downloaded files and a written confidence note (confident regions, relative positions, interface scores, one cross-check, what it can't tell you); it passes when a labmate opens the same files and agrees with every claim in the note.
Power user
16 min read
Share & review code
1
T19-L02
Work on a Shared Gitea Repository From Your Computer With OpenCode
A shared repository with a commit pushed from your computer under your name, a colleague's Gitea commit pulled to your computer, a .gitignore for raw data, and one same-line conflict stopped by OpenCode and decided by the two of you; every message says why.
Power user
15 min read
AI harnesses
1
T20-L02
Choose a Harness by Testing It on Five of Your Own Tasks
A ten-row table (five tasks x two harnesses: known answer, minutes, three habits) and a recommendation of at most five lines naming the pick, the deciding score, the habit that mattered, what the test did not cover and when to test again.
Power user
15 min read
Delegate desk work
1
T21-L02
Turn a Task You Repeat Into a Skill a Colleague Can Run
The skill folder with its SKILL.md, plus a one-page test sheet: your run on the first set of files, your run on a second set, one request that correctly did not use the skill, and a colleague's run with the model they used and where they got stuck. It passes when the colleague produced the result without your help and three rows they checked match the sources.
Power user
14 min read
Tools
AI models