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

Warning: Student feedback can contain identifying details and emotionally charged comments. Remove anything you should not upload, and keep the output tied to the actual comments instead of one loud outlier.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

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 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 teaching-improvement memo without hand-sorting every comment from scratch.

Prerequisites

• Claude with Skills available.
• A feedback export from your LMS, survey tool, or spreadsheet.
• A short note on the course, term, and what you changed this semester.
• A decision on whether you want anonymous quoting or comment paraphrases only.

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, and any major teaching changes you made that term.

Numbered workflow steps

1) Extract patterns before you try to write the memo

The internal-comms pattern is useful here because you need a stable summary format, not a freeform brainstorm. Ask Claude to sort comments into signals, edge cases, and actionable themes before it writes anything polished.

{
  "task": "Extract teaching-improvement themes from course feedback for a Keep, Change, Try memo",
  "input": {
    "feedback_export": "ATTACH CSV, XLSX, DOCX, PDF, or TXT",
    "context_note": "PASTE feedback-context.txt"
  },
  "rules": [
    "Group similar feedback into themes.",
    "Separate repeated themes from one-off comments.",
    "Quote only short excerpts when they add clarity.",
    "Mark any weak-signal theme as [LOW CONFIDENCE].",
    "Do not write recommendations yet."
  ],
  "output": {
    "keep": "Practices students consistently valued",
    "change": "Patterns that suggest a real problem or friction point",
    "try": "Reasonable experiments suggested by the feedback",
    "outliers": "Strong but isolated comments that should not drive the memo alone",
    "evidence_notes": "Short note on why each theme belongs in its section"
  }
}

2) Review the extracted material before Claude writes the final deliverable

Read the grouped output once before Claude drafts the memo. Move anything that feels speculative into outliers or low-confidence notes. Add a human note if there is important context the student comments do not show, such as a policy change or a technology outage that affected the course.

3) Draft the final deliverable

{
  "task": "Write a Keep, Change, Try teaching memo from verified feedback themes",
  "input": {
    "verified_theme_output": "PASTE THE REVIEWED OUTPUT FROM STEP 1",
    "audience": "Instructor or teaching team",
    "tone": "direct, reflective, practical"
  },
  "rules": [
    "Keep the memo under one page unless the user asks otherwise.",
    "Use clear headings: Keep, Change, Try.",
    "Tie each section back to the evidence notes.",
    "Do not invent student motives or emotional states.",
    "End with 3 to 5 concrete next-semester actions."
  ],
  "output_format": {
    "type": "memo"
  }
}

4) Save the output where you actually work

Keep the final deliverable in the same folder as the source package, or paste it into the system you already use. The value here is repeatability. Once your source files and section order are stable, the next run gets much faster.

Tool-specific instructions

Use Claude Skills as the main engine here because the value is repeatability. A good private skill can keep your preferred memo length, tone, and section order stable across semesters. The public internal-comms skill is the best pattern reference because it is built for structured internal summaries, FAQs, and updates instead of loose ideation.

Quality checks

1. Each Keep, Change, or Try item can be traced back to actual comments or ratings in the source file.
2. One intense comment did not become a headline unless the evidence really supports it.
3. The memo ends with changes you could realistically make before the next term.
4. 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 comment counts or rough frequency for each theme before drafting the memo.

The output is too vague to be useful

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

The export is too messy

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

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: Creating custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-creating-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Claude Cowork, file handling, plan availability, and setup paths.