home / skills / omer-metin / skills-for-antigravity / energy-systems
This skill helps you model energy systems, optimize grid flows, and simulate storage dispatch and market economics.
npx playbooks add skill omer-metin/skills-for-antigravity --skill energy-systemsReview the files below or copy the command above to add this skill to your agents.
---
name: energy-systems
description: Power systems engineering covering grid modeling, power flow analysis, energy storage dispatch, demand response, and electricity market economics. Spans transmission/distribution planning to real-time operations. Use when "power flow|load flow|grid model, energy storage|battery dispatch|ESS, demand response|load management|peak shaving, electricity market|LMP|locational marginal price, grid stability|frequency|voltage, capacity planning|resource adequacy, unit commitment|economic dispatch, transmission|distribution|power system, " mentioned.
---
# Energy Systems
## Identity
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
This skill provides practical power systems engineering capabilities for grid modeling, power flow analysis, storage dispatch, demand response, and electricity market economics. It supports tasks from transmission and distribution planning through real-time operations and economic dispatch. The design enforces reference-driven creation, diagnosis, and validation rules to ensure reproducible, auditable results.
When creating models or workflows, the skill follows the patterns defined in references/patterns.md to build grid representations, element parameterization, and solver workflows. For diagnosis it consults references/sharp_edges.md to detect common failure modes and explain root causes and mitigations. For reviews and input checks the skill applies the strict rules in references/validations.md to validate network data, constraints, and solution feasibility before recommending actions.
Which reference should I consult first when building a model?
Start with references/patterns.md to follow the prescribed model construction patterns, then run validations.
What do I do if a power flow doesn't converge?
Use references/sharp_edges.md to identify common causes (bad parameters, islanded buses, unrealistic limits) and apply suggested fixes.
How strict are the validation rules?
Validation rules in references/validations.md are strict and designed to catch physical and data-format violations before simulation.