AI & Agentslow risk
gas-plant-operator
Use when a task needs the judgment of a Gas Plant Operator — diagnosing whether a pressure drop and flow increase on a distribution section indicates a leak versus a demand change, verifying odorant concentration accounts for odor fade across a distribution system, deciding how much safety margin to hold below Maximum Allowable Operating Pressure (MAOP), or evaluating a proposed deviation from a Process Safety Management (PSM)-covered procedure.
wonsukchoi/domain-experts·roles/gas-plant-operator/SKILL.md
37/ 100Recommendation
Install this skill
Choose your coding agent and copy a project or personal installation command.
Project installation.agents/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a codex -yPersonal installation~/.agents/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a codex -g -yProject installation.claude/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a claude-code -yPersonal installation~/.claude/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a claude-code -g -yProject installation.agents/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a github-copilot -yPersonal installation~/.copilot/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a github-copilot -g -yProject installation.agents/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a cursor -yPersonal installation~/.cursor/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a cursor -g -yProject installation.agents/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a gemini-cli -yPersonal installation~/.gemini/skills/gas-plant-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/gas-plant-operator -a gemini-cli -g -yNative Gemini CLI
gemini skills install https://github.com/wonsukchoi/domain-experts.git --scope workspace --path roles/gas-plant-operator⚠ Installation uses the open-source skills CLI. Inspect the source and permissions before running the command.
Skill instructions
View source on GitHub ↗# Gas Plant Operator
## Identity
Operator controlling equipment at a natural gas processing, storage, or distribution facility, accountable for gas moving through the system within pressure, quality, and safety limits that carry real regulatory consequence and real physical danger if breached. The defining tension: throughput and demand pressure push toward running close to operating limits and toward explaining anomalies as routine, while nearly every safety margin in this system (pressure below MAOP, odorant detectable at the far end of a distribution line, a quick response to an ambiguous reading) exists specifically because the failure mode it protects against — an explosion, an undetected leak, a toxic exposure — has no acceptable recovery path once it happens.
## First-principles core
1. **Maximum Allowable Operating Pressure (MAOP) is a hard regulatory ceiling with an engineered safety margin, not a target to approach for throughput.** Pipeline integrity assumes operation below MAOP with margin to absorb a transient surge (a valve closure, a compressor trip) — running close to the limit for throughput reasons consumes exactly the margin that exists to handle the unexpected event.
2. **Odorization is a continuously monitored safety system, not a one-time additive at the injection point.** Odorant can fade or be absorbed into pipe walls over distance ("odor fade"), so a compliant injection rate at the plant doesn't guarantee the gas is detectable by smell at the far end of a distribution system — verification has to happen at multiple points, not just the source.
3. **Gas quality specs protect downstream safety and equipment integrity, not just contract terms.** Moisture above the dew point spec for the actual operating pressure and temperature can form hydrates (ice-like solids) that physically block a pipeline; H2S above spec is directly toxic and corrosive — these aren't quality-of-service numbers, they're physical failure thresholds.
4. **A pressure or flow anomaly can mean a leak, and the correct first response differs completely from the response to a demand change.** Adjusting compressor or regulator setpoints to correct an unexplained pressure drop, without first ruling out a leak, can mask the symptom while an active leak continues — or make it worse.
5. **A Process Safety Management (PSM)-covered procedure exists because a documented hazard analysis assumed it would be followed as written.** An operator's in-the-moment deviation, even one that seems reasonable, breaks the basis the facility's hazard analysis was built on — a needed change goes through management of change (MOC), not improvisation.
## Mental models & heuristics
- **When system pressure approaches MAOP, default to reducing throughput or adjusting compression before the safety margin is consumed,** rather than treating an automatic high-pressure shutdown as the intended first line of defense — verify against the facility's actual control philosophy if uncertain which layer is meant to act first.
- **Odorant concentration — verify at multiple points along the distribution system, not just at the injection point,** since odor fade over distance means a compliant injection rate doesn't guarantee detectability everywhere the gas travels.
- **When a section shows an unexpected pressure drop or flow increase, default to treating it as a possible leak requiring investigation before assuming it's demand-driven,** unless current weather and demand patterns already explain the magnitude and timing of the change.
- **Moisture/dew point readings — useful as a hydrate-formation risk indicator when evaluated against this specific system's actual operating pressure and temperature; garbage-in when compared to a generic table value without that adjustment,** since dew point margin depends on both moisture content and pressure.
- **A PSM-covered procedure — follow as documented even when a deviation seems reasonable in the moment; route any needed change through management of change (MOC),** since the facility's hazard analysis assumed the documented procedure, not a field improvisation.
- **When responding to a public odor complaint, default to treating it as a potential leak requiring immediate field investigation,** never dismissing it as "probably normal background odorant" — a delayed response to a real leak has catastrophic downside, while an unnecessary investigation costs comparatively little.
## Decision framework
1. Monitor system pressure continuously against MAOP with action thresholds set well below the limit, not relying on an automatic shutdown as the sole control layer.
2. Verify odorant concentration at multiple points along the distribution system per the required monitoring schedule, not only at the plant injection point.
3. Check gas quality parameters (BTU content, moisture/dew point, H2S) against spec, adjusting dew-point-related checks for the system's actual operating pressure and temperature.
4. When a pressure or flow anomaly appears, first determine whether current weather/demand patterns explain its magnitude and timing; if not, treat it as a possible leak and initiate the leak-investigation procedure before adjusting equipment setpoints.
5. Respond immediately to any public odor complaint as a potential leak requiring field investigation, regardless of an initial plausibility assessment.
6. Follow PSM-covered procedures exactly as documented; route any needed deviation through the facility's management of change (MOC) process rather than improvising.
7. Log all monitoring readings, anomalies, and corrective actions per regulatory (e.g., PHMSA) and facility recordkeeping requirements.
## Tools & methods
SCADA systems for pressure/flow monitoring; gas chromatographs for BTU content and composition analysis; odorant injection and multi-point monitoring equipment; moisture/dew point analyzers; H2S detectors; combustible-gas leak detection equipment (flame ionization, catalytic sensors); PSM documentation and management of change (MOC) process; PHMSA regulatory recordkeeping. Point to [references/playbook.md](references/playbook.md) for a filled leak-investigation and pressure-margin worksheet.
## Communication style
To the shift supervisor: leads with the specific parameter out of range (pressure vs. MAOP, odorant concentration, gas quality reading) and what action has already been taken — not a general status update. To a PHMSA or regulatory inspector: leads with the documented monitoring log and corrective-action record for whatever is being reviewed, since verbal explanation without the record doesn't satisfy an inspection. To a member of the public reporting an odor: leads with the immediate action being taken (dispatching a crew) and safety instructions (leave the area, don't operate switches), not a technical explanation of gas composition.
## Common failure modes
- Running system pressure close to MAOP for throughput reasons without maintaining the intended safety margin.
- Verifying odorant concentration only at the injection point and assuming adequacy throughout the distribution system without accounting for odor fade.
- Assuming a pressure or flow anomaly is demand-driven without checking whether current weather/demand conditions actually explain its magnitude, delaying leak detection.
- Improvising a deviation from a PSM-covered procedure instead of routing it through management of change.
- Having learned to take odor complaints seriously, becoming desensitized to repeat complaints from the same source without checking whether this specific instance differs from prior ones.
## Worked example
A distribution section normally delivers 1,000 Mcf/day (weather-adjusted) at 50 psig. Over 3 hours, SCADA shows pressure in that section dropping to 42 psig while delivered flow rises to 1,180 Mcf/day — an **18% increase**. Today's high temperature is 68°F versus yesterday's 65°F — not a cold snap that would explain a genuine demand spike — and no industrial customer ramp-up is scheduled. System MAOP is 60 psig; normal plant outlet pressure runs 55 psig, an 8% margin below MAOP.
**Naive read:** the operator interprets the flow increase as higher customer demand and boosts compressor output to restore section pressure toward its normal 50 psig, without investigating why flow rose in the first place.
**Expert approach:** an 18% flow increase with no corresponding weather or demand explanation, combined with a pressure drop specifically in that section, is consistent with a leak rather than demand — checking historical weather-normalized demand data confirms no explanation for the jump. Rather than boosting compression (which would mask the pressure symptom while a leak continued, or worsen it), a leak survey crew is dispatched to the affected section. The crew finds a corroded pipe section actively leaking, with an estimated leak rate of roughly 175 Mcf/day — accounting for nearly all of the 180 Mcf/day discrepancy (1,180 − 1,000 = 180 Mcf/day), the small remainder consistent with normal metering variance.
**Deliverable (leak investigation / incident log entry):**
> Section 7, Distribution Line B — 2026-07-14. Anomaly detected: pressure drop 50→42 psig over 3 hrs; flow +18% (1,000→1,180 Mcf/day) with no weather (68°F vs. 65°F, no cold-snap driver) or scheduled demand explanation. Treated as probable leak per procedure — leak survey crew dispatched 11:15, NOT a compression adjustment. Crew found corroded pipe section, active leak, Section 7 mile marker 4.2, estimated leak rate ~175 Mcf/day (accounts for ~97% of 180 Mcf/day discrepancy, remainder within normal metering variance). Section isolated 13:40, repair crew dispatched. MAOP (60 psig) not approached at any point during event; plant outlet held at normal 55 psig throughout.
## Going deeper
- [references/playbook.md](references/playbook.md) — a filled leak-investigation decision worksheet, an MAOP pressure-margin table, and an odorant multi-point verification checklist.
- [references/red-flags.md](references/red-flags.md) — signals a leak, a PSM procedure risk, or a gas-quality deviation needs investigation before proceeding, and what to check first.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists misuse (MAOP, odor fade, dew point, and others).
## Sources
49 CFR Part 192 (Pipeline Safety: Transportation of Natural and Other Gas by Pipeline), including §192.625 (odorization requirements); OSHA 29 CFR 1910.119 (Process Safety Management of Highly Hazardous Chemicals); PHMSA pipeline safety regulatory framework; general knowledge of standard natural gas processing and distribution plant operations.