How do I install the Frequency Response Mitigation skill?

Run npx skillmds@latest add power-agent/frequency-response-mitigation 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 Frequency Response Mitigation 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 Frequency Response Mitigation?

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 Frequency Response Mitigation free to use?

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

Who published Frequency Response Mitigation?

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

Frequency Response Mitigation by power-agent

Name: Frequency Response Mitigation
Author: power-agent

Frequency Response Mitigation

Senior power-engineer playbook for frequency-performance problems. Use whenever studies or operations show low system inertia, poor frequency nadir, high RoCoF, weak primary frequency response, UFLS encroachment, or reserve shortfall after loss of the largest unit or HVDC import. Triggers on "frequency nadir", "RoCoF too high", "inertia too low", "UFLS risk", "primary frequency response", or "loss of largest unit". Distinct from dynamic-stability-mitigation, which handles damping and angle stability rather than frequency containment.

power-agent a59f381 2.4 KB Updated Sep 17, 2026

File contents

Frequency response mitigation

Start only after the design event and the failing metric are explicit: which contingency, and which of nadir, RoCoF, or settling frequency violates its limit.

Preferred action order

Confirm the study setup is credible: largest credible loss, load-damping assumption, governor models actually enabled and responsive (deadbands, baseload flags), and the inertia of the dispatch being studied.
Increase responsive headroom first: commit or back down units to create governor headroom, and enable fast frequency response from storage, IBRs, or demand response — MW that respond in the first seconds matter most.
Raise inertia where headroom alone is insufficient: additional synchronous units, synchronous condensers (with flywheels where available), and must-run rules for low-inertia hours.
Fix control settings: droop, deadband, and response-withdrawal behavior so primary response is sustained, not transient.
Re-coordinate UFLS last — it is the backstop that protects the system when the fixes above fall short, not the fix itself.

Working rules

Evaluate the worst inertia hour (high renewables, light load), not the average dispatch.
Screen with system-level metrics, then confirm the critical cases in time domain (ANDES, PSS/E) before claiming the fix works.
Track the response trajectory: a good nadir with rapid response withdrawal can still fail the settling-frequency requirement.
Frequency containment and oscillation damping are different problems; route poorly damped responses to dynamic-stability-mitigation.

Deliver

The design event and the violated metric (nadir, RoCoF, settling frequency) with values.
The mitigation sequence: headroom, fast response, inertia, control fixes.
The first credible fix and the time-domain validation still needed.

---name: frequency-response-mitigationdescription: Senior power-engineer playbook for frequency-performance problems. Use whenever studies or operations show low system inertia, poor frequency nadir, high RoCoF, weak primary frequency response, UFLS encroachment, or reserve shortfall after loss of the largest unit or HVDC import. Triggers on "frequency nadir", "RoCoF too high", "inertia too low", "UFLS risk", "primary frequency response", or "loss of largest unit". Distinct from dynamic-stability-mitigation, which handles damping and angle stability rather than frequency containment.---# Frequency response mitigationStart only after the design event and the failing metric are explicit: which contingency, and which of nadir, RoCoF, or settling frequency violates its limit.## Preferred action order1. Confirm the study setup is credible: largest credible loss, load-damping assumption, governor models actually enabled and responsive (deadbands, baseload flags), and the inertia of the dispatch being studied.2. Increase responsive headroom first: commit or back down units to create governor headroom, and enable fast frequency response from storage, IBRs, or demand response — MW that respond in the first seconds matter most.3. Raise inertia where headroom alone is insufficient: additional synchronous units, synchronous condensers (with flywheels where available), and must-run rules for low-inertia hours.4. Fix control settings: droop, deadband, and response-withdrawal behavior so primary response is sustained, not transient.5. Re-coordinate UFLS last — it is the backstop that protects the system when the fixes above fall short, not the fix itself.## Working rules- Evaluate the worst inertia hour (high renewables, light load), not the average dispatch.- Screen with system-level metrics, then confirm the critical cases in time domain (ANDES, PSS/E) before claiming the fix works.- Track the response *trajectory*: a good nadir with rapid response withdrawal can still fail the settling-frequency requirement.- Frequency containment and oscillation damping are different problems; route poorly damped responses to `dynamic-stability-mitigation`.## Deliver- The design event and the violated metric (nadir, RoCoF, settling frequency) with values.- The mitigation sequence: headroom, fast response, inertia, control fixes.- The first credible fix and the time-domain validation still needed.

Frequently asked questions