Claude Operator: Prompt to Autonomy · 45 min · 15 XP
Capstone: cross-tool weekly review
Read bounded data from several services and propose actions without writing silently.
Build a weekly review that reads bounded test data from the connectors you set up in this level — mail, calendar, a document tool, a design file if you have one — and produces a brief plus a queue of proposed actions. Nothing external gets written without your approval.
The brief is the easy half. The queue is the point: each proposed action should name its target, the exact change, the evidence that prompted it, and the risk if it's wrong. An approval queue you can work through in two minutes is a workflow you'll actually keep using; one that asks you to re-derive each item is one you'll start rubber-stamping, which is worse than having no gate at all.
Do it now, in your own tools. Use practice accounts and test data throughout. Keep this evidence: the weekly brief, the approval queue with its four fields per item, a record of the scopes each connection used, and a note of anything you decided not to let the workflow do. Finish by auditing every connection you made during this level — remove what you no longer need and revoke the stale authorisations at the source.
Claude Code MCP guide · https://code.claude.com/docs/en/mcp
Loading your workspace…