[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2DV724VCW8C475HZCBAP4":3,"skill-same:01M7F2DV724VCW8C475HZCBAP4":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7F2DV724VCW8C475HZCBAP4","potpourri",null,"Progressive-disclosure workflow for potpourri (opf-potpourri) AC\u002FDC and multi-period optimal power flow on pandapower distribution networks, including storage and flexible resources. Use whenever the user wants to optimise rather than just simulate a pandapower or SimBench grid — curtail or redispat","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: potpourri\ndescription: \"Progressive-disclosure workflow for potpourri (opf-potpourri) AC\u002FDC and multi-period optimal power flow on pandapower distribution networks, including storage and flexible resources. Use whenever the user wants to optimise rather than just simulate a pandapower or SimBench grid — curtail or redispat\"\ncategory: electrical-engineering\nversion: 1.0.0\ndisable-model-invocation: false\nrisk: low\nsource: \"https:\u002F\u002Fgithub.com\u002FPower-Agent\u002FPowerSkills\"\nsource_repository: \"Power-Agent\u002FPowerSkills\"\nsource_path: \"powerskills-tool\u002Fskills\u002Fpotpourri\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n# potpourri workflow\n\npotpourri builds Pyomo AC\u002FDC OPF models over pandapower networks. There is no\nPowerMCP server for it, so drive it through its Python API using the bundled\nscripts. Establish a credible network and base case before optimising, and a\ncredible single period before a multi-period horizon.\n\n## Default ladder\n1. `scripts\u002Finspect_case.py --case \u003Csimbench:CODE|path.json>` — load, validate,\n   and solve the pandapower base case. Do not skip this: an OPF that fails later\n   is usually a data problem, and this is where data problems are cheap to find.\n2. `scripts\u002Fsolve_opf.py --list-solvers` — confirm what is installed. AC needs an\n   NLP solver (IPOPT); DC needs an LP\u002FMIP solver (GLPK, CBC, HiGHS).\n3. `scripts\u002Fsolve_opf.py --formulation dc --objective ext_grid_import` — linear\n   screening for congestion and active-power headroom.\n4. `scripts\u002Fsolve_opf.py --formulation ac --objective \u003Cobjective>` — the real\n   answer whenever voltage, reactive power, losses, or inverter capability matters.\n5. `scripts\u002Fsolve_opf.py --horizon \u003CN> --battery-penetration \u003Cpct> --seed \u003Cn>` —\n   multi-period, only once a single period is credible.\n\nBoth scripts print an engineering summary, take `--json` for a machine-readable\npayload, and exit non-zero on genuine failure (1 = solved but not optimal,\n2 = bad input, 3 = no compatible solver).\n\n## Working rules\n- **Never read `net.res_*` without checking termination.** The model constructor\n  runs `pp.runpp`, so `net.res_*` is always populated; when a solve is not\n  optimal potpourri skips its result mapping and those tables still hold the\n  *base case*. `solve_opf.py` reports no results at all in that situation.\n- **Multi-period `solve(to_net=True)` writes nothing.** It only logs that it\n  did. Map each step with\n  `pyo_to_net_multi_period.pyo_sol_to_net_res(net, model, t)`.\n- **DC gives no voltage answer.** After a DC OPF `net.res_bus.vm_pu` is a flat\n  1.0 placeholder. DC feasibility never establishes AC feasibility, least of all\n  in distribution networks where voltage and reactive power are the binding\n  physics.\n- **A local NLP optimum is not a global one.** IPOPT on a nonconvex AC OPF gives\n  a locally optimal point; say \"locally optimal\", and never claim global\n  optimality without a global solver reporting it.\n- **Quote numbers, units, and the limit that was configured** — bus and `vm_pu`,\n  element and `loading_percent` against its rating, MW\u002FMvar\u002FMWh, and the solver's\n  own termination condition.\n- Match the objective to the question and state its side effects: voltage-\n  deviation minimisation puts no value on energy, so where curtailment is free it\n  will curtail everything. Check the reported curtailment before accepting a\n  dispatch.\n\n## Reference material\nRead the file that matches what you are doing; do not load them all.\n- `references\u002FAPI_REFERENCE.md` — verified classes, `add_OPF` options, objectives,\n  devices, result extraction, and what is *not* supported.\n- `references\u002FFORMULATION_GUIDE.md` — AC vs DC, snapshot vs multi-period,\n  LP\u002FNLP\u002FMINLP consequences, and single- vs multi-period model differences.\n- `references\u002FSOLVER_GUIDE.md` — solver compatibility, termination\n  interpretation, and the ordered infeasibility diagnosis.\n- `references\u002FVALIDATION_GUIDE.md` — power balance, constraint checks, binding\n  constraints, cross-validation against pandapower, and the reporting checklist.\n\n## Local assets in this skill\n- `scripts\u002Finspect_case.py` — load, validate, base power flow.\n- `scripts\u002Fsolve_opf.py` — build, solve, validate, and escalate.\n- `scripts\u002Ftest_scripts.py` — smoke tests; skips cleanly without solvers.\n- `requirements.txt` — including the `pandapower\u003C3.5` pin potpourri needs.\n\n## Escalation triggers\nQuote the element, value, unit, and configured limit that tripped each row.\n`solve_opf.py` emits these in its `escalation` payload.\n\n| Observation | Escalate to |\n|---|---|\n| Bus `vm_pu` outside the configured `[min_vm_pu, max_vm_pu]` band (AC only) | `voltage-violation-mitigation` |\n| `res_line` \u002F `res_trafo` `loading_percent` above its configured `max_loading_percent` | `thermal-overload-mitigation` |\n| `termination_condition` is `infeasible` or `unbounded`, or curtailment exceeds 5 % of available renewable energy | `operations-planning-mitigation` |\n| Solve ends in any other non-optimal condition (`other`, `maxIterations`, `maxTimeLimit`), or the base `pp.runpp` fails | `convergence-failure-mitigation` |\n| Net export through the external grid, or PV-driven voltage rise on a distribution feeder | `der-hosting-capacity-mitigation` |\n| A newly added generator, storage unit, or large load causes any of the above | `interconnection-impact-mitigation` |\n\n## Deliver\n- Network source and size, study type and formulation, horizon and resolution.\n- Objective, what it means in units, and the solver plus its termination condition.\n- Power balance, voltage extrema with buses, worst line and transformer loading,\n  dispatch by group, curtailment, and storage SOC extrema where relevant.\n- Binding constraints, and limitations (local optimum, DC assumptions, storage\n  modelling caveats).\n- Any justified escalation, with the numbers behind it.\n","# potpourri workflow\n\npotpourri builds Pyomo AC\u002FDC OPF models over pandapower networks. There is no\nPowerMCP server for it, so drive it through its Python API using the bundled\nscripts. Establish a credible network and base case before optimising, and a\ncredible single period before a multi-period horizon.\n\n## Default ladder\n1. `scripts\u002Finspect_case.py --case \u003Csimbench:CODE|path.json>` — load, validate,\n   and solve the pandapower base case. Do not skip this: an OPF that fails later\n   is usually a data problem, and this is where data problems are cheap to find.\n2. `scripts\u002Fsolve_opf.py --list-solvers` — confirm what is installed. AC needs an\n   NLP solver (IPOPT); DC needs an LP\u002FMIP solver (GLPK, CBC, HiGHS).\n3. `scripts\u002Fsolve_opf.py --formulation dc --objective ext_grid_import` — linear\n   screening for congestion and active-power headroom.\n4. `scripts\u002Fsolve_opf.py --formulation ac --objective \u003Cobjective>` — the real\n   answer whenever voltage, reactive power, losses, or inverter capability matters.\n5. `scripts\u002Fsolve_opf.py --horizon \u003CN> --battery-penetration \u003Cpct> --seed \u003Cn>` —\n   multi-period, only once a single period is credible.\n\nBoth scripts print an engineering summary, take `--json` for a machine-readable\npayload, and exit non-zero on genuine failure (1 = solved but not optimal,\n2 = bad input, 3 = no compatible solver).\n\n## Working rules\n- **Never read `net.res_*` without checking termination.** The model constructor\n  runs `pp.runpp`, so `net.res_*` is always populated; when a solve is not\n  optimal potpourri skips its result mapping and those tables still hold the\n  *base case*. `solve_opf.py` reports no results at all in that situation.\n- **Multi-period `solve(to_net=True)` writes nothing.** It only logs that it\n  did. Map each step with\n  `pyo_to_net_multi_period.pyo_sol_to_net_res(net, model, t)`.\n- **DC gives no voltage answer.** After a DC OPF `net.res_bus.vm_pu` is a flat\n  1.0 placeholder. DC feasibility never establishes AC feasibility, least of all\n  in distribution networks where voltage and reactive power are the binding\n  physics.\n- **A local NLP optimum is not a global one.** IPOPT on a nonconvex AC OPF gives\n  a locally optimal point; say \"locally optimal\", and never claim global\n  optimality without a global solver reporting it.\n- **Quote numbers, units, and the limit that was configured** — bus and `vm_pu`,\n  element and `loading_percent` against its rating, MW\u002FMvar\u002FMWh, and the solver's\n  own termination condition.\n- Match the objective to the question and state its side effects: voltage-\n  deviation minimisation puts no value on energy, so where curtailment is free it\n  will curtail everything. Check the reported curtailment before accepting a\n  dispatch.\n\n## Reference material\nRead the file that matches what you are doing; do not load them all.\n- `references\u002FAPI_REFERENCE.md` — verified classes, `add_OPF` options, objectives,\n  devices, result extraction, and what is *not* supported.\n- `references\u002FFORMULATION_GUIDE.md` — AC vs DC, snapshot vs multi-period,\n  LP\u002FNLP\u002FMINLP consequences, and single- vs multi-period model differences.\n- `references\u002FSOLVER_GUIDE.md` — solver compatibility, termination\n  interpretation, and the ordered infeasibility diagnosis.\n- `references\u002FVALIDATION_GUIDE.md` — power balance, constraint checks, binding\n  constraints, cross-validation against pandapower, and the reporting checklist.\n\n## Local assets in this skill\n- `scripts\u002Finspect_case.py` — load, validate, base power flow.\n- `scripts\u002Fsolve_opf.py` — build, solve, validate, and escalate.\n- `scripts\u002Ftest_scripts.py` — smoke tests; skips cleanly without solvers.\n- `requirements.txt` — including the `pandapower\u003C3.5` pin potpourri needs.\n\n## Escalation triggers\nQuote the element, value, unit, and configured limit that tripped each row.\n`solve_opf.py` emits these in its `escalation` payload.\n\n| Observation | Escalate to |\n|---|---|\n| Bus `vm_pu` outside the configured `[min_vm_pu, max_vm_pu]` band (AC only) | `voltage-violation-mitigation` |\n| `res_line` \u002F `res_trafo` `loading_percent` above its configured `max_loading_percent` | `thermal-overload-mitigation` |\n| `termination_condition` is `infeasible` or `unbounded`, or curtailment exceeds 5 % of available renewable energy | `operations-planning-mitigation` |\n| Solve ends in any other non-optimal condition (`other`, `maxIterations`, `maxTimeLimit`), or the base `pp.runpp` fails | `convergence-failure-mitigation` |\n| Net export through the external grid, or PV-driven voltage rise on a distribution feeder | `der-hosting-capacity-mitigation` |\n| A newly added generator, storage unit, or large load causes any of the above | `interconnection-impact-mitigation` |\n\n## Deliver\n- Network source and size, study type and formulation, horizon and resolution.\n- Objective, what it means in units, and the solver plus its termination condition.\n- Power balance, voltage extrema with buses, worst line and transformer loading,\n  dispatch by group, curtailment, and storage SOC extrema where relevant.\n- Binding constraints, and limitations (local optimum, DC assumptions, storage\n  modelling caveats).\n- Any justified escalation, with the numbers behind it.\n",{"name":5,"risk":24,"source":25,"license":15,"version":26,"category":27,"description":7,"imported_at":28,"source_path":29,"source_repository":30,"disable-model-invocation":20},"low","https:\u002F\u002Fgithub.com\u002FPower-Agent\u002FPowerSkills","1.0.0","electrical-engineering","2026-09-20","powerskills-tool\u002Fskills\u002Fpotpourri\u002FSKILL.md","Power-Agent\u002FPowerSkills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Felectrical-engineering\u002Fpotpourri","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill potpourri",{"tool":43,"command":44},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill potpourri",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill potpourri","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002FSKILL.md",true,[51,57,61,65,69,73,79,83],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002FAPI_REFERENCE.md","REFERENCE","参考文档",14748,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Freferences\u002FAPI_REFERENCE.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002FFORMULATION_GUIDE.md",9297,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Freferences\u002FFORMULATION_GUIDE.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002FSOLVER_GUIDE.md",10828,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Freferences\u002FSOLVER_GUIDE.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002FVALIDATION_GUIDE.md",10030,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Freferences\u002FVALIDATION_GUIDE.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"requirements.txt",1604,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Frequirements.txt",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Finspect_case.py","SCRIPT","脚本",25307,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Fscripts\u002Finspect_case.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fsolve_opf.py",61423,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Fscripts\u002Fsolve_opf.py",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Ftest_scripts.py",8898,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Fpotpourri\u002Fscripts\u002Ftest_scripts.py",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]