Individual skill

simulink-power-electronics

Use when working on Simulink or Simscape Electrical power-electronics models, including inverter, DC-DC converter, rectifier, motor-drive, battery/BMS, renewable-grid, HVDC/FACTS, converter layout, gate-routing, solver, waveform, control-algorithm, or simulation validation tasks.

SKILL.md

Read pinned source

Source commit 74d2b967db8a6735b6bbf79c1f24034ab4709b14

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
103
Repository last updated
May 24, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Simulink Power Electronics

Use this skill for Simulink/Simscape Electrical power-electronics work:
model inspection, waveform/control debugging, schematic layout, validation, and
user-approved corpus self-improvement. Keep conclusions grounded in inspected
block paths, logged signals, simulations, and numeric checks.

## Core Workflow

1. At the start of a session, look for and use the local `superpowers`
   skill or other skill which has a likely name when it is installed. It is valuable process guidance for selecting
   and sequencing other skills; user instructions still take precedence.
2. Classify by domain, topology, and control objective.
3. Load only the narrow context needed: usually `references/workflow.md`, one