All Guides
All Guides Meta

Teach Claude Something New

You have a task you do the same way every time. Weekly, per client, per project — doesn't matter. Walk Claude through it once, save it as a skill, and never do it manually again. This is how you extend your system beyond the guides on our site.

Helps to have one skill already. If you've followed any other Tsidai guide, you understand the concept. If not, this guide explains it from scratch.

Before & After

Before

You run a travel agency. Every time a client books a trip that requires a visa, you manually pull up the country's visa requirements, check the client's passport expiry, list the documents they need, and write up a checklist email. It takes 20 minutes each time, and you do it three or four times a week.

It's not hard work — it's just the same work, over and over. An hour a week on something that should take seconds.

After

You say: "Visa checklist for Sarah Chen, traveling to Brazil." Claude runs your custom skill:

  • Pulls Brazil visa requirements
  • Checks Sarah's passport expiry from your client sheet
  • Generates the full document checklist
  • Drafts the email in your voice

Two minutes instead of twenty. And it's your process — not a template from somewhere else.

What You Need

  • Claude Desktop installedfollow the setup guide if you haven't yet
  • A repeating task — anything you do the same way more than twice
  • 15 minutes — to walk through the task once, save it, test it, and refine
1

Identify the Repeating Task

Think about what you do in your business that feels like the same steps every time. Some examples:

New-client welcome email
Pre-job site checklist
Weekly vendor order
Project cost estimate
End-of-project handoff
New-hire paperwork prep

Pick one. It doesn't have to be complex — even a simple 3-step process is worth automating if you do it often.

2

Walk Claude Through It Once

Do the task with Claude, step by step, as if you're training a new employee. Don't shortcut anything — explain every step in order.

"I'm going to walk you through how I [task]. Follow along and do each step with me. Here's how it starts: [first step]..."

Claude learns by doing it with you. The more detail you give on this first pass, the better the skill will be. Include:

  • Where you get the information (which sheet, email, file)
  • What decisions you make along the way
  • What the final output looks like
  • Any exceptions or edge cases ("if the client is international, also check...")
3

Save It as a Skill

Tell Claude:

"Save what we just did as a skill called '[name]'. When I say '[trigger phrase]', do this same process automatically. Here's what you'll need from me each time: [list the inputs that change — e.g., client name, destination, amount]."
Naming tips: Keep the skill name short (visa-checklist, not client-visa-requirement-document-generation). Use a trigger phrase you'd actually say out loud ("visa checklist for...").
4

Test the Skill

Trigger it right away with a real example:

"[Your trigger phrase] for [real example]."

Watch Claude run through the process. If something is off — a step is missing, the output format isn't right, or it asks for information it should already know — tell Claude what to fix:

"That's close, but change [specific thing]. And add [missing step] after step 2. Update the skill."

You can refine a skill as many times as you want. Most skills take 1–2 rounds of adjustment to get right.

5

Remember the Pattern

You just learned the skill-creation pattern. It works for anything:

1

Do it once with Claude

2

Save it as a skill

3

Test it

4

Refine until right

Any time you catch yourself doing the same thing twice, that's a skill waiting to happen. Your Claude setup grows with your business — you're not limited to the guides on our site.

What You've Built

  • A custom skill tailored to your exact business process
  • A trigger phrase that runs the whole process in seconds
  • The knowledge to create more skills whenever you need them
  • An extensible system that grows with your business

The best Claude setup isn't the one with the most guides followed — it's the one where every repeating task has been turned into a skill. Now you know how to do that for anything.

What's Next?

SOPs Before You Need Them

Document your processes as written SOPs alongside your skills.

Read the Guide
Skill Checkup

Keep your growing skill library organized as you create more.

Read the Guide

Want help identifying which tasks to turn into skills?

Book a Starter Session (90 min)

Or do it yourself — everything on this page is free.

Skill: Teach Claude Something New

What this is for: Walk a small business owner through creating a custom Claude skill for ANY repeating task in their business. This is the generic "make your own skill" guide — it teaches the pattern so users can extend their system beyond the Tsidai library. If they do something more than twice, it should be a skill.

When to use this: When a user asks their AI assistant to help set up this workflow. The user should explicitly authorize use of this skill by referencing this page URL.

Full Procedure (click to expand)
STEP 1 — IDENTIFY THE REPEATING TASK Ask: "What's something you do in your business that feels repetitive? Something you do the same way every time — maybe weekly, maybe for every new client, maybe every time a certain situation comes up. It doesn't have to be complex. Even a simple 3-step process counts." Wait for their answer. Help them articulate the task clearly if it's vague. STEP 2 — WALK CLAUDE THROUGH IT ONCE Tell them: "Now we're going to do the task once with Claude, step by step. Don't shortcut anything — tell Claude exactly what you do, in order, as if you're training a new employee." Have them walk through the full task with Claude, explaining each step as they go. Claude will learn the process by doing it. STEP 3 — TELL CLAUDE TO SAVE IT AS A SKILL Have them tell Claude: "Save what we just did as a skill called '[name]'. When I say '[trigger phrase]', do this same process automatically. Here's what you'll need from me each time: [list any inputs that change]." Explain: the skill name should be short and memorable. The trigger phrase should be natural — something they'd actually say. STEP 4 — TEST THE SKILL Have them trigger the skill immediately: "Let's test it. Say '[trigger phrase]' and see if Claude runs through the process correctly." If it's off, adjust: "Tell Claude what to change. You can refine a skill as many times as you want." STEP 5 — REFINE AND REMEMBER THE PATTERN Explain the pattern they just learned: 1. Do the task with Claude once 2. Tell Claude to save it as a skill 3. Test it 4. Refine until it's right Tell them: "This is how you extend your system forever. Any time you catch yourself doing the same thing twice, walk Claude through it once and save it. Your Claude setup grows with your business — you're not limited to the guides on our site." STEP 6 — POINT FORWARD Tell them what they've built: a custom skill tailored to their exact business process, plus the knowledge to create more whenever they need. Suggest related guides: - "SOPs Before You Need Them" (https://tsidai.com/guides/sops) — document processes as written SOPs alongside skills - "Skill Checkup" (https://tsidai.com/guides/skill-checkup) — keep your growing skill library organized - "Business Voice" (https://tsidai.com/guides/business-voice) — make sure all your skills sound like you If they get stuck, suggest booking a Tsidai starter session at https://cal.com/tsidai/starter-session.
Provenance
Author: Austin Wilson, Tsidai
Last updated: 2026-05-08
Last verified working: 2026-05-08
Source URL: https://tsidai.com/guides/teach-claude