How Educators Can Use Claude Skills to Turn Course Feedback Into a Keep, Change, Try Memo

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 Keep, Change, Try memo 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

End-of-course feedback is usually messy. You may have LMS exports, copied comments, a spreadsheet, and your own memory of what actually happened during the term. The job is not to summarize everything. The job is to turn that pile into a short Keep, Change, Try memo you can actually use when you revise the course.

This workflow is for teachers, faculty, course directors, instructional coaches, and program leads who want a clean reflection memo without hand-sorting every comment from scratch or overreacting to one intense comment.

What skill you will use in this workflow

You will build a private custom Skill called course-feedback-reflection-memo. Its job is to group repeated feedback themes, separate outliers from stronger patterns, and draft a practical Keep, Change, Try memo.

This task deserves a Skill because course reflection repeats every term, cohort, or workshop cycle. The Skill keeps the same section order, evidence rules, outlier handling, and no-overreaction guardrail available each time.

Before using the Skill, prepare the raw feedback export, any rating columns that help show frequency, and a short context note about the course, class size, term, and major changes you made.

Prerequisites

• Claude with Skills available and code execution enabled.
• A feedback export from your LMS, survey tool, or spreadsheet.
• A short note on the course, term, class size, student level, and what changed this semester.
• A decision on whether you want anonymous short quotes or paraphrases only.
• A human reviewer who will decide which course changes are actually appropriate.

How to gather the source material

1. Export the raw comments from your LMS or survey tool. CSV is fine. XLSX is fine too if that is what the platform gives you.
2. If the export includes rating columns, keep them. They help you spot whether a comment reflects a broader pattern or one isolated complaint.
3. Delete columns that do not matter for this memo. Example: internal IDs, timestamps down to the second, and technical survey metadata.
4. If the comments live in multiple files, merge them into one sheet or one plain text document before you start. A simple copy-paste into a single DOCX or TXT file is enough.
5. Add a short note called feedback-context.txt with the course name, student level, class size, term, and any major teaching changes you made.
6. Remove names and identifying details unless your institution has a clear approved reason to keep them.

Build the custom skill for this workflow

Create a folder named course-feedback-reflection-memo. Inside it, create a file named Skill.md. Paste the starter Skill below, then edit it so it matches your course context, memo length, tone, and review rules.

When the folder is ready, ZIP the folder itself so the ZIP file contains course-feedback-reflection-memo/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: course-feedback-reflection-memo
description: Turn raw course feedback into a Keep, Change, Try memo that groups themes, highlights outliers, and avoids overreacting to one comment.
---

# Course Feedback Reflection Memo

Use this skill when the user wants to turn raw course or workshop feedback into a Keep, Change, Try memo.

## Output shape
- Keep
- Change
- Try
- Outliers or low-confidence observations

## Guardrails
- Group repeated themes before drafting recommendations.
- Do not overreact to one isolated comment.
- Keep evidence-based reasoning visible.
- Treat the memo as a reflection tool for the instructor.

## Examples
- Turn this course feedback into a Keep, Change, Try memo.
- Use my reflection workflow on these student comments.
- Group themes, highlight outliers, and draft a practical memo.

Skill-creator helper

Do not force a public Skill into this workflow. The closest useful official reference 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 produce a decent memo once. A custom Skill is better when you want the same reflection structure every term: Keep, Change, Try, plus outliers and low-confidence observations. It also reduces the chance that you forget to ask Claude to group themes before making recommendations.

Skill trigger test

After enabling course-feedback-reflection-memo, test it with a small sample before processing the full feedback export. Use five to ten comments plus your feedback-context.txt.

Try prompts like:

• Turn this course feedback into a Keep, Change, Try memo.
• Use my reflection workflow and separate repeated themes from outliers.
• Draft a course-improvement memo without overreacting to one comment.
• Group these student comments into Keep, Change, Try and show low-confidence observations separately.

If Claude does not appear to use the Skill, revise the Skill description so it clearly mentions course feedback, Keep, Change, Try, repeated themes, outliers, and no-overreaction handling.

Numbered workflow steps

1) Gather and clean the source material

Create a source package with three parts:

• course-feedback-export.csv or another export file with comments and ratings.
• feedback-context.txt with course name, term, class size, student level, and major teaching changes.
• Optional notes on constraints, such as required curriculum, platform changes, staffing limits, or policies that affected the course.

Remove identifying details and trim irrelevant metadata. Keep rating columns or counts when they help distinguish repeated themes from isolated comments.

2) Create or enable the custom Skill

If this is your first run, create and upload course-feedback-reflection-memo 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 feedback package, not an old course discussion.

3) Run a quick trigger test

Before the full run, paste a small sample of comments and ask:

Use my reflection workflow on this small course feedback sample. Group repeated themes, separate outliers, and draft a short Keep, Change, Try memo without overreacting to one comment.

Check that Claude produces the four expected areas: Keep, Change, Try, and outliers or low-confidence observations. The test should also show evidence notes rather than turning every comment into a recommendation.

4) Run the actual workflow with the Skill active

Attach or paste the full feedback export and feedback-context.txt. Ask Claude:

Use course-feedback-reflection-memo to turn this course feedback into a Keep, Change, Try memo. Group repeated themes before drafting, keep outliers separate, show evidence-based reasoning, and treat the memo as a reflection aid rather than an automatic course decision.

The useful output should help you see what is worth keeping, what may need change, what is safe to try, and what is too thin or isolated to drive a decision by itself.

5) Review the memo with human judgment

Read the memo before you make course changes. Check:

• Does each Keep, Change, or Try item trace back to actual comments, ratings, or context?
• Did Claude keep isolated comments separate unless they reveal a serious issue?
• Are student quotes short, anonymous, and necessary?
• Are recommendations realistic for the next term or workshop cycle?
• Does the memo avoid inventing student motives, emotions, or causes?

The memo is a reflection aid, not an auto-decision engine. You still decide what to change, what to keep, and what to test.

6) Save, share, or reuse the result

Save the memo beside the feedback export and your course planning notes. If you share it with a teaching team, remove student-identifying details and keep outliers labeled as outliers.

Before the next term, revisit the Skill and feedback-context.txt so the same reflection format can support the next course update.

Tool-specific instructions

Claude Skills

Use course-feedback-reflection-memo as the main workflow tool. The Skill should encode the memo sections, grouping rules, outlier handling, evidence notes, and no-overreaction guardrail.

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. Each Keep, Change, or Try item can be traced back to actual comments, ratings, or context in the source package.
2. One intense comment did not become a headline unless the evidence really supports it.
3. Outliers and low-confidence observations are labeled instead of hidden.
4. The memo ends with changes or experiments you could realistically consider before the next term.
5. The memo does not invent student motives, emotional states, or causes.
6. Any quoted student language is short, anonymous, and necessary.

Common failure modes and fixes

The memo overreacts to one negative comment

Fix: ask Claude to show rough frequency, rating support, or the number of comments behind each theme before drafting recommendations.

The output is too vague to be useful

Fix: add a final instruction that every Change and Try item must end with one concrete next review point or possible next-semester action.

The export is too messy

Fix: trim the sheet first. You do not need every metadata column for this workflow.

The memo turns feedback into automatic decisions

Fix: revise the Skill guardrails so recommendations are framed as reflection options for the instructor, not mandatory course changes.