Delegate desk work

Books matched to this capability.

3books in this track

L01 · User

Who is affectedOnly you
T21-L01

Start With OpenWork: One Folder, One Task, and a Look at Every Change

Install OpenWork, a free desktop app in which an AI agent works on the files in one folder. Give it a practice folder, switch it so that every change waits for your click, hand it one task, and check the table it wrote against the files.

Outcome: The 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.

User15 minLast edited: Oct 12, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T21-L02

Turn a Task You Repeat Into a Skill a Colleague Can Run

Do a task once in OpenWork, then save the way you did it as a skill: a short text file the agent follows the next time someone asks. Read the file, test it on new material, and hand it to a colleague who runs it without you.

Outcome: 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 user14 minLast edited: Oct 12, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T21-L03

Share Skills and Connections With Your Team, and Decide Who Gets What

Move a tested skill from copied folders into one shared library in OpenWork Cloud. Set up an organisation with teams and roles, publish the skill to a team, add a connector where each person signs in as themselves, change the skill safely, and prove that removing someone takes their access away.

Outcome: A 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.

Builder19 minLast edited: Oct 12, 2026