[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2CSVFWHKHW7PKR75KHV8R":3,"skill-same:01M7F2CSVFWHKHW7PKR75KHV8R":51},{"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},"01M7F2CSVFWHKHW7PKR75KHV8R","interconnection-impact-mitigation",null,"Senior power-engineer playbook for screening and mitigating the grid impact of a new generator, storage, or large-load interconnection. Use whenever the question is whether X MW can connect at a point of interconnection and what upgrades it needs. Triggers on 'interconnection study', 'system impact","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\u002Finterconnection-impact-mitigation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: interconnection-impact-mitigation\ndescription: \"Senior power-engineer playbook for screening and mitigating the grid impact of a new generator, storage, or large-load interconnection. Use whenever the question is whether X MW can connect at a point of interconnection and what upgrades it needs. Triggers on 'interconnection study', 'system impact\"\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-engineering\u002Fskills\u002Finterconnection-impact-mitigation\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n# Interconnection impact mitigation\n\nStart with a defined injection: MW and MVAr capability, the point of interconnection (POI), and the dispatch scenarios to study.\n\n## Preferred action order\n1. Pin down the study scenario set: peak and off-peak cases, high-renewable dispatch, and the prior-queued projects that must be modeled as in-service.\n2. Run steady-state screens with the addition: base case and N-1 power flow, thermal loading and voltage screens around the POI. Route violations to `thermal-overload-mitigation` and `voltage-violation-mitigation` for the corrective toolkit.\n3. Check weak-grid risk for inverter-based resources: short-circuit ratio at the POI. Low SCR (roughly below 3, critical below 2) flags control-interaction and stability risk — consider grid-forming controls, synchronous condensers, or POI relocation.\n4. Verify reactive capability and voltage control: power-factor range and voltage ride-through at the POI against the applicable interconnection requirements.\n5. Identify the binding constraint and assemble the mitigation set: network upgrades, an output-limitation or curtailment agreement, reactive devices, or phased interconnection — sized to the smallest set that clears the binding screen.\n\n## Working rules\n- Screen with linear tools (PTDF on the injection) before full N-1 reruns; confirm the short list in AC.\n- The fault contribution of the new plant changes breaker duty nearby; screen it and route over-duty to `short-circuit-mitigation`.\n- Restudy after any material change in plant size, POI, or queue assumptions — interconnection results do not transfer between scenarios.\n- Separate \"needed to connect safely\" from \"needed to deliver full output\" — reliability upgrades and deliverability upgrades have different urgency and cost allocation.\n\n## Deliver\n- The injection studied (MW, POI, scenarios) and the screens it passed.\n- The binding constraint with numbers (element, loading or voltage, contingency).\n- The recommended mitigation set and what must be restudied if assumptions move.\n","# Interconnection impact mitigation\n\nStart with a defined injection: MW and MVAr capability, the point of interconnection (POI), and the dispatch scenarios to study.\n\n## Preferred action order\n1. Pin down the study scenario set: peak and off-peak cases, high-renewable dispatch, and the prior-queued projects that must be modeled as in-service.\n2. Run steady-state screens with the addition: base case and N-1 power flow, thermal loading and voltage screens around the POI. Route violations to `thermal-overload-mitigation` and `voltage-violation-mitigation` for the corrective toolkit.\n3. Check weak-grid risk for inverter-based resources: short-circuit ratio at the POI. Low SCR (roughly below 3, critical below 2) flags control-interaction and stability risk — consider grid-forming controls, synchronous condensers, or POI relocation.\n4. Verify reactive capability and voltage control: power-factor range and voltage ride-through at the POI against the applicable interconnection requirements.\n5. Identify the binding constraint and assemble the mitigation set: network upgrades, an output-limitation or curtailment agreement, reactive devices, or phased interconnection — sized to the smallest set that clears the binding screen.\n\n## Working rules\n- Screen with linear tools (PTDF on the injection) before full N-1 reruns; confirm the short list in AC.\n- The fault contribution of the new plant changes breaker duty nearby; screen it and route over-duty to `short-circuit-mitigation`.\n- Restudy after any material change in plant size, POI, or queue assumptions — interconnection results do not transfer between scenarios.\n- Separate \"needed to connect safely\" from \"needed to deliver full output\" — reliability upgrades and deliverability upgrades have different urgency and cost allocation.\n\n## Deliver\n- The injection studied (MW, POI, scenarios) and the screens it passed.\n- The binding constraint with numbers (element, loading or voltage, contingency).\n- The recommended mitigation set and what must be restudied if assumptions move.\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-engineering\u002Fskills\u002Finterconnection-impact-mitigation\u002FSKILL.md","Power-Agent\u002FPowerSkills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Felectrical-engineering\u002Finterconnection-impact-mitigation","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 interconnection-impact-mitigation",{"tool":43,"command":44},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill interconnection-impact-mitigation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill interconnection-impact-mitigation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Felectrical-engineering\u002Finterconnection-impact-mitigation\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]