How Educators Can Use Claude Skills to Turn Whiteboard Photos Into an Absent-Student Recap and Homework Sheet

If Claude Skills is new to you

Skills are reusable folders of instructions, resources, and optional scripts that Claude can load when a task matches the Skill description. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you only need the basics: create a folder with a Skill.md file, ZIP the folder, upload it in Claude under Customize > Skills, enable it, and test that Claude routes absent-student recap requests to the Skill. The Claude Skills tool hub is useful further reading, but the setup steps you need are included below.

Problem and who this is for

You finish teaching, a student was absent, and now you need a clean recap before the day gets away from you. The board is full, your own notes are half-legible, and the homework directions changed mid-class. A reusable Skill can turn those messy inputs into a stable recap and homework sheet in minutes.

This workflow is for classroom teachers, tutors, small-group instructors, and coaches who need a same-day recap for a student, family, or class portal without rewriting the same structure every time.

What skill you will use in this workflow

You will build a private custom Skill called absent-student-recap. Its job is to turn whiteboard photos and rough teacher notes into a brief student-friendly handout with lesson focus, classwork, homework, materials, and confirmation-needed items.

This task deserves a Skill because the output shape should stay the same each time an absent student needs a recap. The Skill keeps the same sections, tone, and uncertainty rules available across classes, while still letting the teacher check the final details.

Before using the Skill, prepare one clean whiteboard photo, any worksheet or slide image that matters, and a short teacher note with the class, date, final homework wording, and anything the board does not show.

Prerequisites

• Claude with Skills available and code execution enabled.
• A phone photo of the board, slide, worksheet, or handout.
• Your own short teacher note with anything the photo does not show clearly.
• The final homework wording, especially if it changed during class.
• A decision on whether the recap is for the student, the family, or your internal class portal.

How to gather the source material

1. Take the photo straight on, in good light, and close enough that the writing is readable. If you need two photos, take two rather than one blurry wide shot.
2. Crop out student names, grades, seating notes, and side notes that should not leave your phone.
3. If the board content spans multiple photos, upload all of them in one pass or combine them into a simple PDF.
4. Create a short text note called class-context.txt with the course, lesson date, intended audience, and anything the board does not capture, such as oral reminders or changed deadlines.
5. If homework was on paper, snap that too or paste the exact assignment directions into class-context.txt.
6. Label anything you are unsure about before asking Claude to draft. The Skill should preserve uncertainty instead of guessing.

Build the custom skill for this workflow

Create a folder named absent-student-recap. Inside it, create a file named Skill.md. Paste the starter Skill below, then edit it so it matches your class level, preferred tone, and handout format.

When the folder is ready, ZIP the folder itself so the ZIP file contains absent-student-recap/Skill.md at the root. In Claude, open Customize > Skills, upload the ZIP file, and enable the Skill before you run the workflow.

Use this as a starting template, not a perfect final Skill:

---
name: absent-student-recap
description: Turn whiteboard photos and rough class notes into an absent-student recap with lesson focus, classwork, homework, and anything that still needs teacher confirmation.
---

# Absent Student Recap

Use this skill when the user wants to turn whiteboard photos and rough class notes into a recap for an absent student.

## Required sections
- What we covered
- What students did in class
- Homework or next step
- Materials needed
- Needs teacher confirmation

## Guardrails
- Do not guess unclear board text.
- Mark uncertain items instead of inventing them.
- Keep language student-friendly and brief.
- Treat the output as a teacher-reviewed handout.

## Examples
- Turn these whiteboard photos into an absent-student recap and homework sheet.
- Use my absent-student workflow on this board photo and note.
- Draft a student-friendly recap and flag anything unclear.

Skill-creator helper

Do not force a public Skill into this workflow. The useful official helper is Anthropic's skill-creator skill, which can help draft or refine your private Skill before you upload it. Review the generated files before enabling any Skill, especially if it includes scripts or bundled resources.

Why this should be a custom skill, not a one-off prompt

A one-off prompt can work for one absence, but this task repeats all term. A custom Skill keeps the same student-friendly sections, uncertainty labels, and homework accuracy rules available every time, so you do not have to rewrite the instructions after each class.

Skill trigger test

After enabling absent-student-recap, test it with one clean whiteboard photo and a short class-context.txt note before using it on a messy set of images.

Try prompts like:

• Turn this whiteboard photo into an absent-student recap.
• Use my absent-student workflow and keep unclear text visible.
• Draft a recap and homework sheet from this board image and note.
• Create a student-friendly recap, but put unreadable board text under Needs teacher confirmation.

If Claude does not appear to use the Skill, revise the Skill description so it clearly mentions whiteboard photos, absent-student recaps, homework sheets, unclear text, and teacher confirmation.

Numbered workflow steps

1) Gather and clean the source material

Create a source package with three parts:

• One or more cropped whiteboard, slide, worksheet, or handout photos.
• class-context.txt with course name, lesson date, intended audience, and final homework wording.
• Optional notes on materials students used in class, such as textbook pages, worksheet names, slide titles, or shared links.

Remove private student details before upload. If the board is hard to read, add a short teacher note rather than relying on Claude to recover unclear handwriting.

2) Create or enable the custom Skill

If this is your first run, create and upload absent-student-recap using the build steps above. If you already created it, open Claude's Skills settings and confirm the Skill is enabled before starting a new chat.

Use a fresh chat for the production run so the Skill starts from the current lesson material, not an old class recap.

3) Run a quick trigger test

Before the full run, upload one clean board photo and a short note. Ask:

Use my absent-student workflow on this board photo and note. Draft a brief recap and homework sheet, and put unclear board text or missing context under Needs teacher confirmation.

Check that Claude uses the expected sections, keeps the language student-friendly, and does not guess unclear board text.

4) Run the actual workflow with the Skill active

Attach the full set of board photos, handout images, and class-context.txt. Ask Claude:

Use absent-student-recap to turn these whiteboard photos and class notes into an absent-student recap and homework sheet. Include what we covered, what students did in class, homework or next step, materials needed, and anything that needs teacher confirmation. Do not guess unclear text.

The output should be short enough for an absent student to act on the same day.

5) Review the recap before delivery

Do a teacher review before sharing. Check:

• Is the homework exactly right?
• Are due dates, page numbers, problem sets, and submission directions accurate?
• Did Claude flag unclear board text instead of guessing?
• Does the recap include only material covered in class or stated in your note?
• Are private student details removed from the final handout?

Correct missing context yourself. The Skill should not invent homework, materials, lesson goals, or teacher instructions.

6) Save, send, or reuse the result

Save the approved recap in the same place you normally share makeup work, such as the LMS, class portal, email, or a student handout folder.

If this format works, keep absent-student-recap enabled and reuse it whenever a student misses class. Update the Skill if your class handout sections, tone, or homework format changes.

Tool-specific instructions

Claude Skills

Use absent-student-recap as the main workflow tool. The Skill should encode lesson focus, classwork, homework, materials, teacher-confirmation items, student-friendly tone, and the rule that unclear board text must stay visible.

Use the official skill-creator skill only as a helper for drafting or improving your private Skill. Treat the Claude Skills tool hub as further reading for broader setup context, not a prerequisite for this workflow.

Quality checks

1. The homework directions match what was actually assigned.
2. Due dates, page numbers, problem sets, and materials are correct.
3. The recap does not expose private student information from the whiteboard photo.
4. The language is simple enough that an absent student can act on it without follow-up.
5. Unclear details are labeled instead of guessed.
6. The recap does not add explanations or assignments that were not taught, assigned, or stated in the teacher note.

Common failure modes and fixes

The whiteboard photo is too messy

Fix: retake the photo or add a teacher note with the missing pieces. Do not expect Claude to recover unreadable handwriting perfectly.

Claude guesses unclear board text

Fix: revise the Skill guardrails so unclear text goes under Needs teacher confirmation every time.

The recap is too wordy

Fix: set a hard limit, such as one paragraph plus a short homework block.

Homework changed during class

Fix: always put the final homework wording in class-context.txt if the board was not updated.