How Educators Can Use Claude Skills to Turn a Rubric and Student Drafts Into Consistent Feedback Comments

Warning: Do not upload student work into a tool your school has not approved. Remove names if needed, and never let the draft comments replace your actual academic judgment.

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

Giving writing feedback takes time, and the real difficulty is consistency. The first paper gets detailed comments. The eighth paper gets shorter comments because your energy is lower. A reusable Claude Skill can help by keeping the comment structure stable while you stay in control of the grade and the final call.

This workflow is for teachers, faculty, tutors, and writing coaches who already use a rubric and want faster, more even feedback across a stack of drafts.

Prerequisites

• Claude with Skills available.
• The assignment brief and the grading rubric in text, DOCX, or PDF.
• Student drafts in DOCX or PDF. If you only have scans, run OCR first so the text is selectable.
• A short note on your preferred feedback voice. Example: concise margin notes plus one end comment.

How to gather the source material

1. Save the rubric as a clean text file or DOCX. If it only exists in a slideshow or a scan, copy it into a simple text document first.
2. Save the assignment prompt in the same folder so Claude can distinguish between rubric criteria and actual task requirements.
3. Convert any locked or image-only PDFs into searchable text before you start. If you can highlight the words, Claude will have a much easier time.
4. Create one small file called feedback-style.txt with the comment style you want. Example: one strength, one concern, one revision priority, and one sentence of encouragement.
5. Work one student draft at a time unless you are creating reusable comment banks by pattern.

Numbered workflow steps

1) Extract rubric-aligned evidence from the draft before writing comments

The doc-coauthoring pattern fits this task because it separates context gathering from the final writing pass. Claude should first map the draft against the rubric, then write comments from that map.

{
  "task": "Map a student draft to the grading rubric before writing feedback comments",
  "input": {
    "assignment_prompt": "ATTACH OR PASTE",
    "rubric": "ATTACH OR PASTE",
    "student_draft": "ATTACH OR PASTE",
    "feedback_style": "PASTE feedback-style.txt"
  },
  "rules": [
    "Use the rubric as the scoring frame.",
    "Pull specific evidence from the draft for each major criterion.",
    "Separate strengths, concerns, and revision priorities.",
    "Do not assign a final grade unless the user explicitly requests it.",
    "Flag any missing evidence as [NEEDS HUMAN REVIEW]."
  ],
  "output": {
    "criterion_map": "Rubric criterion by criterion evidence map",
    "strengths": "What the student is already doing well",
    "concerns": "Main gaps or weaknesses",
    "revision_priorities": "Top changes that would improve the next draft",
    "unclear_points": "Items that need human judgment"
  }
}

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

Review the criterion map before you let Claude write comments. This is where you catch overconfident interpretations, especially in creative assignments or nuanced arguments where a model might flatten your judgment.

3) Draft the final deliverable

{
  "task": "Write consistent teacher feedback comments from a verified rubric map",
  "input": {
    "verified_rubric_map": "PASTE THE REVIEWED OUTPUT FROM STEP 1"
  },
  "rules": [
    "Write comments in the teacher's preferred feedback style.",
    "Keep comments specific and text-grounded.",
    "Avoid generic praise or generic criticism.",
    "Do not promise a final grade unless the user asked for one.",
    "End with the student's top two revision priorities."
  ],
  "output_format": {
    "type": "feedback_comments"
  }
}

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 to keep your rubric logic and comment format stable across many drafts. The public doc-coauthoring skill is the best pattern reference because it explicitly separates context gathering, structured refinement, and reader testing. That mirrors how careful feedback should work.

Quality checks

1. Each major comment points to evidence in the draft, not generic writing advice.
2. The tone matches how you actually talk to students.
3. The comments do not quietly assign a final score you did not mean to give.
4. Revision priorities are limited enough that a student could act on them.

Common failure modes and fixes

The comments sound generic

Fix: give Claude a tighter feedback-style file and require text-grounded evidence under each criterion.

Claude overstates a weakness

Fix: require an evidence quote or section reference for each concern before the final comment pass.

The rubric is too broad

Fix: rewrite the rubric into plainer criterion labels before using the 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: doc-coauthoring skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/doc-coauthoring

Quarterly Refresh Flag

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