andes

Name: andes
Author: Power-Agent

56stars12forks

How to install andes?

power-agent/powerskills/andes

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

Installs into the current project.

Summary

Progressive-disclosure workflow for ANDES dynamic studies. Use whenever the user wants to run ANDES through PowerMCP for power flow, small-signal / eigenvalue analysis, or time-domain simulation — even when they just say "check the damping", "is this stable", "run a fault", or "l

Files · 1

View on GitHub

SKILL.md

1	# ANDES workflow
2
3	Expose ANDES tools in stages. Do not jump into dynamics until the base case is loaded, solved, and understood.
4
5	## Default tool ladder
6	1. `run_power_flow(file_path)` to load the case and solve the steady-state point.
7	2. `get_system_info()` to summarize buses, generators, dynamic states, and controls.
8	3. `run_eigenvalue_analysis(file_path)` to screen oscillatory modes and poor damping.
9	4. `run_time_domain_simulation(step_size, t_end)` only after the disturbance and success criteria are explicit.
10
11	## Working rules
12	- Re-run the base power flow after any model or dispatch change before dynamic work.
13	- State the disturbance, clearing time, monitored channels, and pass or fail criteria before time-domain runs.
14	- Treat eigenvalue results as screening. Confirm critical cases in time domain.
15
16	## Escalation triggers
17	Quote the failing metric (mode + damping ratio, channel + recovery time) rather than saying "it is unstable".
18
19	\| Observation \| Escalate to \|
20	\|---\|---\|
21	\| Eigenvalue with damping ratio below ~5% or any right-half-plane mode \| `dynamic-stability-mitigation` \|
22	\| Time-domain run shows growing angles, sustained oscillations, or failed voltage recovery \| `dynamic-stability-mitigation` \|
23	\| Base power-flow voltages outside [0.95, 1.05] pu \| `voltage-violation-mitigation` \|
24	\| Frequency nadir, RoCoF, or settling frequency violates its limit after a generation-loss event \| `frequency-response-mitigation` \|
25
26	## Deliver
27	- The case used and whether the base case solved.
28	- The dynamic issue being checked.
29	- The main result and whether mitigation is now required.

People who liked this also viewed

6 picks

Type

andes

56stars12forks

View on GitHub

How to install andes?

power-agent/powerskills/andes

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# ANDES workflow
2
3	Expose ANDES tools in stages. Do not jump into dynamics until the base case is loaded, solved, and understood.
4
5	## Default tool ladder
6	1. `run_power_flow(file_path)` to load the case and solve the steady-state point.
7	2. `get_system_info()` to summarize buses, generators, dynamic states, and controls.
8	3. `run_eigenvalue_analysis(file_path)` to screen oscillatory modes and poor damping.
9	4. `run_time_domain_simulation(step_size, t_end)` only after the disturbance and success criteria are explicit.
10
11	## Working rules
12	- Re-run the base power flow after any model or dispatch change before dynamic work.
13	- State the disturbance, clearing time, monitored channels, and pass or fail criteria before time-domain runs.
14	- Treat eigenvalue results as screening. Confirm critical cases in time domain.
15
16	## Escalation triggers
17	Quote the failing metric (mode + damping ratio, channel + recovery time) rather than saying "it is unstable".
18
19	\| Observation \| Escalate to \|
20	\|---\|---\|
21	\| Eigenvalue with damping ratio below ~5% or any right-half-plane mode \| `dynamic-stability-mitigation` \|
22	\| Time-domain run shows growing angles, sustained oscillations, or failed voltage recovery \| `dynamic-stability-mitigation` \|
23	\| Base power-flow voltages outside [0.95, 1.05] pu \| `voltage-violation-mitigation` \|
24	\| Frequency nadir, RoCoF, or settling frequency violates its limit after a generation-loss event \| `frequency-response-mitigation` \|
25
26	## Deliver
27	- The case used and whether the base case solved.
28	- The dynamic issue being checked.
29	- The main result and whether mitigation is now required.

People who liked this also viewed

6 picks

Type