Example: When You Stop Copying and Pasting

In short

Work that used to be all copy-paste between two windows.
You connect a single tool: the one you go back and forth on most.
What changes is the work, not the tool: the manual bridge disappears.
On actions that go out into the world, keep the brake tighter than usual.

Before: the work of the bridge

Every week you put together a status update. The material lives wherever you and your team track things to do; the result is a document you write yourself.

The current process, honestly:

you open the other tool and see what's moved;
you copy the entries you need and paste them into the chat;
you ask for them to be organized and summarized;
you copy the result back over there, or save it by hand.

Claude does the middle part brilliantly. You do the rest, and you're the bottleneck.

The connection: just one

You connect that one tool and nothing else. Not the whole suite, not "while we're at it, email too": whichever one costs you the most in copy-paste.

It's the right criterion for a precise reason: every connection adds tools the model can ask for and surface area for things to go wrong. One at a time, checking it's worth it.

After: the request becomes a single line

"Look at what moved this week and prepare my update in the usual format."

From here on it does the work: it reads straight from the tool, filters, organizes, writes the document. It already knows the "usual" format, because it's written in your instructions — or it's a skill, if there are a lot of steps.

Notice something: the whole course is working together in this one line. The permanent instructions give the format, the skill gives the procedure, the connection gives the data, permissions decide what it can touch.

Where I keep the brake tighter

There's a difference between reading and acting, and with connected tools it starts to matter.

Reading from the connected system: relax, that's the whole reason you connected it.
Writing into that system — changing state, sending messages, closing things: here permission stays on "ask me," at least until you've got a feel for how it behaves.

The reason is simple: a wrong file you can fix, a message sent by mistake you can't.

And now

The map drawn back in chapter 2 has now been fully walked: what you let it touch, what it knows about you, how many you put to work, what it's connected to outside.

One last piece is left, the one we put at the end on purpose because it's the most advanced: triggering actions on their own, at precise points in the loop, without anyone having to remember to.

Did you get it?

Two minutes, no grade. Trying to answer — even getting it wrong — cements the concepts far more than rereading. Not in the mood? Skip it: the lesson still counts as complete.

Which tool is worth connecting first?

Once the tool is connected, who decides whether an action actually gets carried out?

1
1. 1
2. 2
3. 3
2
1. 4
2. 5
3. 6
4. 7
3
1. 8
2. 9
3. 10
4. 11
5. 12
4
1. 13
2. 14
3. 15
4. 16
5. 17
6. 18
5
1. 19
2. 20
3. 21
4. 22
5. 23
6. 24
6
1. 25
2. 26
3. 27
4. 28
5. 29
6. 30
7
1. 31
2. 32
3. 33
4. 34
8
1. 35
2. 36
3. 37
4. 38
9
1. 39
2. 40
3. 41
10
1. 42
2. 43
3. 44
11
1. 45
2. 46