matlab-plan-course-adoption
Use when an instructor asks for a setup guide, adoption guide, planning guide, implementation checklist, prerequisite check, MATLAB Course Designer course structure plan, Common Cartridge workflow, Simulink starter and solution model planning, LMS import plan, or starter prompt for creating a MATLAB and Simulink enabled course with the matlab-generate-course skill.
git clone --depth 1 https://github.com/matlab/agent-skills-playground /tmp/matlab-plan-course-adoption && cp -r /tmp/matlab-plan-course-adoption/demos/course-generation/skills/matlab-plan-course-adoption ~/.claude/skills/matlab-plan-course-adoptionSKILL.md
# MATLAB Course Instructor Setup Guide Generate a short instructor-facing setup guide for adopting the MATLAB Course Designer Generator skill package. The guide prepares an instructor to run `matlab-generate-course`, review MATLAB and Simulink activities, use the `matlab-create-course-activity` skill to wrap `matlab-generate-grader-assessments` and validate MATLAB Exercise `.m` files, use `simulink-create-course-activity` for Simulink Exercise starter and solution model files, and review the final Common Cartridge package as the persisted course representation. The guide must frame generated content around the MATLAB Course Designer organization model: a course contains ordered modules, and modules contain ordered learning activities. Common Cartridge is the persistence format used outside the web application until future API work creates course instances directly. ## Input Handling Treat the user's course title, syllabus idea, module description, audience, lab sequence, existing course, or rollout goal as the guide input. If the input is missing, ask for one sentence describing the course or rollout context. Infer: - Course context and learner level - MATLAB and Simulink scope - Likely assessment approach - Common Cartridge persistence target and any downstream LMS import target - Course Designer module and learning activity structure - Prerequisite skill/toolkit readiness - Whether MATLAB Exercises are likely needed and should be generated through `matlab-create-course-activity` - Whether Simulink Exercises need starter and solution `.slx` files generated by `simulink-create-course-activity` Do not ask follow-up questions unless the input is too vague to identify a course goal. ## Guide Workflow 1. Restate the inferred course goal. 2. Identify the best-fit course generation context. 3. List prerequisite skill packages and MathWorks access assumptions, always including IDStack, the MATLAB MCP Server, and the activity skills by name. 4. Recommend a `matlab-generate-course` starter prompt. 5. Recommend when and how to use `matlab-create-course-activity` for MATLAB Exercise component generation, MATLAB MCP validation, and Course Designer-only fields. 6. Recommend when and how to use `simulink-create-course-activity` for Simulink Exercise model artifacts. 7. Define Course Designer module and learning activity review gates. 8. Define Common Cartridge export and persisted course review checks. 9. Propose a first pilot with one module or one short course shell. 10. Include a concise instructor checklist. Read [references/setup-guide-template.md](references/setup-guide-template.md) for output format, context mapping, prompt patterns, and checklist content. ## Output Rules - Default to Markdown unless the user asks for another format. - Keep the guide practical enough for an instructor to act on immediately. - Include a concrete `matlab-generate-course` starter prompt. - Include concrete `matlab-create-course-activity` prompts when MATLAB Exercises are likely. - State that Common Cartridge persists the course shell and instructions outside MATLAB Course Designer; MATLAB and Simulink execution happens in the appropriate MathWorks environment. - Keep institutional policy language adjustable unless the user provides local requirements.
>
Use this skill when the user wants to author, design, scope, or refine an Agent Skill (a SKILL.md file). Trigger phrases include "build a new skill", "design an agent skill", "scope a SKILL.md", "how should I structure this skill", "write a skill for X", "my skill isn't working well", or any request to improve an existing SKILL.md. Walks the user through an empirical, test-first process — probe the agent for real failures, design only for genuine knowledge gaps, iterate against runnable examples, and verify across models.
Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.
Use this skill for the architecture phases of an MBSE workflow in MATLAB, when writing idempotent buildXxx.m scripts that produce a three-layer RFLPV architecture (Functional, Logical, Physical) with interface dictionaries, stereotype profiles, allocation sets, and requirements Implement links. Trigger for defining stereotype properties, functional-to-logical / logical-to-physical allocation, mapping requirements to components via slreq Implement links, or running quantitative roll-up analysis on the architecture. Do NOT trigger for ad-hoc structural edits to an already-built System Composer model (adding one component, rewiring a port) — use `building-simulink-models` with `model_edit` for that. Works alongside the `system-composer` skill for detailed SC API patterns.
Use this skill for guided MBSE work in MATLAB — starting a new project, resuming work mid-workflow on an existing project, or answering orientation questions about how the MBSE skills fit together. Trigger when the user says they want to create, start, or set up a new MBSE project; work on a model-based systems engineering / RFLPV project; or asks which skill covers which phase. Walks through phases one at a time — propose → approve → generate → run → confirm. Use proactively whenever someone mentions starting or continuing an MBSE project.
Use this skill for all requirements-related work in a MATLAB MBSE project using the Requirements Toolbox (slreq). Covers creating and populating requirement sets, derivation links, test case requirements, verification coverage, reading and tracing links across requirement sets and models, checking link health, allocating requirements to components (Implement links), and building traceability reports. Trigger when the user asks about slreq API, slreqx files, slmx link files, outLinks/inLinks, traceability matrices, coverage analysis, broken links, or mapping requirements to architecture components. Use proactively for any requirements or traceability task.
Use this skill when authoring reusable, idempotent MATLAB scripts that build System Composer architecture models via the architecture-modeling API — `systemcomposer.createModel`, `addComponent`, `addPort`, `setInterface`, `connect(srcPort, dstPort)`, interface dictionaries (.sldd) with `addInterface`/`addElement`, profiles/stereotypes with `Profile.createProfile` and `addStereotype`, or `systemcomposer.allocation.createAllocationSet`. Also trigger when debugging these APIs (connections that don't appear, interfaces that don't resolve, profile save errors, `createAllocationSet` signature-mismatch errors). Do NOT trigger for ad-hoc structural edits to an already-built model (adding one SubSystem, rewiring a port) — use `building-simulink-models` with `model_edit` for that.
Optimize MATLAB code for better performance through vectorization, memory management, and profiling. Use when user requests optimization, mentions slow code, performance issues, speed improvements, or asks to make code faster or more efficient.