contingency-mitigation

Name: contingency-mitigation
Author: Power-Agent

56stars12forks

How to install contingency-mitigation?

power-agent/powerskills/contingency-mitigation

$npx -y skills add Power-Agent/PowerSkills --skill contingency-mitigation

Installs into the current project.

Summary

Senior power-engineer playbook for contingency violations. Use whenever N-1 or N-2 studies reveal voltage or thermal problems, binding contingencies, or post-outage islanding — including escalations from a tool skill's contingency run. Triggers on "N-1 violation", "worst continge

Files · 1

View on GitHub

SKILL.md

1	# Contingency mitigation
2
3	Start with a solved base case and a ranked list of critical contingencies.
4
5	## Preferred action order
6	1. Verify the contingency definitions, monitored elements, and limits.
7	2. Group critical contingencies by common corridor, interface, or weak area.
8	3. Apply preventive actions first: redispatch, shunts, tap changes, or topology changes that help multiple contingencies.
9	4. Evaluate corrective actions next: post-contingency switching, redispatch, or RAS schemes with explicit triggers.
10	5. Use load shedding only as a last-resort action and state that clearly.
11	6. For recurring problems, recommend reinforcement or a revised operating guide.
12
13	## Working rules
14	- Do not trust contingency results from a bad base case.
15	- Prefer actions that improve a family of contingencies rather than a single outage.
16	- Re-run the full monitored set after any candidate fix.
17
18	## Deliver
19	- The critical contingencies and the shared weak pattern.
20	- The best preventive action.
21	- Any corrective action that is still required after prevention.

People who liked this also viewed

6 picks

Type

contingency-mitigation

56stars12forks

View on GitHub

How to install contingency-mitigation?

power-agent/powerskills/contingency-mitigation

$npx -y skills add Power-Agent/PowerSkills --skill contingency-mitigation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Contingency mitigation
2
3	Start with a solved base case and a ranked list of critical contingencies.
4
5	## Preferred action order
6	1. Verify the contingency definitions, monitored elements, and limits.
7	2. Group critical contingencies by common corridor, interface, or weak area.
8	3. Apply preventive actions first: redispatch, shunts, tap changes, or topology changes that help multiple contingencies.
9	4. Evaluate corrective actions next: post-contingency switching, redispatch, or RAS schemes with explicit triggers.
10	5. Use load shedding only as a last-resort action and state that clearly.
11	6. For recurring problems, recommend reinforcement or a revised operating guide.
12
13	## Working rules
14	- Do not trust contingency results from a bad base case.
15	- Prefer actions that improve a family of contingencies rather than a single outage.
16	- Re-run the full monitored set after any candidate fix.
17
18	## Deliver
19	- The critical contingencies and the shared weak pattern.
20	- The best preventive action.
21	- Any corrective action that is still required after prevention.

People who liked this also viewed

6 picks

Type