Interactive learning session 2 — Chat, Cowork or Code?

Sightsavers · Cohort 2 · 2027

All three run the same Claude models — none is "smarter". What changes is where Claude can act, and how long it keeps going without you. This class you learn to pick the right hands for the job, and to stop retyping your best prompts by turning them into skills.

Every 2 weeks 90 minutes Google Meet Class 2 of 8

This page is part of the course. Everything here is interactive — switch languages at the top, pass the two skill checks, build a skill, and answer the questions about your own problem. Your progress is saved in your browser only.

1 · Same brain, different hands

The question is never "which one is best" — it is who does the follow-through work: you, or Claude.

Chat — talks it through with you

Think, draft, explain, analyse uploaded files, make quick artifacts. Can use connectors (MCP). You carry the results back to where the work lives.

Like a consultant on the phone.

Cowork — works in your files

Runs in the Claude desktop app. Reads, creates and reorganises files in a folder you choose, across documents, spreadsheets and slides. Plans, acts and checks while you do something else.

Like an assistant at your desk.

Code — builds and runs things

A tab in the desktop app, or the command line. Writes and runs scripts, builds web pages and automations that rerun next month without starting over. Awareness level for this course — no coding needed.

Like an engineer with keys to the workshop.

Read it like an ivermectin dose pole

The medicine is the same, and the dose goes up with the size of the job. Chat makes you the courier. Cowork does the errand. Code builds a machine that runs the errand again.

One plug, three sockets

Connectors (MCP) are shared plumbing: the same connector works in Chat, Cowork and Code. What differs is what the tool does with the data — an answer, a document on disk, or a pipeline that reruns. You will connect them yourself in session 4.

A word of safety

Cowork and Code change files. Practise on copies, never on real programme data — and when either tool asks permission before acting, read the whole message before you allow it.

2 · Which Claude for the job?

Two skill checks, straight from the live class. First: guess which tool produced each real output. Then: pick a tool for twelve programme scenarios — some have more than one defensible answer.

3 · Turn a prompt into a skill

You already know the pattern from session 1: refine a prompt until it reliably gives you what you want. A skill is that refined prompt, saved with a name and a trigger so Claude can use it again — and again — without being re-taught.

What a skill is

A skill is a small folder with a SKILL.md file inside: a name, a one-line description of when to use it, and the instructions that follow. Claude loads it when its job matches the description, so good descriptions matter more than clever instructions.

Skill builder — draft your first skill

Fill the three parts and watch the SKILL.md file assemble. Three sentences of instructions beat three paragraphs.


        
1

Make one from a prompt you already have

  1. Open your Claude project and reread your session 1 problem statement.
  2. Find one step in that problem you repeat every week or month — that repetition is your skill candidate.
  3. Take the prompt you use for it, fill the builder above, and copy the result.
  4. In Claude, ask: "Save this as a skill called [name]" and paste your SKILL.md. Then run the task once using the skill.
2

Borrow before you build

Skills are shared — search GitHub and the Claude skills directories for someone else's before writing your own. Read the SKILL.md first: a skill is instructions to an AI, so only use one whose instructions you could defend if asked. The red lines from session 1 still apply: never put restricted data into an untrusted skill.

4 · Your problem — which Claude, which skill?

Take the problem statement you drafted in session 1 and look at it with this session's eyes. Open answers — your instructors read them, so write for them.

Your problem statement from session 1

Paste in your problem statement.

Question 1 · Which Claude would you use for this problem — and why?

Pick a tool

Question 2 · Would a skill help? If so, for what?

Download your session 2 file

Your instructors review this file and give you feedback on Slack. It shows that you read the page, passed the skill checks, and what you answered above.

  • Question 1 · Which Claude not finished
  • Question 2 · Skills not finished
  • Full page · all sections read not finished

Some questions aren't finished yet — the file will show them as incomplete.

Saves a web page (.html). Open it in any browser to check it, then post it on Slack as your homework.

5 · Homework — due before Class 3

Three steps, all on Slack or in your Claude project.

1

Post your session 2 file

Upload it to your private channel, titled FirstNameLastName_Assignment2.

2

Run your skill once

Use the skill you drafted on your real problem, in your project, and post one line in the module channel about what worked or didn't.

3

Reply to one classmate

If their tool choice surprises you, say why — the debate is the exercise.

Quick answers

Do I need a paid plan or special access?

Chat works on what you already have. Cowork and Code need a Pro, Max, Team or Enterprise plan — check yours before class and flag it in your Slack channel if it is missing.

Do I need to know how to code?

No. Claude Code is awareness-level on this course: you should know what it is for and what it can build, but you will never be asked to write code yourself.

Can I work in French?

Yes. Write your answers in whichever language you think in; instructors read both. (This page toggles with EN/FR at the top.)