Picture a Sunday phone call. A mom on one end, her kid on the other, and a question that half the planet is quietly asking too: “What the hell is Claude?”
That’s the exact scene this LinkedIn creator opened with, and I couldn’t stop reading. Instead of burying her in jargon, the author translated Claude into everyday language and walked his mom through six confusions, one at a time. By the end, she was calling back just to say “witchcraft.” I think it’s the best beginner’s guide to Claude I’ve seen, and it wasn’t even written for beginners. It was written for one very skeptical parent.
The story builds like a good drama. Each lesson starts with a frustrated question, the kind you’ve probably heard from a parent, a boss, or a friend. Each one ends with a tiny win. Let me walk you through how the original poster resolved them.
Lesson 1: “What do I type in the prompt box?”
The blank box is where most people freeze. You open Claude, the cursor blinks, and suddenly you don’t know how to talk to a machine. The author’s mom hit that wall immediately.
His fix was a single template. Copy it and fill in your own context:
“I want to [TASK] for [RESULT]. AskUserQuestion.”
That last word does the heavy lifting. Claude responds with 3 to 5 clarifying questions, and you just tap the answers. No prompt engineering, no guessing what the model needs. According to the post’s author, his mom never asked about prompting again. I love this because it flips the dynamic: instead of you figuring out what to say, Claude interviews you.
Lesson 2: “You expect me to type all that?”
Fair pushback. Nobody wants to type three paragraphs of context on a laptop keyboard. The expert’s answer was simple: don’t type, talk.
He pointed her to Wispr, a free voice-to-text app. You speak roughly 4x faster than you type, so a rambling two-minute explanation becomes a rich prompt with zero effort. The author jokes that his mom speaks closer to 400x. Sorry, mom.
Practical tip from me: voice input pairs beautifully with the template above. Say “I want to plan a two-week trip to Portugal for my parents’ anniversary, ask me questions,” and let Claude take it from there.
Lesson 3: “Where did my file go?”
This one hits home. You upload a document, get a result, and then have no idea where anything lives. The tension here is real for anyone who’s ever lost a download.
The creator’s instructions were short:
- Open the Claude desktop app
- Locate “cowork”
- Open “Projects” and upload all your files there
His mom dropped in a messy PDF. She got back a clean Excel file, saved on her own computer. And the best part, in my opinion: she found it herself. No follow-up call needed.
Lesson 4: “What the hell is a Claude skill?”
The author admits this is a fair question. His definition is the clearest I’ve read: a skill is a long prompt turned into a Claude command that runs on its own, every single time.
Think of it as a saved recipe. Instead of re-explaining how you want your weekly report formatted, you build it once as a skill and Claude follows it automatically. The catch is that building a solid library from scratch takes weeks of trial and error.
Once you do have a skill file (they come as a zip), installing takes about 2 minutes. Go to Claude, open Customize, choose Skills, then Upload. That’s it. After that, your Claude behaves consistently instead of starting from zero each session.
Lesson 5: “It’s reading my emails??”
Cue the horror-movie music. This is the moment in the story where trust gets tested, and the original poster handled it honestly: only if you let it.
Claude can connect to Gmail, your calendar, and meeting notes, but you control every connection. His mom’s first test after connecting was one line: “prep me for tomorrow’s meeting.” Claude pulled the relevant emails, the calendar entry, and any notes, then handed her a briefing.
That’s when she called back to say “witchcraft.” I had the same reaction the first time I saw meeting prep done this way. It’s the kind of feature that turns a curious user into a daily one.
Lesson 6: “Why did nobody tell me this?”
This is the resolution, and it’s the line that stuck with me. The author’s answer: because 98.75% of people have never tried Claude. Everyone’s waiting to feel ready.
She skipped the waiting. So can you.
That’s the whole arc in one sentence. The gap between “I’m so behind” and “witchcraft” wasn’t talent or technical skill. It was one afternoon and six plain-language answers.
How to use this yourself
If someone in your life keeps saying they’re behind on AI, this post is a ready-made script. My suggestion:
- Start with Lesson 1. The template removes the scariest part, the blank box.
- Add voice on day two. Typing is the hidden friction that makes people quit.
- Save Lesson 5 for last. Connecting email is the “wow” moment, but only after trust is built.
- Let them find their own file. Small independent wins are what make it stick.
The mind behind this post didn’t teach his mom AI. He removed six reasons to say no. That’s a skill worth copying, whether you’re helping a parent, a colleague, or yourself!
Head over to the full LinkedIn post to see the original six lessons exactly as the author wrote them, and send it to the one person who keeps saying “I’m so behind.”