pslf

Name: pslf
Author: Power-Agent

56stars12forks

How to install pslf?

power-agent/powerskills/pslf

$npx -y skills add Power-Agent/PowerSkills --skill pslf

Installs into the current project.

Summary

Progressive-disclosure workflow for PSLF transmission studies. Use whenever the user wants to open a PSLF case, solve the base power flow, check voltage or overload violations, edit the network (shunts, generators, branches), or run contingency analysis through PowerMCP — even wh

Files · 1

View on GitHub

SKILL.md

1	# PSLF workflow
2
3	Start with the current case and base power flow. Use network edits and contingencies only after the solved case is credible.
4
5	## Default tool ladder
6	1. `open_case(case)`
7	2. `solve_case()`
8	3. `get_voltage(bus)`, `get_voltage_violations(...)`, and `get_overload_violations(...)` to identify the real issue.
9	4. `add_shunt(...)`, `add_generator(...)`, `add_load(...)`, `add_branch(...)`, or `add_bus(...)` for controlled model changes.
10	5. `save_case()` after the edited state is worth keeping.
11	6. `run_contingency_analysis()` only after the base case is solved and monitored.
12
13	## Working rules
14	- Do not run contingencies on an unsolved or obviously bad base case.
15	- Prefer the smallest corrective action that addresses the violation.
16
17	## Escalation triggers
18	Quote the violated bus or branch and its value rather than saying "violations exist".
19
20	\| Observation \| Escalate to \|
21	\|---\|---\|
22	\| `get_voltage_violations` returns low or high buses \| `voltage-violation-mitigation` \|
23	\| `get_overload_violations` returns loaded branches \| `thermal-overload-mitigation` \|
24	\| `run_contingency_analysis` returns binding N-1 cases \| `contingency-mitigation` \|
25	\| `solve_case` fails to converge \| `convergence-failure-mitigation` \|
26
27	## Deliver
28	- The case opened and base-case status.
29	- The key violations found.
30	- The edits applied and whether the contingency study still fails.

People who liked this also viewed

6 picks

Type

pslf

56stars12forks

View on GitHub

How to install pslf?

power-agent/powerskills/pslf

$npx -y skills add Power-Agent/PowerSkills --skill pslf

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PSLF workflow
2
3	Start with the current case and base power flow. Use network edits and contingencies only after the solved case is credible.
4
5	## Default tool ladder
6	1. `open_case(case)`
7	2. `solve_case()`
8	3. `get_voltage(bus)`, `get_voltage_violations(...)`, and `get_overload_violations(...)` to identify the real issue.
9	4. `add_shunt(...)`, `add_generator(...)`, `add_load(...)`, `add_branch(...)`, or `add_bus(...)` for controlled model changes.
10	5. `save_case()` after the edited state is worth keeping.
11	6. `run_contingency_analysis()` only after the base case is solved and monitored.
12
13	## Working rules
14	- Do not run contingencies on an unsolved or obviously bad base case.
15	- Prefer the smallest corrective action that addresses the violation.
16
17	## Escalation triggers
18	Quote the violated bus or branch and its value rather than saying "violations exist".
19
20	\| Observation \| Escalate to \|
21	\|---\|---\|
22	\| `get_voltage_violations` returns low or high buses \| `voltage-violation-mitigation` \|
23	\| `get_overload_violations` returns loaded branches \| `thermal-overload-mitigation` \|
24	\| `run_contingency_analysis` returns binding N-1 cases \| `contingency-mitigation` \|
25	\| `solve_case` fails to converge \| `convergence-failure-mitigation` \|
26
27	## Deliver
28	- The case opened and base-case status.
29	- The key violations found.
30	- The edits applied and whether the contingency study still fails.

People who liked this also viewed

6 picks

Type