How to Use Claude Skills to Turn Handwritten Shift Notes Into a Clean Manager Handoff Report

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 manager handoff 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

At close, people write fast. Shift notes are often incomplete, handwritten, and scattered across a prep sheet, a stock note, a whiteboard reminder, and a few texts. The next manager still needs one clean handoff that says what happened, what needs attention first, and what can wait.

This workflow is for local business owners, clinic admins, studio managers, front-desk leads, and service operators who inherit messy end-of-shift notes and need a clean manager handoff report.

What skill you will use in this workflow

You will build a private custom Skill called manager-handoff-report. Its job is to turn handwritten shift notes, closeout scraps, text reminders, and stock notes into a structured handoff with incidents, staffing, inventory, facilities, and next priorities.

This task deserves a Skill because the categories should stay consistent across shifts. A manager should not have to remember the right prompt every night, and the next manager should not have to decode a different report shape each morning.

Before using the Skill, prepare clear photos of the notes, any related typed messages, and a short location context note with the site, shift date, next opening time, and any house shorthand.

Prerequisites

• Claude with Skills available and code execution enabled.
• Photos of handwritten shift notes, closeout sheets, stock reminders, or whiteboard notes.
• Any related text messages or quick typed notes you want included.
• A short location-context.txt file with site name, shift date, next opening time, and business-specific shorthand.
• A manager who can verify unclear handwriting, incidents, counts, staffing notes, and time-sensitive follow-ups.

How to gather the source material

1. Take clear photos in good light. Fill the frame with the note.
2. If there are multiple pages, number them in the file names.
3. Paste any related texts into one note file instead of giving Claude ten separate screenshots.
4. Make one file called location-context.txt with the site name, shift date, next opening time, and any unusual context for the next manager.
5. If a shorthand term is unique to your business, add a small glossary at the bottom of location-context.txt.
6. Mark anything you already know is hard to read. The Skill should keep unreadable or uncertain items visible instead of guessing.

Build the custom skill for this workflow

Create a folder named manager-handoff-report. Inside it, create a file named Skill.md. Paste the starter Skill below, then edit it so it matches your business categories, escalation language, and manager handoff style.

When the folder is ready, ZIP the folder itself so the ZIP file contains manager-handoff-report/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: manager-handoff-report
description: Turn handwritten shift notes, closeout scraps, and stock reminders into a clean manager handoff report with incidents, staffing notes, inventory issues, facilities issues, and next priorities.
---

# Manager Handoff Report

Use this skill when the user wants to turn messy shift notes into a manager handoff report.

## Required sections
- Incidents
- Staffing notes
- Inventory or supply issues
- Facilities or maintenance issues
- Next priorities

## Guardrails
- Keep uncertain or unreadable items visible.
- Do not soften serious incidents.
- Do not invent causes or resolutions.
- Write for the next manager, not for marketing.

## Examples
- Turn these handwritten shift notes into a clean manager handoff report.
- Use my manager handoff workflow on these closeout notes.
- Draft a shift handoff report and flag anything unreadable.

Optional official Anthropic skill

Anthropic's official internal-comms skill is the closest public reference because a manager handoff is an internal operational update. It can be useful if you want a general model for concise internal communication.

Use the private manager-handoff-report Skill for the actual workflow when your business needs house categories, manager-specific phrasing, escalation rules, opening priorities, or fixed language for incidents and facilities issues.

Skill-creator helper

Anthropic's official skill-creator skill 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 clean up one shift note. A custom Skill is better when the same handoff categories repeat every day: incidents, staffing, inventory, facilities, and next priorities. It lowers prompt rewrite friction and keeps unreadable notes visible instead of letting a rushed prompt accidentally hide them.

Skill trigger test

After enabling manager-handoff-report, test it with a small sample before the first production run. Use one handwritten note photo, one stock reminder, and a short location-context.txt.

Try prompts like:

• Turn these handwritten notes into a clean manager handoff report.
• Use my handoff workflow and keep unreadable items visible.
• Draft a manager handoff from these notes and stock reminders.
• Create a next-manager report with incidents, staffing, inventory, facilities, and next priorities.

If Claude does not appear to use the Skill, revise the Skill description so it clearly mentions shift notes, manager handoffs, incidents, staffing notes, inventory issues, facilities issues, and next priorities.

Numbered workflow steps

1) Gather and clean the source material

Create a source package with three parts:

• Clear photos of handwritten shift notes, closeout sheets, stock reminders, or whiteboard notes.
• One text file with related messages, if any.
• location-context.txt with site name, shift date, next opening time, and business-specific shorthand.

Crop out private information that does not belong in the report. If handwriting is hard to read, add a typed note or flag the area for review rather than expecting Claude to reconstruct it.

2) Create or enable the custom Skill

If this is your first run, create and upload manager-handoff-report 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 shift material, not an old handoff.

3) Run a quick trigger test

Before the full run, upload a small mixed sample of shift notes and ask:

Use my manager handoff workflow on this small sample. Draft a report with incidents, staffing, inventory or supplies, facilities or maintenance, and next priorities. Keep unreadable or uncertain items visible.

Check that Claude creates the expected categories, keeps serious incidents direct, and does not invent causes, resolutions, counts, or ownership.

4) Run the actual workflow with the Skill active

Attach the full set of note photos, related text notes, and location-context.txt. Ask Claude:

Use manager-handoff-report to turn these handwritten shift notes, closeout scraps, and stock reminders into a clean manager handoff report. Group items into incidents, staffing notes, inventory or supply issues, facilities or maintenance issues, and next priorities. Keep unreadable or uncertain items visible for review.

The useful output should tell the next manager what needs attention first without burying them in the full mess of the shift.

5) Review the report before handoff

Do a manager review before sharing. Check:

• Do names, counts, product names, times, and location details match the source notes?
• Are unreadable or uncertain items still visible?
• Are serious incidents stated plainly without being softened?
• Did Claude avoid inventing causes, resolutions, blame, or ownership?
• Are the next priorities truly next-shift actions?

If something is unclear, leave it marked for review rather than rewriting it as a fact.

6) Save, send, or reuse the result

Save or send the approved report where managers already look for handoffs, such as the operations log, team chat, manager email, or opening checklist folder.

If the format works, keep manager-handoff-report enabled and reuse it for daily or weekly shift handoffs. Update the Skill when your categories, escalation rules, or manager expectations change.

Tool-specific instructions

Claude Skills

Use manager-handoff-report as the main workflow tool. The Skill should encode your handoff categories, serious-incident handling, unreadable-note policy, manager-facing tone, and opening-priority rules.

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.

Official public skill reference

The internal-comms public Skill is a useful reference for concise internal communication patterns. It is not a substitute for your private handoff Skill because it does not know your house categories, shift rhythm, escalation rules, or manager phrasing.

Quality checks

1. Every count, item name, and time matches the source note or remains marked uncertain.
2. The first-priority items are truly next-shift actions, not a full replay of the entire day.
3. Unreadable or unclear text remains visible instead of being guessed at.
4. Serious incidents are not softened or buried.
5. The report does not invent causes, resolutions, blame, or ownership.
6. The report is short enough that a manager could scan it in under two minutes.

Common failure modes and fixes

The report repeats trivial details

Fix: tell Claude to keep only items that affect the next shift, inventory, staffing, facilities, incidents, or customer service.

Handwriting causes bad extraction

Fix: retake the photo closer, crop tighter, or manually type only the unreadable line.

Claude hides uncertain notes

Fix: revise the Skill guardrails so [UNREADABLE], [UNCLEAR], or Needs manager review items stay in the final report.

Claude sounds too formal for store ops

Fix: ask for plain operational language and one short paragraph or bullet block per section.