Agents

Books matched to this capability.

4books in this track

L02 · Power user

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

Hand a Task to an Agent, and Check What It Did

Give Claude Cowork a real preparation task on a copy of your team's files: a comparison table from a pile of protocols or supplier quotes. Write a delegation card with the outcome, the limits and the stop point, watch what the agent actually does, and have a colleague check the result before the team uses it.

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

L03 · Builder

Who is affectedColleagues depend on something you built
T07-L03

Build a Small Agent Your Colleagues Can Run, Test and Stop

Package a small agent that drafts, and never sends: instructions in a file, tool permissions the software enforces, a turn and spend limit, a test set of requests with known answers, a check script and a README. Decide first whether the job needs an agent at all, and stop where real credentials begin.

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

Builder20 minLast edited: Oct 18, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T07-L04

Connect an Agent to a Real Mailbox Without Handing It the Keys

Let an agent work on a real mailbox or business system while it holds no credentials itself: two small scripts hold one narrow key, IT limits it to one mailbox, a gate checks every draft, a person sends. Test it with planted instructions, prove what the key can't do, and know how to switch it off.

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

Integrator22 minLast edited: Sep 23, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T07-L05

Keep a Team of Agents Running for Months, With Memory a Person Approves

Run several agents that colleagues depend on, over months: keep the number of agents small, let a person approve every note they remember, log every run, review four numbers weekly, handle incidents with a written runbook, keep an audit folder, and hand it all to a deputy who has run it.

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

Operator19 minLast edited: Sep 23, 2026