[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AR9VJC8HCW19VNET8XQ7W8":3,"skill-same:01M7AR9VJC8HCW19VNET8XQ7W8":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AR9VJC8HCW19VNET8XQ7W8","power-scada-ems-and-protocols",null,"Use when integrating with grid control systems: SCADA, energy management systems and distribution management systems and what each actually does, and the protocols including DNP3, IEC 61850, IEC 60870-5 and Modbus with their data models, timing and security characteristics.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-scada-ems-and-protocols\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: power-scada-ems-and-protocols\ndescription: \"Use when integrating with grid control systems: SCADA, energy management systems and distribution management systems and what each actually does, and the protocols including DNP3, IEC 61850, IEC 60870-5 and Modbus with their data models, timing and security characteristics.\"\n---\n\n# Power Engineering: SCADA, EMS and DMS, and the Protocols\n\n> **Part 3 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §6–§7. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-inverters-storage-markets-and-datacenters` (§8–§12), `power-reference` (§13–§18). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 → `power-reference` for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §6. SCADA, EMS, and DMS\n\n```\nField:  sensors, CTs\u002FVTs, IEDs, relays, RTUs\n   ↓ (§7 protocols)\nSCADA:  acquisition, alarms, supervisory control, historian\n   ↓\nEMS (transmission):  state estimation, contingency analysis, OPF, AGC, dispatch\nDMS (distribution):  fault location\u002Fisolation\u002Frestoration (FLISR), volt\u002FVAr,\n                     outage management, DERMS\n   ↓\nMarkets (§10), planning, asset management\n```\n**⚠️ Contingency analysis is the control room's core loop**: continuously simulate\n**\"what if this element fails?\"** across a large list, and confirm the system stays within\nlimits. **The `N−1` criterion means operating so that any single failure is survivable** —\n⚠️ **so the grid is deliberately run below its physical capability, always.**\n\n**⚠️ The operator is the user, and the design constraints are unusual**: alarm floods\nduring a real event are a documented contributor to blackout escalation; the system must\ndegrade legibly; and ⚠️ **the software's job during a crisis is to reduce the number of\nthings a human must decide, not to present more information.**\n\n---\n\n## §7. Protocols\n\n| Protocol | Domain | ⚠️ Notes |\n|---|---|---|\n| **Modbus** | Ubiquitous, simple | ⚠️ **No security whatsoever. Assume it's plaintext and trusted-by-position** |\n| **DNP3** | ⚠️ **North American SCADA standard** | Event-driven with timestamps and quality flags; **Secure Authentication exists — use it** |\n| **IEC 60870-5-101\u002F104** | European SCADA equivalent | 104 is the TCP\u002FIP variant |\n| **IEC 61850** | ⚠️ **Substation automation, and the modern one** | Object model + SCL config; **GOOSE** and **Sampled Values** |\n| **IEC 61970\u002F61968 CIM** | ⚠️ **Network model exchange** | The semantic model behind EMS\u002FDMS interoperability |\n| **IEEE C37.118 \u002F IEEE 2664** | Synchrophasors | PMU streaming (§4.2 → `power-system-analysis-and-protection`) |\n| **OpenADR, IEEE 2030.5** | Demand response, DER | Utility-to-customer |\n| **OPC UA** | Industrial | Increasingly a bridge layer |\n\n**⚠️ IEC 61850 GOOSE deserves specific attention**: it's a **multicast layer-2 publish\u002F\nsubscribe message for protection signalling with a ~4 ms delivery requirement.** ⚠️ **It\nretransmits with decreasing intervals to survive loss, and it bypasses the IP stack\nentirely — so ordinary network engineering intuitions do not apply.** **Sampled Values\n(SV)** streams digitized CT\u002FVT waveforms at high rate, ⚠️ **which turns substation\nprotection into a hard-real-time networking problem and makes PTP time synchronization\nsafety-relevant.**\n\n> **⚠️ GOTCHA — nearly all of these protocols were designed for physically isolated\n> networks and have no meaningful authentication by default.** **Security in this domain\n> is overwhelmingly perimeter- and segmentation-based** (§11.2 → `power-inverters-storage-markets-and-datacenters`). ⚠️ **Never assume a\n> protocol validates who sent a command.**\n","# Power Engineering: SCADA, EMS and DMS, and the Protocols\n\n> **Part 3 of 5** of the *Power Engineering* reference (plugin `power-engineering`), covering §6–§7. Sibling skills: `power-ac-fundamentals-generation-and-grid` (§0–§3), `power-system-analysis-and-protection` (§4–§5), `power-inverters-storage-markets-and-datacenters` (§8–§12), `power-reference` (§13–§18). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Circuit theory and power system analysis are settled; the inverter-dominated grid and datacenter load growth moved fast. See §15 → `power-reference` for both, dated.\n\n> **Scope.** Complements an electrical-engineering reference, which is circuit-level —\n> components, op-amps, PCB layout, signal integrity. ⚠️ **This is grid scale: kilovolts\n> and megawatts, and the software that runs it.**\n>\n> **⚠️ GOTCHA** boxes mark what kills people, destroys equipment, or causes blackouts.\n>\n> **The three ideas that organize the whole field:**\n> 1. **⚠️ Generation must equal load, continuously, everywhere.** The grid stores almost\n>    nothing. **Frequency IS the balance signal** — it falls when load exceeds generation\n>    and rises when it doesn't, in real time, across a continent (§1.4 → `power-ac-fundamentals-generation-and-grid`).\n> 2. **⚠️ Reactive power is not \"wasted\" power — it's a separate commodity that must also\n>    balance, and it's local.** Real power flows across a system; reactive power doesn't\n>    travel well, so voltage is a local problem and frequency is a global one (§1.2 → `power-ac-fundamentals-generation-and-grid`).\n> 3. **⚠️ Protection is the fastest software in the system and it acts on trust.** A relay\n>    decides in milliseconds to disconnect equipment, and it must be right — a false trip\n>    causes an outage, a missed trip destroys equipment or kills someone (§5 → `power-system-analysis-and-protection`).\n\n---\n\n## §6. SCADA, EMS, and DMS\n\n```\nField:  sensors, CTs\u002FVTs, IEDs, relays, RTUs\n   ↓ (§7 protocols)\nSCADA:  acquisition, alarms, supervisory control, historian\n   ↓\nEMS (transmission):  state estimation, contingency analysis, OPF, AGC, dispatch\nDMS (distribution):  fault location\u002Fisolation\u002Frestoration (FLISR), volt\u002FVAr,\n                     outage management, DERMS\n   ↓\nMarkets (§10), planning, asset management\n```\n**⚠️ Contingency analysis is the control room's core loop**: continuously simulate\n**\"what if this element fails?\"** across a large list, and confirm the system stays within\nlimits. **The `N−1` criterion means operating so that any single failure is survivable** —\n⚠️ **so the grid is deliberately run below its physical capability, always.**\n\n**⚠️ The operator is the user, and the design constraints are unusual**: alarm floods\nduring a real event are a documented contributor to blackout escalation; the system must\ndegrade legibly; and ⚠️ **the software's job during a crisis is to reduce the number of\nthings a human must decide, not to present more information.**\n\n---\n\n## §7. Protocols\n\n| Protocol | Domain | ⚠️ Notes |\n|---|---|---|\n| **Modbus** | Ubiquitous, simple | ⚠️ **No security whatsoever. Assume it's plaintext and trusted-by-position** |\n| **DNP3** | ⚠️ **North American SCADA standard** | Event-driven with timestamps and quality flags; **Secure Authentication exists — use it** |\n| **IEC 60870-5-101\u002F104** | European SCADA equivalent | 104 is the TCP\u002FIP variant |\n| **IEC 61850** | ⚠️ **Substation automation, and the modern one** | Object model + SCL config; **GOOSE** and **Sampled Values** |\n| **IEC 61970\u002F61968 CIM** | ⚠️ **Network model exchange** | The semantic model behind EMS\u002FDMS interoperability |\n| **IEEE C37.118 \u002F IEEE 2664** | Synchrophasors | PMU streaming (§4.2 → `power-system-analysis-and-protection`) |\n| **OpenADR, IEEE 2030.5** | Demand response, DER | Utility-to-customer |\n| **OPC UA** | Industrial | Increasingly a bridge layer |\n\n**⚠️ IEC 61850 GOOSE deserves specific attention**: it's a **multicast layer-2 publish\u002F\nsubscribe message for protection signalling with a ~4 ms delivery requirement.** ⚠️ **It\nretransmits with decreasing intervals to survive loss, and it bypasses the IP stack\nentirely — so ordinary network engineering intuitions do not apply.** **Sampled Values\n(SV)** streams digitized CT\u002FVT waveforms at high rate, ⚠️ **which turns substation\nprotection into a hard-real-time networking problem and makes PTP time synchronization\nsafety-relevant.**\n\n> **⚠️ GOTCHA — nearly all of these protocols were designed for physically isolated\n> networks and have no meaningful authentication by default.** **Security in this domain\n> is overwhelmingly perimeter- and segmentation-based** (§11.2 → `power-inverters-storage-markets-and-datacenters`). ⚠️ **Never assume a\n> protocol validates who sent a command.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-scada-ems-and-protocols",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill power-scada-ems-and-protocols",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill power-scada-ems-and-protocols",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill power-scada-ems-and-protocols","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpower-engineering\u002Fskills\u002Fpower-scada-ems-and-protocols\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]