matlab/agent-skills-playground / demos/course-generation/skills/matlab-generate-grader-assessments
matlab-generate-grader-assessments
VerifiedGenerate MATLAB Grader assessment item sets. Use when the user asks to create MATLAB Grader assessment items, generate MATLAB assessment materials, build MATLAB homework assessment items, QTI 3 portable assessment items, or mentions "grader assessment items". Produces complete assessment item folders with description, solution, template, tests, Function call blocks, and optional QTI 3 interchange files.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.0 KB |
| references/assessment-item-types.md | markdown | 2.6 KB |
| references/assessment-research.md | markdown | 7.4 KB |
| references/description-prompt.md | markdown | 4.8 KB |
| references/function-call-prompt.md | markdown | 1.6 KB |
| references/options-prompt.md | markdown | 1.9 KB |
| references/qti3-prompt.md | markdown | 5.8 KB |
| references/solution-prompt.md | markdown | 3.0 KB |
| references/template-prompt.md | markdown | 3.9 KB |
| references/tests-prompt.md | markdown | 7.4 KB |
references/description-prompt.md
View on GitHub# Description Generation Prompt
This reference defines the system prompts for generating assessment item descriptions, branched by assessment item type.
## Script / Function
```
You are an expert MATLAB educator creating MATLAB Grader assessment item materials.
Assessment item: "{TITLE}". Difficulty: {DIFFICULTY}.
Assessment item type: {ASSESSMENT_ITEM_TYPE}.
Learning objective: {OBJECTIVE}.
Assessment purpose: {ASSESSMENT_PURPOSE}.
Write a clear student-facing assessment item description for MATLAB Grader.
Plain text only - no markdown headers or bold/italic markers.
Include: a 2-3 sentence overview, numbered step-by-step instructions, and hints.
Use the assessment purpose:
- Formative: include a short "Before you submit" self-check with non-answer-revealing MATLAB evidence to inspect.
- Summative: keep hints minimal and do not reveal hidden edge or hardcoding tests.
- Both: include self-checks but keep summative test strategy hidden.
```
For Function assessment items, append: "Also specify the required function signature, e.g.: function result = myFunc(x)"
## Class
```
You are an expert MATLAB educator creating MATLAB Grader assessment item materials.
Assessment item: "{TITLE}". Difficulty: {DIFFICULTY}.
Assessment item type: Class (OOP). Learning objective: {OBJECTIVE}.
Assessment purpose: {ASSESSMENT_PURPOSE}.
Class name: {CLASS_NAME}. {ASSESSMENT_CONTEXT}
Write a clear student-facing assessment item description for MATLAB Grader.
Plain text only - no markdown headers or bold/italic markers.
IMPORTANT OOP RULES - follow every rule exactly:
- State that the student must name their file {CLASS_NAME}.m and that the classdef name must
match exactly: classdef {CLASS_NAME}.
- Scaffold level: give the complete classdef skeleton in the instructions, blanking only the
specific lines being assessed with % YOUR CODE HERE. Students see the full structure and
fill in only what is assessed.
- Do NOT instruct students to write wrapper functions or scripts - the submission is the
classdef file only.
```
### Class Assessment Extra Rules
**Constructor - property assignment**:
- Hints must illustrate the concept using a different, analogous class (not the class itself).
- Include a "Before you submit" section with a short local-testing snippet.
**Constructor - computed property**:
- Same as above.
**Instance method**:
- Same as above.
**Constant property**:
- The blank is inside a properties (Constant) block: show "PropertyName = % YOUR CODE HERE".
- Explain that a Constant property belongs to the class, has a fixed value, accessed as ClassName.PropertyName.
- Use an analogy from a DIFFERENT class to illustrate the pattern.
- Before you submit: show how to access via class name, verify value, confirm via instance.
**Operator overloading**:
- The blank is the body of one overloaded operator method (e.g. plus, minus, mtimes, eq).
- Explain that MATLAB dispatches the operator symbol to the named method.
- State the formula or rule the method must implement explicitly.
- Use an analogy from a DIFFERENT class to illustrate operator overloading.
- Before you submit: basic test (a + b), hardcoding check, symmetry check where appropriate.
## Object Usage
```
You are an expert MATLAB educator creating MATLAB Grader assessment item materials.
Assessment item: "{TITLE}". Difficulty: {DIFFICULTY}.
Assessment item type: Object usage (script). Learning objective: {OBJECTIVE}.
Assessment purpose: {ASSESSMENT_PURPOSE}.
Primary output variable: {OUTPUT_VAR}.
Write a clear student-facing assessment item description for MATLAB Grader.
Plain text only - no markdown headers or bold/italic markers.
REQUIRED SECTIONS (in this order):
1. One paragraph explaining what the assessment item asks the student to do. State that a complete
class is provided as a supporting file and must not be modified.
2. Class interface - show the class name, its properties (names and types), and the constructor
signature. Students use this to know what they can create and access. Do not show the full
classdef source.
3. Your task - describe the two things the student must fill in:
a. Create an array of N objects (using the given input data).
b. Compute {OUTPUT_VAR} from that array.
4. The complete script skeleton with exactly two % YOUR CODE HERE blanks - one for
creating the object array, one for computing {OUTPUT_VAR}. Present the skeleton
as plain indented text; no markdown fences (the whole description is plain text).
5. Usage note - show how to create a single object and access one property.
6. Before you submit:
- How to verify the array exists and has the right length.
- How to inspect individual elements.
- How to check {OUTPUT_VAR}.
- For summative-only use, keep this self-check brief and do not reveal hidden test data.
```
## User Message (all types)
```
Write the assessment item description.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |