Ch 13: Skills as Capability Injection
Picture a family doctor's clinic on a quiet street. Dr. Patel sees patients all day long — colds, sprained ankles, stomach bugs, earaches. She is good at her job and handles most visits from memory. Her head is clear, her decisions are quick, and her patients trust her.
One Tuesday afternoon, a patient named Marco walks in. His skin has an unusual rash that Dr. Patel has never seen before. It does not match any of the common conditions she deals with every week. She could guess. She could try a treatment that works for a different rash and hope for the best. But Dr. Patel is smarter than that.
She turns to the shelf behind her desk. It holds dozens of specialist handbooks — one for tropical diseases, one for rare skin conditions, one for unusual allergies, and many more. She pulls out the handbook on rare skin conditions, flips to the chapter on heat-triggered rashes, reads the recommended steps, and treats Marco accordingly. When she is done, she closes the book and slides it back on the shelf.
A smart helper does not try to know everything — they know when to look something up and when to put the book back.
The handbook did not get glued to Dr. Patel's forehead. She did not carry it around for the rest of the day. She borrowed the knowledge, used it, and returned it. Her head stayed clear for the next patient.
Why the Doctor Doesn't Memorize Every Book
You might wonder: why doesn't Dr. Patel just memorize every specialist handbook? If she knew everything in every book, she would never need to reach for the shelf. Problem solved, right?
Not quite. Here is what would actually happen:
- Her head would be too full. If Dr. Patel tried to memorize the contents of forty specialist handbooks, she would get slower. Every time she saw a simple cold, her brain would be sifting through information about tropical diseases, rare bone conditions, and unusual eye problems — none of which matter for a cold.
- She would mix things up. With so many facts crammed together, she might confuse the treatment for one rash with the treatment for a completely different rash. Two conditions might have similar-sounding names, and with everything jumbled in her memory, she could grab the wrong one.
- Most of it would go to waste. On a typical day, Dr. Patel sees colds, sprains, and earaches. All that specialist knowledge would just be sitting in her head, taking up space, never being used.
- Updating would be a nightmare. Medical knowledge changes. If Dr. Patel memorized everything, she would have to re-memorize entire handbooks every time a treatment was updated. But if the knowledge lives in books on the shelf, each book can be updated on its own without disturbing the rest.
The better approach is exactly what Dr. Patel already does: keep a clear head for everyday work, and reach for the right handbook only when a rare case appears. Pick it up, use it, put it back.
You are Dr. Patel. It is a normal afternoon at your clinic. Let's see what happens when a patient brings something you have never encountered.
Put the doctor's handbook steps in the correct order
Drag to reorder, or use Tab + Enter + Arrow keys.
- A patient arrives with symptoms the doctor does not recognize
- The doctor checks the reference shelf for the right handbook
- The doctor opens the handbook and reads the relevant chapter
- The doctor follows the handbook's instructions to treat the patient
- The doctor closes the book and returns it to the shelf
Borrowed Knowledge, Not Permanent Baggage
Here is the detail that makes Dr. Patel's approach so effective: the specialist knowledge is borrowed, not permanent.
Think about the difference. If Dr. Patel memorized every handbook, that knowledge would be with her all the time — during every patient visit, whether she needed it or not. Her mind would be crowded. She would be slower with simple cases because her brain would have to wade through mountains of information that had nothing to do with a common cold.
Instead, the handbook arrives at the exact moment she needs it. She reads it while she is looking at the patient with the problem. The information is right there, next to the situation that calls for it. And when the job is done, the book goes back on the shelf. It is not taking up space in her head anymore. Her mind is fresh and ready for the next patient.
This is the power of temporary knowledge. The doctor's everyday skills — the things she uses on every visit — stay sharp and uncluttered. The specialist knowledge flows in when a rare case appears and flows back out when the case is resolved.
Think of it this way: who the doctor is stays the same every day. What the doctor looks up changes depending on who walks through the door. The handbooks belong in the second category — temporary expertise borrowed for a specific patient, not a permanent part of the doctor's identity.
What's Next
You have a system that can dynamically expand its capabilities at runtime. Skills keep the agent lean when idle and powerful when needed. But right now, skills are loaded manually — someone decides which skills are needed and passes them to the agent.
In Chapter 14, you will build automations: background workflows that trigger automatically in response to events. When code is pushed, an automation loads the right skills, creates an agent, and runs a task — all without human intervention. Skills become the building blocks of automated workflows.