matlab/agent-skills-playground / demos/course-generation/skills/matlab-create-course-activity
matlab-create-course-activity
VerifiedCreate MATLAB Course Designer MATLAB Exercise learning activities by wrapping the existing matlab-generate-grader-assessments skill, then validating generated solution.m, template.m, and tests.m files with MATLAB MCP Server tool calls. Use when the user asks to create a MATLAB Exercise, MATLAB course activity, Course Designer MATLAB activity, validated MATLAB solution file, or MATLAB Exercise component folder.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.9 KB |
| references/course-designer-artifacts.md | markdown | 4.5 KB |
| references/grader-wrapper-workflow.md | markdown | 1.7 KB |
| references/matlab-validation-rules.md | markdown | 2.7 KB |
references/matlab-validation-rules.md
View on GitHub# MATLAB Validation Rules
Use MATLAB MCP Server tool calls to validate generated MATLAB Exercise files.
## Required Checks
- Product check: MATLAB and required toolboxes are available or missing products
are reported.
- File check: `description.txt`, `template.m`, `solution.m`, and `tests.m`
exist, plus `function_call.m` for Function assessment items.
- Static analysis: run `check_matlab_code` on `solution.m`, `template.m`, and
`tests.m`.
- Solution check: run or call `solution.m` when the generated artifact is
executable in MATLAB.
- Template check: confirm `template.m` preserves required function names, class
names, variable names, or scaffold comments.
- Tests check: confirm `tests.m` parses and contains the expected MATLAB
Exercise checks.
- Discrimination check (summative items): run at least two plausible wrong
implementations (for example a hardcoded result and an off-by-one variant)
against `tests.m`; every wrong implementation must fail at least one test.
A test suite that only passes the reference solution is not validated.
Record any test rewritten because of this check.
## Execution Guidance
Use the least invasive MCP call that gives useful evidence:
- `check_matlab_code` for `solution.m`, `template.m`, and `tests.m`
(never `background.m` or `task.m`, which are plain-text fields).
- `evaluate_matlab_code` to add the activity folder to the path, call generated
functions, instantiate generated classes, or parse files.
- `run_matlab_file` for script-style solution smoke tests and validation
drivers.
Some `tests.m` files depend on MATLAB assessment functions such as
`assessVariableEqual`. If those functions are unavailable in the current MATLAB
environment, record static validation and mark runtime test execution as
partial instead of pretending the tests passed.
## Validation Report
`validation-report.md` must include:
- Date generated
- MATLAB release/toolbox check status when available
- Files checked
- Static analysis results
- Execution checks attempted
- Test checks attempted
- Deferred checks
- Final status: passed, partial, or failed
Never mark validation as passed when file existence, static analysis, or
required dependency checks failed.
Treat Code Analyzer errors as failures.
Expected warnings are reportable, not blocking: the Grader file-naming warning
on `solution.m` and `template.m`, unset outputs and unused inputs in
`template.m` (they are the blank), and unused-variable warnings on variables
that `assessVariableEqual` consumes by name inside a character vector.
Keep validation scaffolding (drivers, stand-ins, wrong implementations) outside
the activity and grader-source folders; it is working material, not a
deliverable.
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | 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 |