Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans.
Install Specifying Plant Models
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-models --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .claude/skills/specifying-plant-models && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .claude/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-modelsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-models --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .agents/skills/specifying-plant-models && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .agents/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-models --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .cursor/skills/specifying-plant-models && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .cursor/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/matlab/simulink-agentic-toolkit.git --path skills-catalog/model-based-design-core/specifying-plant-models--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-models --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .gemini/skills/specifying-plant-models && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .gemini/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-modelsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .github/skills/specifying-plant-models && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .github/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install matlab/simulink-agentic-toolkit specifying-plant-models --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills-catalog/model-based-design-core/specifying-plant-models .opencode/skills/specifying-plant-models && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "specifying-plant-models" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/specifying-plant-models into .opencode/skills/specifying-plant-models/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specifying-plant-models", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
specifying-plant-models- GitHub stars
- 1.2k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 905 words
- Files
- 7 (incl. references, assets)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans.
- Works in 6 steps: Analyze Controller Interface → Assess Validation Evidence → Research the Physics Domain → …
- Reviewing plant model specifications
- SKILL.md covers When to Use, When NOT to Use, Output Conventions and Mode Selection, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Specifying Plant Models is an agent skill from matlab/simulink-agentic-toolkit. Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans. Use when creating, updating, or reviewing plant model specifications, planning plant model architecture, or planning plant model validation.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `assets/architecture-spec-template.md`, `assets/implementation-plan-template.md` and `assets/system-spec-template.md`).
It sits in Agent Workflows, covering Planning. The repository describes itself as: The Simulink Agentic Toolkit gives your AI agent both the tools and the expertise to work effectively with Simulink and Model-Based Design.
When your agent uses it
- Reviewing plant model specifications
- Planning plant model architecture
- Planning plant model validation
Example prompts
- “/specifying-plant-models”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Analyze Controller Interface
- Assess Validation Evidence
- Research the Physics Domain
- Write System Spec
- Write Architecture Spec
- Write Implementation Plan + Test Plan
What it can do on your machine
Read from SKILL.md and the folder at commit c58e6ae. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Specifying Plant Models loads about 2.2k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 905 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 905 words (~2,168 tokens).
“Structured specification of plant models for closed-loop simulation. Adapts the specifying-software templates for the physics-modeling domain.”
- name
- specifying-plant-models
- license
- https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md
- metadata.author
- MathWorks
- metadata.version
- 1.1
Files
SKILL.md and 6 other files (references, assets) in skills-catalog/model-based-design-core/specifying-plant-models of matlab/simulink-agentic-toolkit.
- SKILL.md
- assets/architecture-spec-template.md
- assets/implementation-plan-template.md
- assets/system-spec-template.md
- assets/test-plan-template.md
- manifest.yaml
- references/plant-model-guidance.md
Open the folder on GitHubat commit c58e6ae
Compare with similar skills
Specifying Plant Models next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Specifying Plant Models this skillmatlab/simulink-agentic-toolkit | 1.2k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Improvefossasia/eventyay-interpretation | 1.6k | 10 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Workflow Orchestrationvxcozy/workflow-orchestration | 116 | — | ~1k | Automated safety check: Pass | MIT | |
| Deep Planpiercelamb/deep-plan | 101 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Plan Py4vaspvasp-dev/py4vasp | 100 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Execute PhasealchemiststudiosDOTai/harness-engineering | 105 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Workflow Orchestration
vxcozy/workflow-orchestration
Disciplined task execution with planning, verification, and self-improvement loops.
Deep Plan
piercelamb/deep-plan
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review.
Plan Py4vasp
vasp-dev/py4vasp
Plan a py4vasp change as an ordered list of test-first chunks — that chunk list is the plan.
Execute Phase
alchemiststudiosDOTai/harness-engineering
Execute implementation plans from .artifacts/plan/. An agent skill from alchemiststudiosDOTai/harness-engineering.
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
More from matlab/simulink-agentic-toolkit
All 43 skills in this repoResolve Design Errors
matlab/simulink-agentic-toolkit
A skill your agent uses when asked to run Design Error Detection (quick defect scan), find design errors in a Simulink model, perform root cause analysis on DED findings, fix division-by-zero…
Simscape Write Ssc
matlab/simulink-agentic-toolkit
A skill your agent uses when writing or editing Simscape Language (.ssc) source files — components, domains, or functions.
Simulink Optimizing Embedded Code
matlab/simulink-agentic-toolkit
Optimizes Simulink models for Embedded Coder generated code.
Checking Model Compliance
matlab/simulink-agentic-toolkit
A skill your agent uses when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO, DO, IEC, EN, CERT C/CWE, AUTOSAR, Simulink Code Inspector (SLCI)), wants to…
Fix Sldv Incompatibility
matlab/simulink-agentic-toolkit
A skill your agent uses when a Simulink model is incompatible with Simulink Design Verifier (sldvcompat returns false, or an SLDV analysis errors out on an unsupported construct) and needs to be…
Simulink Collect Metrics
matlab/simulink-agentic-toolkit
Collect and assess quality metrics for Simulink models using the metric.Engine API.
Related
Categories
Questions about Specifying Plant Models
What does Specifying Plant Models do?
Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans. Specifying Plant Models is an agent skill from matlab/simulink-agentic-toolkit. Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans.
When should I use Specifying Plant Models?
Specifying Plant Models fits situations like: reviewing plant model specifications; planning plant model architecture; planning plant model validation.
How do I install Specifying Plant Models in Claude Code?
Run `npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a claude-code`. Or copy the skill folder (skills-catalog/model-based-design-core/specifying-plant-models in matlab/simulink-agentic-toolkit) into .claude/skills/specifying-plant-models in your project. Claude Code loads it when a task matches its description.
How do I install Specifying Plant Models in Codex?
Run `npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a codex`. Or copy the skill folder (skills-catalog/model-based-design-core/specifying-plant-models in matlab/simulink-agentic-toolkit) into .agents/skills/specifying-plant-models in your project. Codex loads it when a task matches its description.
Can I use Specifying Plant Models in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add matlab/simulink-agentic-toolkit --skill specifying-plant-models -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specifying-plant-models, .gemini/skills/specifying-plant-models, .github/skills/specifying-plant-models and .opencode/skills/specifying-plant-models in your project.
What does Specifying Plant Models need to run?
SKILL.md names no scripts, command-line tools or credentials: Specifying Plant Models is instructions for the agent only.
Does Specifying Plant Models access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Specifying Plant Models safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Specifying Plant Models use?
Specifying Plant Models has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Specifying Plant Models use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 626 tokens, read only when the agent opens those files.
What are the alternatives to Specifying Plant Models?
Skills that share tags, products or a category with Specifying Plant Models: Improve (fossasia/eventyay-interpretation, 1.6k stars), Workflow Orchestration (vxcozy/workflow-orchestration, 116 stars), Deep Plan (piercelamb/deep-plan, 101 stars) and Plan Py4vasp (vasp-dev/py4vasp, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specifying Plant Models?
matlab (a GitHub organization) maintains it in matlab/simulink-agentic-toolkit, which has 1,199 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.
Source: matlab/simulink-agentic-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.