DayDreamers

Enter passcode to access materials

Contact the instructor for access

DayDreamers
Claude Masterclass 1 / 14

Claude
Masterclass

Build your AI operating system — model, skills, tools, jobs

Diagnostic Model Skills Tools Scheduled Jobs
press arrow to begin
DayDreamers
Resources 2 / 14
01 — Start Here

Recording & Resources

Everything from tonight lives here. Watch the replay, grab the diagnostic template, and keep this page open while you build.

Session Recording

Full Claude Masterclass walkthrough — posted after class

Watch

Claude Code — install before class

Our workspace for the whole session. Have it running before Friday.

Download
Before Friday: install Claude Code and sign in. We start hands-on — you'll want it ready to go.

Stay Updated

No coding background needed. If you can write an email, you can do everything in this class.
DayDreamers
The Arc 3 / 14
02 — Roadmap

Tonight's Arc

We start where you are, then build the four components one layer at a time. By the end you'll have a working picture of your own AI operating system.

DiagnoseWhere you are
ModelThe brain
SkillsYour playbooks
ToolsYour real apps
JobsOn autopilot
The mental model: Model is the brain, Skills are its training, Tools are its hands, Scheduled Jobs are its heartbeat. Stack them and you've built an AI teammate.
DayDreamers
Diagnostic 4 / 14
03 — The Diagnostic

Most people use 5% of Claude Code

Not because it's hard — because nobody showed them the other 95%. You can't improve what you haven't named. So we score where you are on each of the four components, 1 to 5.

Component 1

Model

Do you pick the right model and brief it well, or take whatever's default?

Component 2

Skills

Do you re-type instructions each time, or have reusable playbooks?

Component 3

Tools / Connections

Is Claude connected to your real apps, or copy-pasting in and out?

Component 4

Scheduled Jobs

Does anything run on autopilot, or do you start every task by hand?

Be honest here. The goal isn't a high score — it's a clear starting line on each of the four.
DayDreamers
Diagnostic 5 / 14
04 — Try It Now

Build your own Claude diagnostic

Let Claude assess you. Paste this prompt, answer honestly, and it scores you 1–5 on each component and tells you the one move that lifts you a level.

# Paste into Claude Code You are my AI coach. Run a short diagnostic on how I use Claude Code. Ask me one question at a time about each component: Model, Skills, Tools/Connections, and Scheduled Jobs. Then score me 1 to 5 on each, and for my lowest one, give me the single highest-leverage habit to add this week.

The 1–5 ladder (same for every component)

1 · CuriousHaven't tried it
2 · Dabbling
Tried once or twice
3 · Regular
Use it weekly
4 · Builder
Built my own
5 · OperatorRuns without me
Keep your four scores. We'll come back at the end and pick the one component to level up first.
DayDreamers
The Framework 6 / 14
05 — The Framework

The four components

Everything you build with Claude is some mix of these four. Together they turn a chatbot into an operating system that works for you.

1. Model — the brain

The reasoning engine you talk to. Pick the right one for the job and brief it well.

2. Skills — the training

Reusable playbooks you teach Claude once so it does the task your way every time.

3. Tools / Connections — the hands

How Claude reaches your real apps — Gmail, Calendar, Drive, the web — to read and act.

4. Scheduled Jobs — the heartbeat

Cron jobs and automated triggers that run skills + tools on a schedule, without you asking.

Model + Skills + Tools + Jobs = an agent. We'll take each one in turn, then wire them together.
DayDreamers
Component 1 · Model 7 / 14
06 — Component 1

Model — the brain

The model is the reasoning engine. Two things matter: picking the right one for the task, and briefing it like a sharp new hire — role, context, and what "done" looks like.

Fast

Haiku

Quick, cheap, instant. Great for simple lookups and high-volume tasks.

Balanced

Sonnet

The everyday workhorse — smart and quick for most real work.

Deep

Opus

The heavyweight. Reach for it on hard reasoning and high-stakes thinking.

However you brief it, name three things

Role

Who should it be?

"You're my chief of staff." Setting the role sets the standard.

Context

What does it need?

Paste the thread, the doc, the numbers. Don't make it guess.

Goal

What's "done"?

Format, length, audience. "Three bullets for my board."

If the output is wrong, the brief was thin. Add the missing context and ask again — don't start over.
DayDreamers
Component 2 · Skills 8 / 14
07 — Component 2

Skills — expertise on tap

A skill is a playbook you teach Claude once — an SOP a specialist would follow — so it does the job your way every time, instead of you re-explaining it from scratch.

Without a skill

Every time you re-paste the same instructions, examples, and tone notes. Same setup, every time.

With a skill

"Use my proposal playbook." Claude already knows the structure, the voice, and the standard.

Skills worth building first

  • Write in my voice — tone, phrasing, and the words you'd never use.
  • Our proposal format — the exact sections and order every doc should follow.
  • Weekly review — the questions you ask yourself every Friday, run the same way each time.
In Claude, a skill can be a saved Project, a set of custom instructions, or — in Claude Code — a literal Skill file. Same idea: reusable expertise.
DayDreamers
Component 3 · Tools 9 / 14
08 — Component 3

Tools & Connections — give it your world

A teammate who can't see your calendar, inbox, or files is guessing. Tools and connections let Claude read and act on your real apps — so it works from facts, not assumptions.

Gmail

Gmail

"Summarize everything unread this week and flag what needs a reply."

Calendar

Calendar

"What's my week look like? Find two hours of deep-work time and protect it."

Drive

Drive & Docs

"Pull the latest proposal and turn the pricing section into a clean table."

Sheets

Sheets

"Read this signup sheet and group people by role and seniority."

Notion

Notion & Docs

"Find my notes from the last three calls with this client and draft an update."

The web

"Research this company and tell me who I'd actually want to meet."

The pattern is always read → reason → act. And always ask it to show you before it sends — trust grows one reviewed action at a time.
DayDreamers
Component 4 · Scheduled Jobs 10 / 14
09 — Component 4

Scheduled Jobs — autopilot

A scheduled job runs a skill and its tools on a cron schedule (every weekday 8am) or an automated trigger (a new email from a key client). This is where Claude stops being something you use and becomes something that works for you.

TriggerTime or event
Skill + Tools runRead · reason · act
Result landsReady to review

Daily digest

Each morning: news, calendar, urgent email, and your top 3 priorities — one short brief.

Inbox triage

Twice a day: sort mail into reply-now, FYI, ignore — with drafts ready for reply-now.

Meeting recap

After every call: summary, decisions, and action items, sent to the right people.

# Turn a habit into a scheduled job Every weekday at 8am, check my calendar and inbox, then send me a 5-bullet morning brief: top priorities, anything urgent, and one thing I'm forgetting.
The "AI chief of staff" everyone asks about is just a few good scheduled jobs stacked together.
DayDreamers
Putting It Together 11 / 14
10 — All Four

One brief, all four components

The components aren't separate tricks — they stack. Here's a single morning brief that uses every one.

Model

The brain

Sonnet does the reasoning — fast enough for a daily run.

Skill

The playbook

Your "morning brief" format: 5 bullets, priorities first.

Tools

The hands

Reads your calendar and inbox to get the real facts.

Job

The heartbeat

Runs every weekday at 8am — before you're even up.

# The whole stack in one sentence Every weekday at 8am (Job), use my morning-brief playbook (Skill) to read my calendar and inbox (Tools) and write me a 5-bullet brief (Model). Show me before sending anything.
Rule of thumb: the third time you ask for the same thing, turn it into a skill — then put it on a schedule.
DayDreamers
Second Brain 12 / 14
11 — Looking Ahead

Your second brain

All four components get sharper when Claude has a memory of you — your notes, decisions, and context in one place. That's the second brain: a 4-week course building your personal AI assistant with Obsidian + Claude Code.

CaptureNotes, calls, ideas
ConnectClaude reads it all
RetrieveAsk anything, anytime

Obsidian

Where your notes live — plain files Claude can read

Visit
Coming up: a 4-week course to build your second brain end to end — capture, connect, reflect.
DayDreamers
Hands-On 13 / 14
12 — Build It

Build your operating system

Open Claude Code. In the next 15 minutes, touch all four components. Use the timer in the corner.

  • Model — pick a real task from today and write a strong brief (role + context + goal). Run it.
  • Skills — save that brief as a reusable playbook so you never re-type it again.
  • Tools — turn on one connection (Calendar or Gmail) and ask Claude to read it and tell you something useful.
  • Scheduled Jobs — describe one recurring task you'd love off your plate. Ask Claude how to put it on a schedule.
Stuck on the brief? Ask Claude: "Interview me until you have enough to do this well, then go."
Done early? Share your best result in the chat — we'll workshop a couple live.
DayDreamers
Recap 14 / 14
13 — Wrap Up

Take it home

Remember

Model · Skills · Tools · Jobs

The brain, its training, its hands, its heartbeat. Stack them and you've built an agent.

This week

Level up your lowest

Take your weakest of the four and ship one scheduled job — the daily morning brief.

Next

Your second brain

A 4-week course building your AI assistant with Obsidian + Claude Code.

Share your feedback

Two minutes — it shapes the next class

Give Feedback

Stay in the loop

DayDreamers newsletter — new classes and drops

Subscribe
You don't need a smarter AI. You need a better-briefed one.
05:00
Timer
05:00

Have any questions? Just ask the instructor in the chat.