All books
Compare the outcome you want, then open a book. Filter by level and track.
Progress is saved in this browser only.
95 books
Foundations & judgement3
- T01-L01From Idea to Working Result: The Four-Quadrant MethodOne working first result for a task from your own week, with five lines on the problem, what exploring changed, your choice, the result and your next step.
- T01-L02Check AI Output Before Your Team Relies on ItA 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.
- T01-L03Build the Smallest Thing Your Colleagues Can Run Without YouA working build for one recurring job (a saved prompt, form, automation or app) with a one-page README, a known-answer test with expected results and a decision paragraph naming two rejected options and a trigger; it passes when your deputy runs the test and one real job from the README alone, without asking you.
Chat & assistants5
- T02-L01Get Answers You Can Use from a ChatbotA before/after pair from your own notes, with the one follow-up that fixed it, which passes when a colleague can see the improvement and finds nothing in the final version that isn't in your notes.
- T02-L02Set Up Projects a Colleague Can Pick UpA 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.
- T02-L03Build a Shared Assistant Your Team Can Test and Take OverA shared assistant for one recurring team job, with a usage note, a test set of at least ten known-answer questions and a change log; it passes when your deputy replaces one source, reruns the test set, publishes the new version and a colleague gets the updated answer, all without your help.
- T02-L04A Self-Hosted Assistant Your Team Can Use SafelyA one-page assistant record (model and where prompts go, who can reach it, how accounts are approved, who administers it, allowed data classes, backups) plus Open WebUI running on one machine with a non-admin test account; it passes when the test account can chat but can't open the Admin Panel, sign-up is off, and a colleague answers three paste questions correctly from the record alone.
- T02-L05Run One Assistant for a Whole Institute or Company, and Hand It OverAn access audit for the shared assistant: every account, role, key and emergency access with its owner and revocation path, a tested one-action leaver removal, group budgets with last month's cost per group, the records and retention table signed by the data protection officer, and the substitute's run. It passes when a test leaver loses a live session and a fresh login within the stated window after one action, no local password login works, and the substitute repeats the audit from the runbook alone.
Prompting & context5
- T03-L01Write a Prompt You Can ReuseOne saved prompt improved across three revisions on the same five inputs, with a one-line note per revision, which passes when a colleague can see what each change did and every missing field reads "not stated" instead of a guess.
- T03-L02Build a Context Packet Your Team Can RerunA 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.
- T03-L03Put a Test Set Under the Prompt Your Team Depends OnA test folder for one shared prompt: the contract, at least 15 cases with known answers, the Promptfoo configuration with pinned versions, the before-and-after results and a README; it passes when a colleague reruns it from the README alone and gets the same pass or fail on every case.
- T03-L04Release Prompt Changes Through Review, Tests and a Way BackA prompt repository with one released change: the pull request with its automatic test run and approval, the release tag recorded in production outputs, and a rehearsed rollback. It passes when a colleague rolls production back to the previous tag from the README alone in under ten minutes, and IT has confirmed the access list in writing.
- T03-L05Keep a Production Prompt Healthy for Months, and Hand It OverAn operations folder for one production prompt: the regression set with its critical group and pass rule, the gate results for one change, a monitoring page with three signals and named responders, and one incident or drill note. It passes when the substitute reproduces the gate decision and a rollback from the runbook alone, and a colleague answers three auditor questions from the folder.
Your documents & knowledge5
- T04-L01Ask Your Own Documents and Check Every CitationThree answers from your own documents with every claim labelled and every supported claim traced to file, page and a short quote, which passes when a colleague can find each passage within a minute and nothing marked supported says more than its passage.
- T04-L02Curate a Document Set Your Team Can AskA 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.
- T04-L03Test and Fix the Document Assistant Your Group Relies OnA test folder for your group's document assistant (test questions with expected passages and answers, the settings record, a before-and-after result for one change, and a README), which passes when a colleague adds or changes one document, reruns the check from the README alone, and gets PASS or explains every failure.
- T04-L04Connect an Assistant to Real Documents Without Widening Anyone's AccessA permission test record for one connected source: the access model and why, the sign-offs, two ordinary test accounts, a marker document and the results for the authorised account, the outside account and a removed member. It passes when the outside account surfaces no marker, title, snippet or citation anywhere, the shared control works for both, and removal took effect within the stated window.
- T04-L05Keep a Connected Knowledge Base Current, and Prove a Withdrawn Document Is GoneA withdrawal drill record for one connected knowledge base: the stated windows, a current and a withdrawn marker checked before and after, the time from withdrawal to disappearance in every place checked, who received the withdrawn document and how they were told, and the substitute's run. It passes when the withdrawn marker is gone within the window, the current one still works, and the substitute ran it from the runbook alone.
Automation5
- T05-L01Your First Automation: Build It, Break It, Switch It OffA screenshot of your workflow's Executions tab showing one successful and one deliberately failed run, plus one line saying where its off switch is; it passes when the failed run left no row in your table.
- T05-L02Put AI in the Middle of a Workflow, and Check Every AnswerA 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.
- T05-L03Chain Checked Steps Into a Weekly Digest Your Team Can RerunA published n8n pipeline that produces a weekly digest draft for a named reviewer, with a test data table of six to eight cases and their expected end states, the model ID and workflow version in a README, and a note naming maintainer and deputy; it passes when the deputy runs the test set from the README alone and every case ends where the table says.
- T05-L04Make an Automation Safe to Fail Before It Touches Real SystemsOne n8n workflow that writes to a real system, with a failure test sheet and a takeover page; it passes when all five injected failures (double run, revoked login, empty input, timeout on the irreversible step, three failures in a row) end where the sheet says, IT and the data owner have signed, and a deputy takes over by hand from the page alone.
- T05-L05Keep Your Automations Running for Months, and After You LeaveAn operations folder for every automation you run (register, alert setup, incident routine, change log and handover checklist), which passes when every automation has a keeper and deputy other than you alone and a heartbeat that alerts a team channel, a deputy handles a staged incident from the folder alone, and a colleague answers three auditor questions from it in 15 minutes.
Build apps5
- T06-L01Build a Small Browser Tool You Will Actually UseYour index.html plus three test cases, each with the input, your hand-calculated answer and the tool's answer; it passes when all three match, an impossible input is refused, and one improvement came from real use.
- T06-L02Build a Small Shared Tool From a Prompt, and Test It With a ColleagueA 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.
- T06-L03Turn Your Team App Into One Colleagues Can Depend OnA published Base44 app with two roles, a test copy with known-answer records, a one-page test sheet and an operating note; it passes when a colleague who didn't build it runs the whole test sheet through the testing link and every line matches, and the deputy publishes one small change without your help.
- T06-L04Put Your Team App on the Organisation's Own Database, and Prove You Can Restore ItA restore record and a role test sheet for a team app whose data lives in a Supabase your organisation runs; it passes when the restored copy, built from the off-server backup into an empty database, gives the same answers to every line of the role test sheet, no admin key appears in the app, and IT and the data owner have signed.
- T06-L05Run the App Others Depend On, and Hand It OverA handover folder for one app (release steps, rollback record, monitor list, update and cost plan, access review, restore record), which passes when a deputy, with the builder's accounts disabled for the day, releases a change through staging, rolls it back, and restores last night's backup to a test server from the folder alone.
Agents4
- T07-L02Hand a Task to an Agent, and Check What It DidThe 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.
- T07-L03Build a Small Agent Your Colleagues Can Run, Test and StopAn agent folder (instructions, permissions file, reference files, test cases with expected results, check script, README naming maintainer and deputy) that a colleague clones and runs; it passes when their check run prints PASS, nothing outside the output folder changed, and they produce one real draft from the README without asking you.
- T07-L04Connect an Agent to a Real Mailbox Without Handing It the KeysA connection record for one agent working on a real mailbox or business system: the access granted and the denials proved, the gate rules, a before-and-after run of at least three planted-instruction tests, the sign-offs, and a tested switch-off. It passes when every planted instruction ends as a draft for a person or a refusal, and IT has signed.
- T07-L05Keep a Team of Agents Running for Months, With Memory a Person ApprovesAn operations folder for agents colleagues depend on: four weeks of run log and weekly reviews, the memory file with a source and review date for every note, a runbook with one drill, an audit index, and a deputy's handover record. It passes when the deputy runs a review and a drill alone and an auditor's question is answered from the folder.
Write code5
- T08-L01Start With OpenCode: Set It Up, Change One Line, and Undo ItA before-and-after table of five searches for your changed page, a screenshot of the Review panel showing the one changed line, and one sentence saying how you undid the change; it passes when all five results match, only the intended line changed, and Undo brought the old behaviour back.
- T08-L02Get a Script Your Colleague Can Rerun, Without Being a DeveloperA 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.
- T08-L03Write the Spec First, So an AI Assistant Can Change Code Your Team Depends OnA repository with SPEC.md, known-answer tests, the changed script, CHANGES.md and a version tag; it passes when a colleague, on their own computer and using only the README, runs the tests and all pass, and can point to the rule in SPEC.md behind every changed block of code.
- T08-L04Use OpenCode Desktop on Your Organisation's Real RepositoriesOne merged pull request in a real team repository, made with OpenCode, plus a one-page repository record. It passes when main rejects a direct push, a second person approved the pull request against the spec, the secret scan and tests ran before the push, and the record names the account, its access and the undo.
- T08-L05Run Automatic Checks, an AI Reviewer and Releases You Can Roll BackA repository with required checks, a comment-only AI reviewer, dependency notes, a release record and a runbook, plus a handover record. It passes when a pull request that breaks a known answer is blocked, a rollback drill restores the previous version in under 15 minutes, and the deputy runs both without help.
Create media5
- T09-L01Make One Image or Narrated Clip, and Label ItOne finished image or clip with its AI label, its alt text or captions, and the prompt that produced it; it passes when a colleague finds no wrong word, no missing label and no input you lack the rights to use.
- T09-L02Keep One Look Across Your Team's ImagesA 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.
- T09-L03Build a Caption Pipeline Your Team Can Rerun Every WeekA pipeline folder (script, settings, glossary, manifest, test recordings with known transcripts, check script, README) plus one week of reviewed captions; it passes when the deputy runs the check and one week's recordings on their own computer from the README alone, the check passes, and every published caption file has a named reviewer.
- T09-L04Transcribe Recordings That Must Stay in the BuildingA signed one-page data route plus a working local transcription setup; it passes when the test clips pass the check with the local model, fit and speed are measured on your own hardware, the job account is shown to be unable to read outside its folder, one approved real recording has a reviewed transcript, and a colleague has run the stop-and-delete procedure from the run sheet.
- T09-L05Keep Every Published AI Image, Voice and Video Labelled, Cleared and TraceableA media register and a one-page runbook in a place the organisation owns; it passes when every AI asset published in the last quarter has a complete register row, one monthly check has been run and logged, a takedown drill has been done on one asset, and the deputy answers an auditor's question about a randomly chosen asset from the register alone within five minutes.
Data & analysis5
- T10-L01Ask a Spreadsheet a Question and Check Which Rows It UsedThree answers from your own table, each with the assistant's row accounting and your own recount of one group; it passes when every source row is accounted for and each recount matches or explains the difference.
- T10-L02Clean a Messy Export Once, So Your Team Can Refresh ItA 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.
- T10-L03Build an Analysis Your Colleague Can Rerun and Get the Same NumbersA Git repository with the analysis script, settings per month, a lockfile, a sample with a hand-checked expected summary, a check script and a README; it passes when a colleague clones it on their own computer, the check prints PASS, and their rerun of one real month gives a summary identical to yours.
- T10-L04Connect Your Analysis to a Live System, and Stop Bad Data Before It Reaches AnyoneA scheduled pipeline reading a live source through a read-only account; it passes when a deliberately corrupted copy of the source makes the run stop with a clear message and leaves the last accepted output unchanged, a write attempt with the pipeline's account is refused, the data owner and IT have signed the field list, and a colleague can rerun a stopped week from the run sheet.
- T10-L05Keep a Data Pipeline Right for Years, and Trace Any Published Number to Its SourceA written trace of one number that was published from the pipeline, from where it appears back to the source rows, which passes when every step names its run ID, fingerprint and person, the missed-run alert and the drift check have each fired once in a test, and a colleague repeats the trace from the runbook alone and reaches the same rows.
Run your own AI5
- T11-L01Run an AI Model on Your Own Laptop, OfflineA screenshot of LM Studio answering your own prompt while your laptop shows no network connection, plus three lines (model and download size, your installed RAM, one task you'll use it for); it passes if the answer was generated after you disconnected.
- T11-L02A Local Model Your Tools Can CallOne 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.
- T11-L03Local AI Apps Your Colleagues Can Rely OnA one-page run note for one app (what it produces, who reads it, how to start, stop, back up and restore it, and what happens when it fails), plus a restore of your latest backup on a second computer; it passes when a colleague follows the note without your help and the restored app shows your real data.
- T11-L04Put Your Team's Assistant on a Server Colleagues Can ReachA server record for your team's assistant, plus a second-device test: it passes when the HTTPS address works from a colleague's computer, the Open WebUI and model ports don't answer from there, a restore from last night's backup has worked on another machine, and IT (plus the data protection officer if chats hold personal data) has signed the record.
- T11-L05Keep a Shared Model Server Fast, Affordable and RunningAn operations pack for a shared model server: a capacity table from a load test with the limit you set, a cost sheet comparing your server and an API per 1,000 answers, a one-page runbook and an operations log. It passes when a second operator has handled a practice outage from the runbook alone and the service owner has signed the cost decision.
Security, privacy & governance5
- T12-L01Decide What You May Paste Into AI at WorkYour last five pastes into an AI tool, each classified green, yellow or red with a one-line reason, and every red one rewritten; it passes when a colleague agrees with each colour and no rewrite still contains red material.
- T12-L02Clean the Copy, Label the Result, Spot the TrapA 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.
- T12-L03Give an Unattended Workflow Limits and a Stop a Colleague Can UseA published n8n workflow with its one-page operating rule and a filled-in test sheet for the five tests. It passes when all five tests pass, the credential can't perform any action the rule forbids, and the deputy stops the workflow from the rule alone while you watch without helping.
- T12-L04Lock Down a Self-Hosted AI Service Before Real Data Goes InA dated five-step audit of a self-hosted AI service: every finding with its fix, who fixed it and the retest result, plus one denied-access test and one restore test. It passes when every step has a result, no finding is open without a named person and a date, and IT has signed.
- T12-L05Keep One List of Every AI System Your Team Runs, and Make It Survive YouAn AI inventory for one team: every system with purpose, risk tier, responsible person and stand-in, data touched, training record, linked proof and next review date, plus a record of one 'author has left' test. It passes when a stand-in who didn't build any of the systems answers an auditor's five questions and handles a practice incident from the inventory alone.
Adoption & enablement4
- T13-L02Show a Colleague AI on Their Own Task, in 30 MinutesA 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.
- T13-L03Write a One-Page AI Rule Your Team Can Use Without Asking YouA one-page AI working rule, approved by the person accountable for the team, with its eight test cards and the results of three colleagues who didn't write it. It passes when every red card is stopped, each tester gets at least seven of eight right, the edge-case question gets an answer from the named person or deputy, and the deputy runs the card test with someone new without you.
- T13-L04Roll Out an AI Assistant to a Whole Department, With Access, Cost and Consent Settled FirstA rollout plan and the results of its first wave; it passes when every seat is tied to a named role and task, the cost includes people's time, the oversharing check and its fixes are recorded, the DPO and the works or staff council have signed, access is removable by one group change, and after wave one the plan shows accepted outcomes, unused seats and every objection with its answer.
- T13-L05Keep Everyone's AI Skills Current, and Show It When AskedA role map and a training register for one real department, which pass when every role's abilities are written as checkable tasks, every person with access to an AI tool has a current check result or a dated reason why not, one monthly reconciliation with the access lists has been run and logged, one change has gone through the refresh decision, and a deputy answers an auditor's three questions from the register alone.
Connect your tools4
- T14-L02Brief Your Team From the Shared Drive, Through a ConnectorA 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.
- T14-L03Turn a Connector Brief Into a Routine Colleagues Can RerunA saved routine (instructions, scope, inputs, output format), a test sheet with a fixed test week and four more cases with expected results, each colleague's run of the test week, and a README with maintainer, deputy and manual fallback; it passes when a colleague runs the routine from the README under their own account, their test-week file list matches yours or every difference is explained, and they produce the week's brief without asking you.
- T14-L04Build a Read-Only Connector for a System Your Assistant Can't Reach YetA working read-only connector with its README and a test sheet of six cases; it passes when all six give the expected result, a write attempt through the same key is refused by the system itself, a colleague's run shows only what their own access allows, and the system's administrator has agreed in writing.
- T14-L05Run Your Organisation's Connectors: One List, Per-Person Access, a Log and a Clean ExitA connector list for one department or company team, plus one retirement record: it passes when every connector has what it reaches, whose access, version, log, responsible person, stand-in and stop; two test accounts show different access where they should; and a retired connector can't be called while its former users know the fallback.
AI in research5
- T15-L01Use AI in Your Research and Say Exactly HowA disclosure statement for one real piece of your work, checked against the target journal's or funder's AI policy, with the use log behind it; it passes when a co-author can match every sentence of the statement to a log entry and to the policy.
- T15-L02Record an AI Step So a Co-Author Can Rerun ItA 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.
- T15-L03Get an AI Step on Participant Data Reviewed, Then Build It Inside the ApprovalOne review request with its data-flow map and the reviewers' answer, plus the working AI step: README, run record, the hand-coded test set and a colleague's rerun. It passes when no real data went anywhere before the answer, the test result meets the threshold you wrote down in advance, and the colleague reruns the step from the README and gets the same labels.
- T15-L04Set Up AI for a Whole Research GroupA one-page group AI-use policy plus a data map (each data source, its class, the tools allowed, who has access), reviewed and signed by the PI with a review date; it passes when every data source the group uses appears in the map and a new member can answer three paste questions from the policy alone.
- T15-L05Keep Your Group's AI Use Compliant and Running After You LeaveA compliance and continuity dossier: a register of the group's AI uses with who decided each open question, a retention plan per item, and a record of a named successor's walkthrough; it passes when the successor has run the main AI-assisted step and restored one archived result without help, and the PI has signed.
Choose tools5
- T16-L01Pick the Right Tool for One Task by Trying ItA one-page choice note for a task from your own week: must-haves, the candidates you knocked out and why, a trial of one challenger against your current method on the same input, and a one-sentence decision; it passes when a colleague could repeat your trial from the note and would reach the same choice.
- T16-L02Choose Tools Your Team Can Use, and AffordA 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.
- T16-L03Test a Tool on Your Own Work Before Your Team Depends on ItAn evaluation pack for one tool and one recurring job: the workload card, a case pack of at least 15 cases with known answers, the scoring rule, the results, and a one-page decision with a routing rule, a fallback and re-test triggers; it passes when a colleague reruns two cases and the fallback from the pack alone and reaches the same scores.
- T16-L04Replace a Tool Without Losing Your WorkA migration record for one team (inventory with a decision per item, re-test results in the new tool, cutover plan with rollback trigger, list of revoked keys and closed accounts, sign-offs); it passes when a pilot user completes the team's three most important jobs in the new tool without the old one, the rollback was tried on copies, and every credential the old tool used is accounted for.
- T16-L05Keep Your Toolset UsefulA toolset folder (register, last quarterly review, change routine, one completed retirement record, handover checklist), which passes when every tool has two named admins and organisation billing, every contract with personal data has a data processing agreement on file, one tool has been retired with a deletion confirmation, and a colleague answers three auditor questions from the folder in 15 minutes.
Structure & understand4
- T17-L02Frame a Problem Your Team Agrees OnA 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.
- T17-L03Explore What Already Exists Before You BuildA two-page exploration note with how it's done today, what exists, a checked source for every claim, one experiment and a revised problem statement, which passes when a colleague can open every source and find the claim it supports, and the two people who signed the original statement accept the revision.
- T17-L04Run a Pilot with Real Users and Real DataA pilot plan and a results note for a real pilot, which pass when the criteria and decision rule are dated before the start, data permissions are confirmed in writing, every criterion (including harm) has a measured result, and the go, change or stop decision follows the rule and is signed by the person who decides.
- T17-L05Decide Which Problems Deserve BuildingA ranked portfolio of every running and proposed item with four scores and a decision each, plus a decision log, which passes when every kept or built item has a named keeper and backup other than you, and a colleague who wasn't involved can answer three questions about past decisions from the log alone.
AI for lab data3
- T18-L01Count Cells With a Ready-Made Model and Check It by HandA segmented image plus a manual-vs-model count on one region, with your counting rule and one sentence on where the model failed; it passes when a labmate can recount the same region with your rule and get your manual number.
- T18-L02Predict a Protein Structure and Read Its Confidence HonestlyOne 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.
- T18-L03Build a Cell-Counting Pipeline Your Group Can Rerun and CheckA pipeline folder (script, settings file, pinned requirements, sample images, expected counts, check script, README) that a colleague sets up and runs on their own computer from the README alone; it passes when their check prints PASS, or any difference is explained and written into the README.
Share & review code5
- T19-L01Keep Your Files in Gitea and Get Any Version BackA private Gitea repository whose main file has at least four commits in its History, including one revert; every message says why, and you can show the red-and-green view of one change and the earlier version within a minute.
- T19-L02Work on a Shared Gitea Repository From Your Computer With OpenCodeA 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.
- T19-L03Propose, Review and Merge Changes With Pull RequestsA protected main, an issue and a merged pull request that fixes it, with at least one line comment, one Request changes, a new commit answering it and an Approve; the merge closed the issue, and a direct push to main is refused.
- T19-L04Check Every Change Automatically, Release Versions and Tell the LabA repository where a required automatic check runs on every pull request, one pull request was blocked by it and fixed, and publishing release v1.0 posted a message in the chat using the secret address.
- T19-L05Run Your Organisation's Gitea: Teams, Safe Sign-In and a Restore You Have TestedA colleague restores last night's backup on a test server using only the runbook and finds the organisation with its repositories, issues and pull requests; every password account has two-factor, a student account can read but not edit, and the mirror updated within the last day.
AI harnesses5
- T20-L01Same Model, Different Harness: See What the Program Around the AI ChangesA four-row comparison table (three given runs plus your own OpenCode run) with result, minutes and step counts, one sentence naming the biggest difference, and three lines for your own task: the task, a check the agent cannot see, and two measures.
- T20-L02Choose a Harness by Testing It on Five of Your Own TasksA 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.
- T20-L03Run a Harness on a Model You Control: Local Server or Team GatewayA half-page set-up guide: approved model and where it runs, the four values per harness, the practice task result (2.000) per harness, and one provoked failure with how each harness reported it.
- T20-L04Set Up a Harness So a Mistake Stays Small: Container, Rules, Keys and NetworkThe four promises with their layers, the two probe rows (before and after), and the practice task result in the final set-up. Passes when the after-row shows internet and writing outside blocked, no promise depends on a harness rule alone, the key expires and is limited to one model, and a colleague can rerun the probe.
- T20-L05Run Coding Agents for a Team: Shared Rules, a Test Set, Nightly Jobs and No Lock-InHouse rules with their checks, the four-row run table, links to one passing and one deliberately failed workflow run, and the operator log. Passes when every rule has a check, the job fails on a broken rule even if the agent reports success, harness/model/gateway are single settings, and the log names the next test-set date.
Delegate desk work3
- T21-L01Start With OpenWork: One Folder, One Task, and a Look at Every ChangeThe overview table the agent wrote for your practice folder, plus a five-line note: the model you used and where your files went, files counted against rows, three rows checked against their sources, one thing the agent got wrong or marked as not stated, and which requests you allowed. It passes when the row count equals the file count and the source files are unchanged.
- T21-L02Turn a Task You Repeat Into a Skill a Colleague Can RunThe 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.
- T21-L03Share Skills and Connections With Your Team, and Decide Who Gets WhatA one-page library sheet: each shared skill and connector with who can use it, who can change it, how people sign in and what the agent can do through it; where the service runs and who agreed to that; one change made by copy, test and replace, with its date; and the result of removing one colleague's access. It passes when a second colleague ran the shared skill without help, and the skill was gone from the removed colleague's Library after a refresh.