psse

Name: psse
Author: Power-Agent

56stars12forks

How to install psse?

power-agent/powerskills/psse

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

Installs into the current project.

Summary

Progressive-disclosure workflow for PSS/E studies through PowerMCP. Use whenever the user wants to open a PSS/E case, solve the base case, discover the right PSSPY command, or run targeted PSS/E automation — even when they just say "open this sav", "solve it", or "how do I change

Files · 1

View on GitHub

SKILL.md

1	# PSSE workflow
2
3	Treat PSSE as a layered interface. Start with the built-in base-case tools. Use generic `psspy` execution only after the correct command and argument shape are known.
4
5	## Default tool ladder
6	1. `open_case(case)`
7	2. `solve_case()`
8	3. `search_psspy_commands(query, category)` or `lookup_psspy_command(function_name)` to discover the right API entry point.
9	4. `run_psspy_command(function_name, arguments)` only after the command contract is explicit.
10
11	## Working rules
12	- Do not use `run_psspy_command` as a search tool. Search or look up first.
13	- Keep every executed command tied to a study objective, not just API curiosity.
14	- Re-solve or re-check the case after commands that alter topology, controls, or dispatch.
15
16	## Escalation triggers
17	Quote the bus or branch and its value rather than saying "violations exist". Use `dynamic-stability-mitigation` for dynamic-performance issues.
18
19	\| Observation \| Escalate to \|
20	\|---\|---\|
21	\| Bus voltage < 0.95 or > 1.05 pu after `solve_case` \| `voltage-violation-mitigation` \|
22	\| Branch loading above its MVA rating \| `thermal-overload-mitigation` \|
23	\| Contingency run returns binding N-1 cases \| `contingency-mitigation` \|
24	\| `solve_case` fails to converge \| `convergence-failure-mitigation` \|
25	\| Fault duty near or above breaker interrupting ratings \| `short-circuit-mitigation` \|
26
27	## Deliver
28	- The case, the command path chosen, and why it was needed.
29	- The arguments passed to the command.
30	- The study outcome and any required mitigation.

People who liked this also viewed

6 picks

Type

psse

56stars12forks

View on GitHub

How to install psse?

power-agent/powerskills/psse

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PSSE workflow
2
3	Treat PSSE as a layered interface. Start with the built-in base-case tools. Use generic `psspy` execution only after the correct command and argument shape are known.
4
5	## Default tool ladder
6	1. `open_case(case)`
7	2. `solve_case()`
8	3. `search_psspy_commands(query, category)` or `lookup_psspy_command(function_name)` to discover the right API entry point.
9	4. `run_psspy_command(function_name, arguments)` only after the command contract is explicit.
10
11	## Working rules
12	- Do not use `run_psspy_command` as a search tool. Search or look up first.
13	- Keep every executed command tied to a study objective, not just API curiosity.
14	- Re-solve or re-check the case after commands that alter topology, controls, or dispatch.
15
16	## Escalation triggers
17	Quote the bus or branch and its value rather than saying "violations exist". Use `dynamic-stability-mitigation` for dynamic-performance issues.
18
19	\| Observation \| Escalate to \|
20	\|---\|---\|
21	\| Bus voltage < 0.95 or > 1.05 pu after `solve_case` \| `voltage-violation-mitigation` \|
22	\| Branch loading above its MVA rating \| `thermal-overload-mitigation` \|
23	\| Contingency run returns binding N-1 cases \| `contingency-mitigation` \|
24	\| `solve_case` fails to converge \| `convergence-failure-mitigation` \|
25	\| Fault duty near or above breaker interrupting ratings \| `short-circuit-mitigation` \|
26
27	## Deliver
28	- The case, the command path chosen, and why it was needed.
29	- The arguments passed to the command.
30	- The study outcome and any required mitigation.

People who liked this also viewed

6 picks

Type