plugmyagentNew here? Start with guide 001, the beginner's guide, first.
01The level-up: stop assigning tasks, start building systems
The beginner move is handing over one task with a finish line. The intermediate move is setting up a workflow that runs without you asking each time.
The shift is small, but everything changes with it: from "do this" to "handle this, ongoing." A task ends. A system keeps working. Your agent can do both, but systems are where the real leverage lives.
"Check this price now."
"Watch this price every day and tell me the moment it drops below $400." You asked once. It works forever.
Tasks save you minutes. Systems save you hours. This guide is about systems.
02Teach it how you work: memory that matters
Your agent remembers context across conversations. The intermediate skill is feeding it the things that do not change: how you like your emails (short, no fluff), your budget rules, your projects, the names and details it keeps needing.
When it gets something wrong about you, correct it the way you would a person: "from now on, always use my work email for drafts." Say it once. It sticks.
One: preferences and context go in memory.
Two: secrets never do. Passwords and keys go in the secure vault, never in the chat.
Every few weeks, ask it "what do you remember about me and how I like to work?" Delete what is stale. Memory is a garden, not a hard drive.
03Connect your world: inbox, calendar, files
An agent with no connections is a brilliant assistant locked out of your office. Connections change that.
●Calendar
It can schedule, reschedule, and warn you about conflicts before you walk into them.
●Inbox
It can triage, draft replies, and surface only the messages that need your decision.
●Files
It can organize, summarize, and pull the right document the moment you need it.
You grant access once. After that, the approval habit in section 06 decides what it does on its own and what it brings to you first.
Start with read access everywhere. Let it look before it touches. Expand to write access once it proves it handles the small stuff. Read is cheap. Write is earned.
Walkthrough W03 connects your first MCP server in five minutes: the fastest way to feel what "connected tools" actually means. Start W03 →
04Put it on a schedule: briefings, checks, watches
Three patterns cover almost every recurring need.
"Every weekday at 7:30am, send me a 5-bullet briefing: the top news in my industry, my calendar for the day, and anything on my watch list that moved."
"Every morning, check my inbox. Draft replies to anything routine. Only ping me about the ones that need my decision."
"Watch flights to Denver for October. Tell me the moment a round trip drops under $250."
Define the trigger, the quiet hours, and what "tell me" means. Vague schedules create noise. Precise schedules create leverage.
05Run long projects without losing the plot
Big work dies in long, shapeless conversations. The intermediate move is milestones plus checkpoints.
Before it starts, ask for the plan: "Break this into milestones and show me the plan before you do anything." Approve the plan, then let it run. Then add one rule: "Report back after each milestone with what is done and what is next. Do not wait until the end."
Keep one conversation per project. Everything it learns stays in one place, and you can scroll up any time to see how a decision was made.
"Pick up where we left off: the last finished milestone was X, continue from Y." Do not restart from zero. Context is the asset. Protect it.
06The approval habit: what to auto-allow vs always check
You do not want to approve everything. You also do not want to approve nothing. Set the line once, in plain words.
Research, drafts, organizing files, summaries, reminders, price checks. Anything reversible and private.
Spending money, sending or posting anything, touching accounts, changing settings, deleting anything. Anything hard to undo.
"Draft anything, send nothing. Research anything, buy nothing. If it is hard to undo, ask me first."
When in doubt, it asks. That is the deal that makes everything else safe.
07When it goes wrong: the 3-minute fix
It will misunderstand you sometimes. The fix is almost always fast.
- Point at the exact problem. Not "this is wrong" but "the dates are wrong, use October 16 to 18, not September." Specific corrections teach. Vague ones do not.
- Give the correction once, then move on. "From now on, prices in USD." Done. Do not re-explain every time.
- If the output is vague, ask for shape. "Give me the top 3 with prices and links, not a paragraph." Agents default to prose. Tell it the format you want.
- If it assumed wrong, add the constraint it missed. Most bad output is a missing constraint, not a bad agent. "You assumed business travel. This is a family trip with two kids." Then let it redo.
A correction inside the same conversation keeps everything it already got right.
08Five intermediate plays
Copy, paste, customize. Each one is a system, not a task.
"Every Monday at 8am, send me: the 3 biggest stories in [my field], any price drops on my watch list, and conflicts in my calendar this week."
"Every weekday at 9am, scan my inbox. Draft replies to anything routine. Flag the 3 messages that need my decision, with a one-line summary of each. Send nothing."
"Track my [project name] project. Every Friday, ask me for a status update, then reply with: what is done, what is stuck, and what is next."
"Watch [product, flight, hotel]. Alert me the moment the price drops below [number] or a clearly better option appears. Include the link."
"Take my [notes / voice memo / rough draft] and turn it into three things: a social post, a short email, and a one-pager. Keep my voice, cut the fluff."
09What's next
You have gone from chatbot to coworker to systems builder. The advanced guide is next: chaining agents together, building custom workflows, connecting your own tools and data, and running your agent like a small ops team.
Take this guide with you
The full intermediate guide as a clean, shareable PDF. Same series, same format.
Download the PDFMissed the first one?
From Chatbot to Coworker: the beginner's guide that starts the series. The chatbot-to-agent shift, the delegation recipe, and five starter tasks.
003Next: the advanced guide
From Systems to Leverage: compose teams of specialist agents, build your own workflows, feed them your data, and run the whole thing like a small ops team.