How do I install the Andes skill?

Run npx skillmds@latest add power-agent/andes 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 Andes 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 Andes?

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 Andes free to use?

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

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

Andes by power-agent — Agent Skill

Name: Andes
Author: power-agent

Andes

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 "look at the oscillation modes". Exposes a solved base case before eigenvalue screening and time-domain runs. Reach for this instead of answering ANDES dynamics questions unaided.

power-agent 94b1616 2.6 KB Updated Sep 17, 2026

File contents

ANDES workflow

Expose ANDES tools in stages. Do not jump into dynamics until the base case is loaded, solved, and understood.

Default tool ladder

run_power_flow(file_path) to load the case and solve the steady-state point.
get_system_info() to summarize buses, generators, dynamic states, and controls.
run_eigenvalue_analysis(file_path) to screen oscillatory modes and poor damping.
run_time_domain_simulation(step_size, t_end) only after the disturbance and success criteria are explicit.

Example sequence

Illustrative run on an ANDES-bundled case:

run_power_flow("ieee14.xlsx")           -> base case solved, 14 buses, 5 generators
get_system_info()                       -> dynamic models, governor and exciter types
run_eigenvalue_analysis("ieee14.xlsx")  -> dominant mode 0.42 Hz, damping 3.1%
run_time_domain_simulation(0.01, 10.0)  -> generator trip at t=1s, monitor rotor angles

The 3.1% damping is below the ~5% screening threshold, so this case escalates to dynamic-stability-mitigation rather than stopping at "the modes look weak".

Working rules

Re-run the base power flow after any model or dispatch change before dynamic work.
State the disturbance, clearing time, monitored channels, and pass or fail criteria before time-domain runs.
Treat eigenvalue results as screening. Confirm critical cases in time domain.

Escalation triggers

Quote the failing metric (mode + damping ratio, channel + recovery time) rather than saying "it is unstable".

Observation	Escalate to
Eigenvalue with damping ratio below ~5% or any right-half-plane mode	`dynamic-stability-mitigation`
Time-domain run shows growing angles, sustained oscillations, or failed voltage recovery	`dynamic-stability-mitigation`
Base power-flow voltages outside [0.95, 1.05] pu	`voltage-violation-mitigation`
Frequency nadir, RoCoF, or settling frequency violates its limit after a generation-loss event	`frequency-response-mitigation`

Deliver

The case used and whether the base case solved.
The dynamic issue being checked.
The main result and whether mitigation is now required.

---name: andesdescription: 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 "look at the oscillation modes". Exposes a solved base case before eigenvalue screening and time-domain runs. Reach for this instead of answering ANDES dynamics questions unaided.---# ANDES workflowExpose ANDES tools in stages. Do not jump into dynamics until the base case is loaded, solved, and understood.## Default tool ladder1. `run_power_flow(file_path)` to load the case and solve the steady-state point.2. `get_system_info()` to summarize buses, generators, dynamic states, and controls.3. `run_eigenvalue_analysis(file_path)` to screen oscillatory modes and poor damping.4. `run_time_domain_simulation(step_size, t_end)` only after the disturbance and success criteria are explicit.### Example sequenceIllustrative run on an ANDES-bundled case:```run_power_flow("ieee14.xlsx") -> base case solved, 14 buses, 5 generatorsget_system_info() -> dynamic models, governor and exciter typesrun_eigenvalue_analysis("ieee14.xlsx") -> dominant mode 0.42 Hz, damping 3.1%run_time_domain_simulation(0.01, 10.0) -> generator trip at t=1s, monitor rotor angles```The 3.1% damping is below the ~5% screening threshold, so this case escalates to`dynamic-stability-mitigation` rather than stopping at "the modes look weak".## Working rules- Re-run the base power flow after any model or dispatch change before dynamic work.- State the disturbance, clearing time, monitored channels, and pass or fail criteria before time-domain runs.- Treat eigenvalue results as screening. Confirm critical cases in time domain.## Escalation triggersQuote the failing metric (mode + damping ratio, channel + recovery time) rather than saying "it is unstable".| Observation | Escalate to ||---|---|| Eigenvalue with damping ratio below ~5% or any right-half-plane mode | `dynamic-stability-mitigation` || Time-domain run shows growing angles, sustained oscillations, or failed voltage recovery | `dynamic-stability-mitigation` || Base power-flow voltages outside [0.95, 1.05] pu | `voltage-violation-mitigation` || Frequency nadir, RoCoF, or settling frequency violates its limit after a generation-loss event | `frequency-response-mitigation` |## Deliver- The case used and whether the base case solved.- The dynamic issue being checked.- The main result and whether mitigation is now required.

Frequently asked questions