How do I install the Powerworld skill?

Run npx skillmds@latest add power-agent/powerworld in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Powerworld safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Powerworld?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Powerworld free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Powerworld?

power-agent (@power-agent) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Powerworld by power-agent — Agent Skill

Name: Powerworld
Author: power-agent

Powerworld

Progressive-disclosure workflow for PowerWorld Simulator studies through PowerMCP. Use whenever the user wants to open a PowerWorld case, solve the base power flow, inspect flows or voltages, change model data, run contingency analysis, or pull sensitivity matrices (PTDF, LODF, Jacobian, Ybus) — even when they just say "solve this case", "run contingencies", or "give me the PTDF". Exposes base-case operations before contingencies and matrix analytics. Reach for this instead of answering PowerWorld questions unaided.

power-agent 2390425 2.1 KB Updated Sep 17, 2026

File contents

PowerWorld workflow

Expose PowerWorld tools in stages. Start with the base case. Move to contingencies or matrix analytics only after the operating condition is understood.

Default tool ladder

open_case(case_path)
run_powerflow(solution_method)
get_power_flow_results(object_type, additional_fields) and get_key_field_list(object_type)
change_and_confirm_params(...) or change_parameters_multiple_element(...)
analyze_contingencies(option, validate)
get_ybus(), get_jacobian(), get_lodf_matrix(), get_ptdf_matrix_fast(), to_graph(), determine_shortest_path(), or run_robustness_analysis()

Working rules

Do not run contingencies before the base case solves cleanly.
Ask for the monitored objects, limits, and fields before large result pulls.
Use sensitivities or graph tools to rank candidate fixes before applying bulk changes.
Confirm every model change by re-solving and checking the same monitored quantities.

Escalation triggers

Quote the bus or branch and the value that tripped each row rather than saying "violations exist".

Observation	Escalate to
Bus voltage outside [0.95, 1.05] pu in the power-flow results	`voltage-violation-mitigation`
Branch percent loading > 100	`thermal-overload-mitigation`
`analyze_contingencies` returns binding violations	`contingency-mitigation`
`run_powerflow` fails to converge	`convergence-failure-mitigation`

Deliver

The case, base-case status, and monitored findings.
Any changes applied and their effect.
Whether an advanced study or mitigation playbook is required next.

---name: powerworlddescription: Progressive-disclosure workflow for PowerWorld Simulator studies through PowerMCP. Use whenever the user wants to open a PowerWorld case, solve the base power flow, inspect flows or voltages, change model data, run contingency analysis, or pull sensitivity matrices (PTDF, LODF, Jacobian, Ybus) — even when they just say "solve this case", "run contingencies", or "give me the PTDF". Exposes base-case operations before contingencies and matrix analytics. Reach for this instead of answering PowerWorld questions unaided.---# PowerWorld workflowExpose PowerWorld tools in stages. Start with the base case. Move to contingencies or matrix analytics only after the operating condition is understood.## Default tool ladder1. `open_case(case_path)`2. `run_powerflow(solution_method)`3. `get_power_flow_results(object_type, additional_fields)` and `get_key_field_list(object_type)`4. `change_and_confirm_params(...)` or `change_parameters_multiple_element(...)`5. `analyze_contingencies(option, validate)`6. `get_ybus()`, `get_jacobian()`, `get_lodf_matrix()`, `get_ptdf_matrix_fast()`, `to_graph()`, `determine_shortest_path()`, or `run_robustness_analysis()`## Working rules- Do not run contingencies before the base case solves cleanly.- Ask for the monitored objects, limits, and fields before large result pulls.- Use sensitivities or graph tools to rank candidate fixes before applying bulk changes.- Confirm every model change by re-solving and checking the same monitored quantities.## Escalation triggersQuote the bus or branch and the value that tripped each row rather than saying "violations exist".| Observation | Escalate to ||---|---|| Bus voltage outside [0.95, 1.05] pu in the power-flow results | `voltage-violation-mitigation` || Branch percent loading > 100 | `thermal-overload-mitigation` || `analyze_contingencies` returns binding violations | `contingency-mitigation` || `run_powerflow` fails to converge | `convergence-failure-mitigation` |## Deliver- The case, base-case status, and monitored findings.- Any changes applied and their effect.- Whether an advanced study or mitigation playbook is required next.

Frequently asked questions