marking

name

marking

description

Grade or review student assignments from course folders using assignment criteria, course outlines, rubrics, and grade sheets. Use when Codex is asked to mark essays, exams, coding assignments, problem sets, presentations, reports, projects, or whole assignment folders; create grade tables with student name, ID, mark out of 100, short comments, remarks about inaccessible content, and an overall marking report.

Marking

Overview

Mark student submissions by grounding every grade in the relevant assignment criteria, course outline, grade sheet, and submitted files. Preserve academic integrity: do not invent missing content, do not grade inaccessible evidence as if it were read, and make uncertainty visible in remarks.

Core Workflow

1. Identify the course, assignment, submission folder, and intended output location from the user's request and nearby files.
2. Locate the relevant course grade sheet and course outline before opening student work.
3. Find the specific assignment criteria first. If unavailable, fall back to the course's general grading criteria from the course outline.
4. Read the grade sheet for student names, IDs, existing grade ranges, and expected grade distribution.
5. Inspect each student's submission and grade against the located criteria and distribution.
6. Create a grade table containing Student Name, Student ID, Mark (100/100), Short Comment, and Remarks.
7. Mark any inaccessible, missing, corrupted, password-protected, unsupported, or unreadable assignment content in Remarks.
8. Generate an overall report after grading the assignment.

Resource Guide

Read references/marking-workflow.md whenever starting an actual marking task. It contains the required evidence hierarchy, folder-search approach, grading distribution checks, grade table schema, and report format.

For spreadsheet grade sheets, use the spreadsheet tooling available in the workspace. For .docx, .pptx, .pdf, code, notebooks, archives, images, or mixed submissions, use the appropriate document, presentation, PDF, code, archive, and visual-inspection tools rather than relying on filenames alone.

For .docx submissions with any visual component, do not rely on text extraction or a single media path. Render or inspect the document visually, and also inspect the DOCX package for images under word/media/, root-level media/, relationship image targets, and nonstandard image extensions such as .tmp that may still contain valid PNG/JPEG data. Treat "no embedded image found" as a finding only after these checks.

Marking Rules

• Prefer specific assignment criteria over course-level grading criteria.
• Use course-level criteria only when assignment-specific criteria cannot be found.
• Use the grade sheet as the authority for student identity, enrollment, and grade-distribution context.
• Base marks on observed evidence from submissions and criteria, not on expected quality, filenames, or inferred intent.
• Apply one consistent scale: convert all outcomes to Mark (100/100).
• Keep comments short, specific, and constructive.
• Preserve a clear audit trail of sources consulted and files that could not be accessed.
• Ask the user before making irreversible changes to original grade sheets; otherwise create a new grade table or report file.