MATLAB Grader Instructor Setup Guide
Purpose
Generate a short instructor-facing setup guide for adopting the MATLAB Grader
Assessment Item Generator skill in a course, module, lab, assessment sequence, or
instructional-design workflow.
Treat the user's provided objective, course description, assessment goal, or
pilot request as the guide input. If the input is missing, ask for one sentence
describing the course, module, learning objective, or assessment context before
generating the guide.
Input Handling
Use the input to infer the best-fit setup context:
- introductory MATLAB programming;
- engineering computation or modeling;
- data analysis or visualization lab;
- object-oriented programming with MATLAB classes;
- graded homework, quiz, lab, project, or exam preparation;
- QTI 3 interchange, LMS review, or instructional-design sharing;
- mixed or uncertain context.
If multiple contexts fit, choose the primary context and add a short note about
secondary considerations. Do not ask follow-up questions unless the input is too
vague to identify an assessment goal.
Guide Workflow
- Restate the inferred learning objective or assessment goal.
- Identify the best-fit assessment context and why it fits.
- Recommend an assessment item type: Script, Function, Class, or Object usage.
- Recommend assessment purpose: formative, summative, or both.
When the context mapping has a purpose emphasis, use it.
Otherwise default to summative for graded or unspecified use, and both when
the module serves practice first with grading reuse later.
- Provide an instructor-ready generation prompt for the
matlab-generate-grader-assessments skill.
- Define review gates for
description.txt, solution.m, template.m,
function_call.m when the recommended type is Function, and tests.m.
- Define QTI 3 export and sharing guidance when portability is requested.
- Propose a first pilot with one generated item, one review pass, and one
revision loop.
- Include a concise instructor checklist.
Read references/setup-guide-template.md
for context mapping, output format, prompt patterns, and adaptation rules.
Read references/research-summary.md when the
user asks for research basis, evidence, rationale, literature mapping, or an
instructor-facing explanation of the assessment design choices.
Output Rules
- Default to Markdown unless the user asks for another format.
- Keep the guide practical enough for an instructor to use without extra setup.
- Include concrete
matlab-generate-grader-assessments prompts, not only advice.
- Recommend QTI 3 only when the instructor asks for portability, LMS review,
interchange, standards-based sharing, or instructional-design handoff.
- State that QTI 3 preserves MATLAB Grader artifacts for interchange and does
not make generic QTI runtimes execute MATLAB code.
- Keep policies and institutional workflow language adjustable unless the user
provides local requirements.
- Include a brief research-basis section only when requested or when the guide
is intended for departmental review, pilot approval, or assessment redesign.
1---2name: matlab-plan-grader-adoption3description: Use when an instructor asks for a MATLAB Grader assessment setup guide, adoption guide, pilot plan, course-specific rollout, QTI 3 sharing workflow, or recommended MATLAB Grader assessment-item-generation configuration based on a learning objective, course title, course description, module description, lab description, or assessment goal.4license: MathWorks BSD-3-Clause (see LICENSE)5---6
7# MATLAB Grader Instructor Setup Guide
8
9## Purpose
10
11Generate a short instructor-facing setup guide for adopting the MATLAB Grader
12Assessment Item Generator skill in a course, module, lab, assessment sequence, or
13instructional-design workflow.
14
15Treat the user's provided objective, course description, assessment goal, or
16pilot request as the guide input. If the input is missing, ask for one sentence
17describing the course, module, learning objective, or assessment context before
18generating the guide.
19
20## Input Handling
21
22Use the input to infer the best-fit setup context:
23
24- introductory MATLAB programming;
25- engineering computation or modeling;
26- data analysis or visualization lab;
27- object-oriented programming with MATLAB classes;
28- graded homework, quiz, lab, project, or exam preparation;
29- QTI 3 interchange, LMS review, or instructional-design sharing;
30- mixed or uncertain context.
31
32If multiple contexts fit, choose the primary context and add a short note about
33secondary considerations. Do not ask follow-up questions unless the input is too
34vague to identify an assessment goal.
35
36## Guide Workflow
37
381. Restate the inferred learning objective or assessment goal.
392. Identify the best-fit assessment context and why it fits.
403. Recommend an assessment item type: Script, Function, Class, or Object usage.
414. Recommend assessment purpose: formative, summative, or both.
42 When the context mapping has a purpose emphasis, use it.
43 Otherwise default to summative for graded or unspecified use, and both when
44 the module serves practice first with grading reuse later.
455. Provide an instructor-ready generation prompt for the `matlab-generate-grader-assessments` skill.
466. Define review gates for `description.txt`, `solution.m`, `template.m`,
47 `function_call.m` when the recommended type is Function, and `tests.m`.
487. Define QTI 3 export and sharing guidance when portability is requested.
498. Propose a first pilot with one generated item, one review pass, and one
50 revision loop.
519. Include a concise instructor checklist.
52
53Read [references/setup-guide-template.md](references/setup-guide-template.md)
54for context mapping, output format, prompt patterns, and adaptation rules.
55
56Read [references/research-summary.md](references/research-summary.md) when the
57user asks for research basis, evidence, rationale, literature mapping, or an
58instructor-facing explanation of the assessment design choices.
59
60## Output Rules
61
62- Default to Markdown unless the user asks for another format.
63- Keep the guide practical enough for an instructor to use without extra setup.
64- Include concrete `matlab-generate-grader-assessments` prompts, not only advice.
65- Recommend QTI 3 only when the instructor asks for portability, LMS review,
66 interchange, standards-based sharing, or instructional-design handoff.
67- State that QTI 3 preserves MATLAB Grader artifacts for interchange and does
68 not make generic QTI runtimes execute MATLAB code.
69- Keep policies and institutional workflow language adjustable unless the user
70 provides local requirements.
71- Include a brief research-basis section only when requested or when the guide
72 is intended for departmental review, pilot approval, or assessment redesign.
gabrielmoreira