opendss

Name: opendss
Author: Power-Agent

56stars12forks

How to install opendss?

power-agent/powerskills/opendss

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

Installs into the current project.

Summary

Progressive-disclosure workflow for OpenDSS distribution-feeder studies. Use whenever the user wants to compile a DSS model, solve a distribution circuit, inspect feeder bus voltages or power, sweep load multipliers, or run daily / harmonic studies through PowerMCP — even when th

Files · 1

View on GitHub

SKILL.md

1	# OpenDSS workflow
2
3	Start with a solved feeder. Do not jump to daily or harmonic studies until the base feeder compiles and the voltage profile is understood.
4
5	## Default tool ladder
6	1. `compile_and_solve(dss_file)` to load and solve the circuit.
7	2. `get_total_power()` and `get_bus_voltages()` to confirm the base operating point.
8	3. `set_load_multiplier(load_mult)` for simple scenario sweeps.
9	4. `run_daily_energy_meter(meter_name, hours)` for daily feeder behavior.
10	5. `get_harmonic_results(load_name, harmonic)` only after the harmonic question is well scoped.
11
12	## Working rules
13	- Fix compile or solve errors before any scenario analysis.
14	- For voltage issues, inspect the weak buses first.
15	- Separate load-growth screening from harmonic analysis; they answer different questions.
16	- Keep feeder, meter, and load names explicit in the response.
17
18	## Escalation triggers
19	Quote the weak bus + voltage or the loaded element rather than saying "there is a problem".
20
21	\| Observation \| Escalate to \|
22	\|---\|---\|
23	\| `get_bus_voltages` shows pu outside the feeder band (e.g. < 0.95 or > 1.05) \| `voltage-violation-mitigation` \|
24	\| A line, transformer, or regulator loaded above its rating \| `thermal-overload-mitigation` \|
25	\| `compile_and_solve` succeeds to compile but the solution diverges \| `convergence-failure-mitigation` \|
26	\| The study is DER (PV, storage) integration or hosting capacity on the feeder \| `der-hosting-capacity-mitigation` \|
27
28	## Deliver
29	- The compiled feeder and base-case status.
30	- The voltage or power quantities checked.
31	- Any scenario result and whether mitigation is needed.

People who liked this also viewed

6 picks

Type

opendss

56stars12forks

View on GitHub

How to install opendss?

power-agent/powerskills/opendss

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# OpenDSS workflow
2
3	Start with a solved feeder. Do not jump to daily or harmonic studies until the base feeder compiles and the voltage profile is understood.
4
5	## Default tool ladder
6	1. `compile_and_solve(dss_file)` to load and solve the circuit.
7	2. `get_total_power()` and `get_bus_voltages()` to confirm the base operating point.
8	3. `set_load_multiplier(load_mult)` for simple scenario sweeps.
9	4. `run_daily_energy_meter(meter_name, hours)` for daily feeder behavior.
10	5. `get_harmonic_results(load_name, harmonic)` only after the harmonic question is well scoped.
11
12	## Working rules
13	- Fix compile or solve errors before any scenario analysis.
14	- For voltage issues, inspect the weak buses first.
15	- Separate load-growth screening from harmonic analysis; they answer different questions.
16	- Keep feeder, meter, and load names explicit in the response.
17
18	## Escalation triggers
19	Quote the weak bus + voltage or the loaded element rather than saying "there is a problem".
20
21	\| Observation \| Escalate to \|
22	\|---\|---\|
23	\| `get_bus_voltages` shows pu outside the feeder band (e.g. < 0.95 or > 1.05) \| `voltage-violation-mitigation` \|
24	\| A line, transformer, or regulator loaded above its rating \| `thermal-overload-mitigation` \|
25	\| `compile_and_solve` succeeds to compile but the solution diverges \| `convergence-failure-mitigation` \|
26	\| The study is DER (PV, storage) integration or hosting capacity on the feeder \| `der-hosting-capacity-mitigation` \|
27
28	## Deliver
29	- The compiled feeder and base-case status.
30	- The voltage or power quantities checked.
31	- Any scenario result and whether mitigation is needed.

People who liked this also viewed

6 picks

Type