PRESENTS · MAVEN COHORT 2 · SESSION 3 OF 5 · WEEK 4
SAT JUN 6, 2026 · 12:00 PM EDT
Make it
safe to ship.
Your skill · one real website · three real demos · the same five building blocks.
Module 3 · Week 4 · Live on Maven
CO-INSTRUCTORS
S
Sandhiya Thiruvengadam
Leader, HRBP & AI · Apexon
Q
Q Hamirani
Chief People Officer, Highlevel · Adjunct Faculty, LBS
Session 3 · Slide 1/17
FROM YOUR WEEK 2 FEEDBACK + QUESTIONS
We heard you.
★ NANCY ASKED
"Do you recommend always having Claude
running to make scheduling work?"
OUR ANSWER · LIVE TODAY
We'll demo Cowork's scheduled run in the routine demo.
★ OLIVIA ASKED
"Why Gemini first · when there are so
many tools to pick from?"
OUR ANSWER · LIVE TODAY
We'll show one door · in three different vocabularies.
★ ON PACING
You asked us to slow down · we're picking ONE example today and walking through it slowly.
Less surface, more depth. Stop us when you have a question.
↩ HOME Session 3 · Slide 2/17
★ FIRST 12 MIN · ROUND ROBIN
What you built · or what's next.
60 sec each · share the skill you shipped · or the one you're going to build · 12 minutes · steal what works.
★ HOW IT GOES
1
Share-screen the Slack thread
Pinned in #cohort · everyone's one-liners
2
Each person · 60 seconds · live
Elaborate your line · what surprised you
3
Listen for what to steal
React with 🔥 to anything you'd fork
4
Thread stays pinned
Cohort 3 scrolls it · steals your idea next quarter
# cohort · pinned
SKILL SHARE · PIN THIS
Quick ask for Session 3 prep · drop a reply
with two lines:
SKILL NAME · 3-5 words
DESCRIPTION · ≤15 words
S
Sandhiya
just now
jd-ai-native-check
Scores a JD vs 3,497 frontier-AI roles · returns a punch list of edits.
github.com/AlmostTechHR/AI-Native-Jobs-GPL · fork it · open in Claude Code
+ YOUR REPLY GOES HERE
Drop yours by Fri June 5. "Still cooking" is a fine reply too.
And quick poll · type 1 · 2 · or 3 in chat for where you are on terminal.
↩ HOME Session 3 · Slide 3/17
How to use Claude · the restaurant
Same map. Today we step through Door 3 for the first time. Standing orders get scheduled.
FRONT + BACK · 1 NEW ZONE OPENS TODAY
✓ SESSION 1 ① WALK IN
Chat
claude.ai · type back-and-forth
Where you started 3 weeks ago.
✓ SESSION 2 ② SIT AT A TABLE
Claude Project
a contained workspace with memory
Your CoS v1 lives here. Built last week.
✓ SESSION 2 ③ THE FILE ON YOU
CLAUDE.md
the profile that personalizes
Powers Sandhiya's CoS demo · Slide 8.
✓ SESSION 1 ④ THE MENU
Skills
markdown packs Claude can call
By now you've installed at least one.
YOU ARE HERE ⑤ STANDING ORDERS
Routines
scheduled actions Claude runs for you
Anatomy on Slide 10. Built today.
Your first one ships by Fri Jun 12.
⑥ THE RUNNER
Dispatch
parallel sub-agents
Met in Session 4.
⑦ KITCHEN LINE
Computer Use
Claude drives a browser
Met in Session 4.
⑧ THE RECEIPT
Hooks
what fires after every meal
Mentioned in Session 4.
⑨ BACK OF HOUSE · the supply chain (still ahead)
APIs · Connectors · MCP
Today's Routine will pull from one connector (Granola). Full Supply Chain Trio = Session 4.
When your routine fires, it reaches BACK here to read your data.
API Connector MCP Today: Connector. Session 4: all three.
DOORS ↔ ZONES
Door 1 ✓ · Door 2 ✓ · Door 3 = TODAY (Standing orders + Claude Code · 1 of 5 zones opens).
↩ HOME Session 3 · Slide 4/17
Today's path · three real demos
One set of building blocks · three completely different things shipped with them.
1
JD AI-Native
on Claude Code
★ 20 MIN · ONE STEP FURTHER
Same prompt agent you built ·
now hosted on a URL.
→ Bring your JD HTML (any tool)
→ Open the cohort repo · fork
→ Drop into CLAUDE.md + knowledge
→ Push · get a URL to share
From "I built one for me" to "my team has the URL."
2
Sandhiya's
learning routine
★ 15 MIN · DAILY ROUTINE
A Routine that fires every
morning at 9 AM.
→ Reads Granola yesterday
→ Reflects on what to learn
→ Posts to Slack as Daily Learning
Answers Nancy's "always running?" question live.
3
Inside the build ·
what it took.
★ 15-20 MIN · SHOW + WALK
The GPL site you've been using ·
opened end-to-end together.
→ Open the live site
→ "What would you redesign?"
→ Walk the code + GitHub
→ Show Netlify auto-deploy
No live build · feedback drives next week.
One recipe · three meals. The 5 Building Blocks carry through all three.
Same prompt agent you built last week · today we take it further on Claude Code.
↩ HOME Session 3 · Slide 5/17
★ REAL QUESTION YOU ALL ASKED · COWORK OR CODE?
Use it · delegate it · steer it.
Three rungs on one spectrum. Same Claude · what changes is how much you're in the loop.
LOW TECHNICAL LIFT
DELEGATE & WALK AWAY
FULL CONTROL · STEER LIVE
COWORK · DESKTOP
Use it.
Does your work in your own files,
sandboxed. You approve what it
touches. No technical skill needed.
PICK IT WHEN
It's one task · low judgment ·
you want it done tomorrow.
CODE · ON THE WEB
Delegate it.
Hand a well-defined job to a cloud
sandbox · walk away · come back to
the result. No terminal needed.
PICK IT WHEN
You know what you want ·
just don't want to babysit it.
CODE · IN TERMINAL · ★ TODAY
Steer it.
Full local access · you course-correct
as it works. For jobs that need control
and live direction · not hand-off.
PICK IT WHEN
You need to drive the work as
it unfolds · push it · own history.
Think of a book · Cowork is the audiobook you press play on · Code on web is the editor's read-through you ask for · Code in terminal is the manuscript you mark up live as you read.
The simple tell: web when you know what you want · terminal when you need to drive it as it unfolds.
↩ HOME Session 3 · Slide 6/17
★ ANATOMY OF A WEBSITE PLATFORM
globalpeoplelabs.com · in pieces.
Same building blocks as a Gem · just at the next level of intensity. Site mockup on the left · what runs each piece on the right.
GLOBAL PEOPLE LABS
Home
Cohorts
Atlas 30
Resources
Contact
COHORT
👤 Sandhiya Thiruvengadam · sandy_vignesh@outlook.com
Manage account · Sign out
IDENTITY
Cohort 2 sessions
Session 3 · Jun 6
Make it safe to ship
JOIN ZOOM →
Session 4 · Jun 13
Deploy & make the case
Session 5 · Jun 20
Capstone showcase
MAVEN
Featured resources
AI Agency Ladder
9-slide walkthrough · video
CoS Template
Use Case 1 · download
JD AI-Native
Use Case 2 · 2 .md files
NETLIFY
LAYER 1 · WHAT YOU CLICK
Pages · buttons · sign-in.
· Pages: Home · Cohorts · Atlas 30 · Resources
· Sign-in: Netlify Identity (the orange dashed box)
Same as Gem's interface layer · just bigger.
LAYER 2 · WHERE IT LIVES
Code on GitHub · site on Netlify.
· GitHub: every file with full history
· Netlify: serves the site · auto-deploy on git push
Same as Gem's Knowledge files · just version-controlled.
LAYER 3 · WHERE WE BUILD
Claude Code · on a laptop.
· Claude Code: the CLI that edits + pushes
· .env: the file that holds the API keys
Same as Gem's Instructions · but on your machine.
Three layers · five services · one .env file holds all the keys.
↩ HOME Session 3 · Slide 7/17
★ REAL QUESTION TWO · DO YOU NEED A GITHUB ACCOUNT?
What you actually need to start.
Another real question you all asked this week. Here's the answer · per surface.
COWORK · USE IT
YOU NEED
The desktop app +
the folder you choose.
That's it.
GITHUB?
No · never.
RUNS
On your machine ·
sandboxed.
CODE · ON THE WEB
YOU NEED
A Claude account +
a connected GitHub
repo to work on.
GITHUB?
Yes · it clones
your repo.
RUNS
In a secure cloud
sandbox.
CODE · IN THE TERMINAL
YOU NEED
A one-time local install ·
working on your own files.
GITHUB?
Optional · only if
your project uses it.
RUNS
On your machine ·
full access.
So · GitHub is only for Code on the web. Cowork never needs it · terminal only if your work already lives there.
↩ HOME Session 3 · Slide 8/17
★ HUDDLE · 60 SECONDS · BEFORE WE GO LIVE
The words you'll hear · and what terminal lets us do.
Two minutes on vocab · then a 60-second comparison · then we're in Demo 1.
★ 8 WORDS YOU'LL HEAR TODAY
fork
Your own copy of someone else's
repo on GitHub. Yours to change.
clone
Download the repo to your laptop
so you can open it locally.
pull
Grab the latest changes from
GitHub down to your laptop.
push
Send your changes from your
laptop up to GitHub.
commit
Save a checkpoint of your work
with a message · "what changed?"
diff
The list of changes between
now and your last commit.
plan mode
Claude shows its plan first ·
you approve before it does.
auto-accept
Claude applies its edits without
asking each time. (shift-tab.)
★ WHAT CODE-ON-WEB CAN'T DO · WHAT TERMINAL CAN
1
Read any file in your project folder
Ask once for anything beyond. Web only sees the one repo you opened.
2
Run any CLI tool you already use
git, gh, python, npm, your ATS scraper. Web is a fixed sandbox.
3
Multi-step plans without re-prompting
Plan mode → auto-accept lets it work through a multi-step task in one run.
4
CLAUDE.md + local skills auto-load
Local conventions become defaults · web's Projects come close, with less control.
5
Private code never goes to GitHub
Same Claude data terms as Cowork · matters for HR data.
6
Show the diff before every change
You see what it's about to do, file by file. You hit y or n.
If you can read these eight words, you can read everything in Demo 1.
↩ HOME Session 3 · Slide 9/17
★ DEMO 1
20 MIN · 4 SURFACES · 1 SHIP
JD AI-Native · one step further.
Last week 4 ways to prototype. This week · 1 way to ship · so your team can actually use it.
★ LAST WEEK · 4 WAYS TO PROTOTYPE
G
Google Gem
5 fields · paste prompt · drop files · run.
"What you built last week."
M
Microsoft Copilot Agent
Same 5 fields · inside Copilot Studio.
Where Sandhiya's CoS lives.
P
Claude Project
Same recipe · inside claude.ai.
Persistent · conversational.
C
Claude Cowork
Same shape · desktop · runs on your files.
No terminal · GUI.
★ ALL FOUR · PROVE THE BRAIN
None of them ship to a URL your team can hit.
★ THIS WEEK · CLAUDE CODE
Ship it · so your team can use it.
★ CLAUDE.md = the same prompt · now in code
★ Knowledge files = committed to GitHub · auditable
★ Tweak = a commit · full history · roll back anytime
★ Push = live URL · your team logs in (auth · Layer 1)
★ .env = the API keys file · same pattern as our site
★ SAME RECIPE · SAME WEBSITE PATTERN AS SLIDE 7
Pages · sign-in · keys in .env · all the same three layers.
Just smaller. Your team's first internal HR tool.
"I built one for me" → "my team has the URL."
Claude Code adds one thing: shippability. The brain is already yours.
↩ HOME Session 3 · Slide 10/17
★ TODAY'S BUILD · YOUR TURN
Your JD · on Claude Code · in 5 moves.
Same prompt agent you built last week (any tool). Today we make it shippable. The end state · a URL you paste in Slack.
★ WHERE YOU ARE
Your JD lives in
your AI tool.
Cowork · Claude Project · Gem · Custom GPT · all valid.
· Perfect prompt · grounded knowledge
· Runs in your browser
· Your team can't use it
· You can't share a URL
A QUESTION YOU ALL ASKED
"Where does the HTML go?
How do I share it with my managers?"
★ THE 5 MOVES · LIVE TOGETHER
1
Bring your JD HTML (from wherever you built it)
If you haven't built one · prompt it now · prompt till you get what you want.
2
Fork the cohort repo · open Claude Code in terminal
gh repo fork AlmostTechHR/AI-Native-Jobs-GPL --clone · then claude .
3
Tell it: "make a CLAUDE.md from my prompt"
Same instructions · now in code. Code reads it every time.
4
Add Knowledge files · git commit
Drop the .md files in · save the state · we have a history.
5
Push · get a URL · paste it in Slack
git push · Netlify deploys · your team has the link.
★ WHERE YOU'LL BE BY 1 PM
Your JD · shipped
to a URL.
★ Same brain · same prompt
★ Knowledge files in Git · auditable
★ Every tweak is a commit · roll back
★ Your team logs in · uses it
★ Same .env pattern as our website
YOUR DELIVERABLE
A URL pasted in Slack · #cohort ·
before we close the room today.
This isn't theoretical. By 1 PM you'll have a URL you can paste in Slack.
↩ HOME Session 3 · Slide 11/17
Anatomy of a Routine
Week 1 you learned the shape of a Skill. This is the shape of a Routine.
routines/daily-learning-slack.md
4 PARTS THAT MAKE A ROUTINE
1
---
2
name: daily-learning-slack3
description: Posts one learning from yesterday's meetings to my Slack.
4
schedule: "0 7 * * *"# cron format · every day at 7:00 AM
5
output: slack:dm:@sandhiya6
---
8
# When this fires
9
1. Pull Granola transcripts from last 24h.
10
2. Surface ONE non-obvious insight a busy
HR leader would miss.
11
3. Match my voice: bullets, exec-up-top.
12
4. Post with header "★ One thing from
yesterday"
13
5. Cite N meetings + read-time.
1
NAME + DESCRIPTION
Same as a Skill. Identity for Claude.
2
SCHEDULE · the NEW field
Cron line. The one thing that makes a Routine.
3
OUTPUT CHANNEL
Where it lands. Slack · email · file · Notion.
4
BODY · markdown SOP
Numbered steps. Claude follows top-to-bottom.
CATEGORY B · WHAT ELSE LIVES IN DOOR 3 ↑
Routines are 1 of 5. Dispatch = event-triggered · Skills = anatomy from S1 · MCP = connectors from S2 · Hooks = fires before/after for CLEAR audits
★ WHAT YOU SHIP THIS WEEK
By Friday Jun 12: ✅ 1 Routine written · ✅ 1 schedule running · ✅ 1 daily ping landing in your Slack.
★ HOW THIS TRANSLATES TO YOUR STACK
same idea, different brand · pick the door your company already pays for
★ CLAUDE · RECOMMENDED
Routine (cron + Skill)
MICROSOFT COPILOT
Power Automate scheduled flow
GOOGLE GEMINI
Apps Script + time trigger
OPENAI CHATGPT
Scheduled Tasks (Pro feature)
↩ HOME Session 3 · Slide 12/17
★ DEMO 2
15 MIN · ANSWERS NANCY
Sandhiya's learning routine.
A daily reflection that posts itself before I open my laptop.
★ THE ROUTINE · ANATOMY
TRIGGER
9 AM
every day
Scheduled · automatic
Nancy's "always on"
question · answered.
READ
Granola
yesterday's notes
All my meetings.
All the people.
All my notes.
★ LLM REFLECTS
"What could I have
done better today?"
Not a summary.
A learning prompt.
The agent reasons.
OUTPUT
My Slack
Daily Learning post
Waiting for me when
I open my laptop.
No clicks · just there.
Same 5 Building Blocks · the Trigger is what makes this Category 2 not Category 1.
A Routine doesn't wait for you to ask.
It just shows up · every morning · same time · with the answer.
↩ HOME Session 3 · Slide 13/17
★ SAFETY BASELINE · BEFORE YOU SHIP
4 levels · 5 checks · one Gmail rule.
★ 4-LEVEL DATA SENSITIVITY
What kind of data goes into the agent?
1
Public
JD samples · published reports · ATS questions you wrote · benchmarks
2
Internal
Onboarding docs · benefits FAQs · org chart · job titles · process maps
3
Confidential
Performance reviews · comp bands · individual feedback · 1:1 notes
4
Restricted
PII · health · legal · investigations · M&A · termination details
★ THE SIMPLE RULE
If you wouldn't send it via Gmail · don't feed it to AI.
★ CLEAR GOVERNANCE
5-check ritual · run before every new agent + connector.
C
Consent
Data owner said yes? They can revoke anytime?
L
Limits
Read-only first. Narrow tokens. Never write on day 1.
E
Explainable
Every answer cites source · meeting · sender · file.
A
Auditable
CLAUDE.md · mcp.json · history · reviewable in 1 line.
R
Reversible
One command removes · token gone · agent unregistered.
↩ HOME Session 3 · Slide 14/17
★ DEMO 3
SHOW + WALK · 15-20 MIN · NO LIVE EDIT
Inside the build · what it took.
The very site you've been using for three weeks · opened end-to-end.
No live build today · we walk the same pipeline you'll run on your JD.
★ THE WALK · 5 STOPS · ASK QUESTIONS ANYTIME
1
Open the live site
Pull up globalpeoplelabs.com.
Scroll the resources page together.
Same site you've used for 3 weeks.
2
"What would you redesign?"
Cohort feedback · 3 minutes in chat.
Cards · copy · order · gates.
Drives the v3 backlog · not today's edit.
3
Walk the codebase
CLAUDE.md · the index files · resources.
No magic · markdown + HTML + auth.
"You could read every line of this."
4
Show GitHub
Commit history · every tweak audited.
Diffs · who changed what · when.
This is the audit trail HR teams ask for.
5
Show Netlify
A push to main · auto-deploys in 30 sec.
No drag-and-drop · no manual upload.
Free tier · works for small HR tools.
★ THE TAKEAWAY
Same recipe.
Same pipeline you'll run on
your JD this week.
No live build today · feedback in chat shapes v3 · the pipeline you saw is the pipeline you'll use.
↩ HOME Session 3 · Slide 15/17
★ HANDS-ON · 15-20 MIN · NOBODY LEFT BEHIND
Share your screen.
Three checks. Five commands. Done.
★ CHECK 1 · GITHUB
Account works
☐ github.com loads · signed in
☐ Profile is visible
☐ One test repo created
☐ README added in browser
STUCK?
Share screen · we fix it now.
★ CHECK 2 · CLAUDE CODE
Install + login
☐ Open Terminal app
☐ Type claude · Enter
☐ Signed in to claude.ai
☐ Got the "Ready" prompt
STUCK?
Share screen · we fix it now.
★ CHECK 3 · FIRST RUN
Do something.
$ /init
→ creates CLAUDE.md
$ "what's in this folder?"
→ Claude lists files
$ "create hello.md"
→ Claude creates file
SUCCESS
A file you didn't write yourself.
★ THE 5 COMMANDS · MEMORIZE
Type a slash · pick from the menu.
/init
First command in any new repo
/compact
When Claude slows · compress history
Model picker
Sonnet fast · Opus smart
/ultraplan
Forces a plan before any code
/ultrareview
Second-opinion review on your work
Three checks · five commands · now you have Claude Code's whole keyboard.
↩ HOME Session 3 · Slide 16/17
Take these with you · ship by Saturday.
Three actions · one Slack post · we're back together June 13.
★ DO 1
Ship one edit
Any agent · any surface.
Claude Code · OR Cowork · OR your
Gem · OR your CoS · OR Routine.
One edit · screenshot · share.
★ DO 2
Run CLEAR on it
5 checks · 5 minutes.
Consent · Limits · Explainable ·
Auditable · Reversible.
Note any check you can't pass.
★ DO 3
Post your rung
In Slack · which Category.
Cat 1 deterministic · Cat 2
reasoning + acting · Cat 3 multi.
We pair you up before S4.
★ PICK YOUR RUNG · CALLBACK FROM SESSION 2
CATEGORY 1
Deterministic
automation
Zapier · Power Automate · light LLM step.
CATEGORY 2
Reasoning +
acting agent
CoS · Gem · Copilot Agent · Routine.
CATEGORY 3
Multi-agent
network
Next session · the kitchen line.
★ RESOURCES · ALL FOUR USE CASES
globalpeoplelabs.com/resources · CoS · JD AI-Native · Build a Skill · Build a Routine · pick one · fork it.
By Session 5, we will all have shipped this same JD tool together.
See you in Slack · then Saturday June 13 at noon.
↩ HOME Session 3 · Slide 17/17
SESSION 3 DECK · COHORT 2
Cohort 2 is in the room.Session 3 — Make it safe to ship. These slides walk through it live with Q & Sandhiya. Cohort members sign in to open the deck; everyone else: catch Cohort 3.
ALREADY IN COHORT 2?
Welcome back. The deck loads behind the sign-in.
SIGN IN WITH YOUR INVITE →
WATCHING FROM OUTSIDE?
Cohort 3 opens later this summer. We'll save you a seat.
CATCH COHORT 3 →