8. Your Agent vs LeanScale Agents
Action Step
Complete this before moving on.
Find TaskMaster in Slack and send it a test transcript (or a few paragraphs of meeting notes). Compare its output to what your personal agent would produce with the same input.
Training Guide
You have your own agent. But LeanScale also has shared agents that do specific jobs. Let's talk about when to use which.
Your Personal Agent
This is YOUR assistant — it knows your name, your projects, your preferences. It has your SOUL.md, your USER.md, your memory. It's now connected to Fireflies and GitHub — it can reach your meetings and your repos.
Use it for: personal tasks, quick questions, drafting messages, processing your transcripts, checking repos. This is your desk assistant. It works for you.
TaskMaster — The Team's Workhorse
TaskMaster is a shared LeanScale agent with a specific job: process transcripts and create tasks in Teamwork. It's trained on the LeanScale workflow — it knows how to format tasks, assign owners, set due dates. It has its own memory, its own skills, optimized for this one workflow.
You know how in Section 3, you processed a transcript and manually created Teamwork tasks? TaskMaster does that automatically.
When to use TaskMaster vs your own agent:
- TaskMaster: when you need tasks created in Teamwork from a transcript — it's optimized for this
- Your agent: when you need something personal, custom, or outside the TaskMaster workflow
The "Teach Them to Fish" Philosophy
Yasin's lean: learn to build your OWN skills and workflows rather than depending on centrally-maintained agents. TaskMaster is great for standard workflows — but YOUR agent, with YOUR custom skills, is where the real power is.
We maintain TaskMaster for the team. But the goal is for you to build your own skills that make YOUR agent just as powerful for YOUR specific work. This is a compounding asset — every skill you build makes your agent more capable over time.
The Fleet (Just Enough Context)
Every team member at LeanScale has their own agent running on its own server. There are 17+ agents in the fleet — each with a unique name. The tech team manages the servers — you don't need to worry about the infrastructure.
You just need to know that your agent is always on, always running, and the tech team keeps it healthy. If it goes down, let the tech team know.
Comment in Slack
Post your answer in your onboarding channel.
What's one custom skill you could build for your personal agent that would be more useful to you than any shared team agent?