How do I install the Convergence Failure Mitigation skill?

Run npx skillmds@latest add power-agent/convergence-failure-mitigation 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 Convergence Failure Mitigation 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 Convergence Failure Mitigation?

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 Convergence Failure Mitigation free to use?

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

Who published Convergence Failure Mitigation?

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

Convergence Failure Mitigation by power-agent

Name: Convergence Failure Mitigation
Author: power-agent

Convergence Failure Mitigation

Senior power-engineer playbook for power-flow convergence failures. Use whenever a base case or post-change case diverges, oscillates, or fails to solve in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Triggers on "power flow diverged", "case won't solve", "did not converge", "blown-up voltages", or "max iterations reached". Every tool skill stops on a non-convergent base case — this playbook is what to do next, separating data errors from numerical fragility from genuine physical infeasibility.

power-agent e588fdb 2.4 KB Updated Sep 17, 2026

File contents

Convergence failure mitigation

Start from the failed solve and its mismatch report. The goal is to learn why it failed, not just to force a solution.

Preferred action order

Rule out data problems first: isolated or de-energized buses, zero or absurd branch impedances, missing or misplaced swing bus, transformer tap and phase-angle data, load/generation totals that cannot balance.
Check islanding and slack coverage: every energized island needs a slack with feasible MW. Use the tool's island or topology report before touching solver settings.
Simplify the solve, then restore: try flat start vs warm start, lock taps, switched shunts, and phase shifters, relax generator Q-limits — then re-enable controls stepwise once a solution exists.
Seed from an easier point: a DC solve, a previously solved neighbor case, or a reduced-stress version of the case, then scale load or transfer toward the target in steps.
If failure persists only near the target stress level, treat it as a feasibility boundary, not a numerical bug: reduce transfer or load, add reactive support, and flag possible voltage-collapse proximity.

Working rules

The largest mismatch bus tells you where to look — start there, not with global solver settings.
Change one solver setting at a time and record what finally solved.
A case solved with controls locked or Q-limits relaxed is not finished; restore realism before reporting results from it.
Distinguish "the math failed" from "the operating point does not exist" — the corrective actions are completely different.

Deliver

The failure category: data error, control interaction, numerical fragility, or physical infeasibility.
The specific change that made the case solve.
Any realism caveats that remain (locked controls, relaxed limits) and what to re-check.

---name: convergence-failure-mitigationdescription: Senior power-engineer playbook for power-flow convergence failures. Use whenever a base case or post-change case diverges, oscillates, or fails to solve in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Triggers on "power flow diverged", "case won't solve", "did not converge", "blown-up voltages", or "max iterations reached". Every tool skill stops on a non-convergent base case — this playbook is what to do next, separating data errors from numerical fragility from genuine physical infeasibility.---# Convergence failure mitigationStart from the failed solve and its mismatch report. The goal is to learn *why* it failed, not just to force a solution.## Preferred action order1. Rule out data problems first: isolated or de-energized buses, zero or absurd branch impedances, missing or misplaced swing bus, transformer tap and phase-angle data, load/generation totals that cannot balance.2. Check islanding and slack coverage: every energized island needs a slack with feasible MW. Use the tool's island or topology report before touching solver settings.3. Simplify the solve, then restore: try flat start vs warm start, lock taps, switched shunts, and phase shifters, relax generator Q-limits — then re-enable controls stepwise once a solution exists.4. Seed from an easier point: a DC solve, a previously solved neighbor case, or a reduced-stress version of the case, then scale load or transfer toward the target in steps.5. If failure persists only near the target stress level, treat it as a feasibility boundary, not a numerical bug: reduce transfer or load, add reactive support, and flag possible voltage-collapse proximity.## Working rules- The largest mismatch bus tells you where to look — start there, not with global solver settings.- Change one solver setting at a time and record what finally solved.- A case solved with controls locked or Q-limits relaxed is not finished; restore realism before reporting results from it.- Distinguish "the math failed" from "the operating point does not exist" — the corrective actions are completely different.## Deliver- The failure category: data error, control interaction, numerical fragility, or physical infeasibility.- The specific change that made the case solve.- Any realism caveats that remain (locked controls, relaxed limits) and what to re-check.

Frequently asked questions