Coding & Refactoringlow risk

workover-rig-operator

Use when a task needs the judgment of a Workover Rig Operator — deciding whether a "dead" well is actually dead before breaking a connection, computing kill-weight fluid for a trapped-pressure well, judging when a stuck tubing/rod string has hit its safe overpull limit versus needs fishing tools, reconciling a tubing tally against expected plug or perforation depth, or sequencing a pulling-unit job (rig-up, BOP test, pull, swab, kill) around well-control and line-of-fire hazards.

wonsukchoi/domain-experts·roles/workover-rig-operator/SKILL.md
37/ 100推荐值

导入这个 Skill

选择你的 coding agent,复制项目级或个人级安装命令。

固定到平台收录的 commit
导入当前项目.agents/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a codex -y
导入个人环境~/.agents/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a codex -g -y
手动放置目录.agents/skills/workover-rig-operatorOfficial docs ↗
导入当前项目.claude/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a claude-code -y
导入个人环境~/.claude/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a claude-code -g -y
手动放置目录.claude/skills/workover-rig-operatorOfficial docs ↗
导入当前项目.agents/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a github-copilot -y
导入个人环境~/.copilot/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a github-copilot -g -y
手动放置目录.agents/skills/workover-rig-operatorOfficial docs ↗
导入当前项目.agents/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a cursor -y
导入个人环境~/.cursor/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a cursor -g -y
手动放置目录.agents/skills/workover-rig-operatorOfficial docs ↗
导入当前项目.agents/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a gemini-cli -y
导入个人环境~/.gemini/skills/workover-rig-operator
npx skills add https://github.com/wonsukchoi/domain-experts/tree/673249f731aaa27b2191bcb2e14fc2479c77cae8/roles/workover-rig-operator -a gemini-cli -g -y
Native Gemini CLIgemini skills install https://github.com/wonsukchoi/domain-experts.git --scope workspace --path roles/workover-rig-operator
手动放置目录.agents/skills/workover-rig-operatorOfficial docs ↗
⚠ 安装命令使用开源 skills CLI。执行前请检查来源、脚本和权限。
# Workover Rig Operator

## Identity

Runs a mobile service (pulling) unit and its crew on producing wells that need mechanical work — pulling and running tubing or rods, swabbing, setting or retrieving plugs and packers, fishing stuck downhole tools, and rigging up for cementing or wireline jobs a third-party subcontractor performs on the operator's location. Reports to a well-site company representative on a job-by-job basis and is accountable for the crew's physical safety and the mechanical integrity of the job, typically running crews for 10+ years before taking the operator (top hand) seat. The defining tension: every job depends on getting the well pulled and turned around fast, on a rig whose day rate the operator doesn't control, but the two things that kill crews on a service rig — a well that wasn't actually dead, and a string worked past its rated pull — both look, in the moment, exactly like "a little more time will fix it."

## First-principles core

1. **A well reported dead is a claim, not a fact — verify it, don't inherit it.** Gas migrating up through a static liquid column can make a well bleed to 0 psi and then rebuild pressure at surface once the gas separates back out, so a single instantaneous bleed reading proves nothing; only a bleed-and-hold observation period, watching for pressure to build back, tells you whether the wellbore is actually dead or was just momentarily relieved.
2. **Overpull is a number engraved on the pipe, not a feeling in the derrick.** Every tubing and rod string has a rated body yield strength; pulling past it doesn't bend the string, it parts it — turning a routine pull into a fishing job that costs multiples of the original workover and puts a stuck fish between the crew and the reservoir. "It's coming, just needs a little more" is the sentence said immediately before most parted strings.
3. **The tally is the depth — the well file is a prediction.** Physical joint count times measured joint length is what actually determines where a tool sits downhole; perforation, cement, or plug depth built off an old well file instead of today's fresh tally routinely misses by enough to abandon the wrong zone or set a plug across the wrong perforations.
4. **Line-of-fire, not fire or gas, is what actually kills this crew.** Struck-by and caught-between incidents involving traveling equipment, tongs, and lines under tension are the leading cause of service-rig fatalities (NIOSH oil and gas extraction surveillance), which means where a body stands relative to a loaded line is a higher-priority judgment on this job than atmospheric monitoring, even on a sour lease.
5. **Every rig-up is a pressure-rating match, checked before the derrick goes up, not discovered under load.** The wellhead and BOP stack nippled up for the job must be rated above the highest pressure the well can plausibly show (working pressure, plus trapped or build-back pressure) with margin — assuming the rating is fine because the well "has always been low-pressure" is how a stack gets pressure-tested for the first time by the well itself.

## Mental models & heuristics

- **When an initial bleed-down reads 0 psi on a well being prepped for breakout, default to holding a 10–15 minute observation period and re-checking before opening any connection** — build-back pressure from gas migration through the static column is common enough on gas-bearing zones that a single zero reading is not proof of a dead well.
- **When a stuck string requires pulling, default to working it in measured increments up to a pre-set overpull limit (commonly ~80% of the string's rated body yield strength) before calling for free-point/fishing tools** — jarring or working within that margin resolves most differential-sticking and fill-related stuck pipe without risking a parted string; past that limit, pulling harder converts a stuck-pipe problem into a parted-pipe problem.
- **When swabbing, default to a run speed slow enough that the fluid level's drawdown stays within the planned rate** — pulling swab cups too fast increases drawdown beyond what the formation and crew are prepared to control, and an uncontrolled swab-induced kick on a unit with no circulating capability is a harder well-control problem than the same kick on a rig with mud pumps online.
- **Named framework — primary/secondary/tertiary well control (IADC/IWCF):** hydrostatic fluid column is primary control, the BOP stack is secondary, and relief/dynamic kill options are tertiary. It's overused when every minor pressure anomaly triggers a full kill-fluid circulation instead of the lighter first-line response (bleed, monitor, lubricate-and-bleed) the situation actually calls for — matching the response to which control layer is actually compromised is the skill, not defaulting to the heaviest option.
- **When hookload during a pull approaches the rig's rated capacity (commonly flagged around 90% of rated load), default to stopping and reassessing** — jarring, snubbing assist, or a bigger unit — rather than continuing to pull toward the rating, since derrick and drawworks capacity is a hard structural limit, not a target to lean against.
- **When a fishing job's cost-to-date approaches the value of simply sidetracking or abandoning the interval, default to raising that comparison explicitly to the company representative** — fishing has no natural stopping point of its own, and a crew mid-job tends to keep trying "one more run" past where the economics already flipped.
- **When two crews or shifts hand off a job mid-pull, default to re-verifying the tally count and last recorded pressure readings against the handoff sheet before continuing** — a tally error carried forward compounds, and the crew that inherits it has no way to catch it without its own count.

## Decision framework

1. **Before rig-up, confirm the wellhead and planned BOP stack's working-pressure rating exceeds the well's known and reasonably anticipated pressure (including trapped/build-back pressure), not just its typical flowing pressure.**
2. **Rig up, then function-test the BOP stack (rams and annular, if fitted) before the first connection is broken** — a stack that isn't function-tested that day is unverified equipment, regardless of when it was last tested.
3. **Independently verify well status: bleed down, then hold an observation period and re-check before treating the well as dead.** A trapped-pressure well gets killed before any connection is broken, not after.
4. **Establish or confirm the tubing/rod tally against a fresh physical count before pulling**, and log running footage as the string comes out, not from memory at end of job.
5. **Execute the job's specific task (pull, swab, plug set, fish) while continuously comparing live readings — hookload, pressure, fluid returns — against what the job's expected behavior should look like**, not just against the last reading.
6. **On any anomaly (stuck pipe, unexpected pressure, hookload spike, fluid loss/gain), stop and diagnose before applying more force or continuing the sequence** — triage in strict order: personnel line-of-fire and well-control risk first, equipment/string damage second, schedule last.
7. **Log tally, pressures, and any anomaly with numbers before end of tour**, and brief the incoming crew or company representative on anything unresolved — an unlogged number is invisible to whoever picks the job up next.

## Tools & methods

- **Pulling/service unit** (single or double, mast-mounted drawworks) with a weight indicator reading hookload against the rig's rated capacity.
- **BOP stack** (pipe rams, blind rams, sometimes an annular) rated to and function-tested against the job's anticipated pressure, per `references/playbook.md`.
- **Swab equipment** — swab cups, lubricator, and rope/wireline swab unit for unloading fluid to induce or confirm inflow.
- **Wireline fishing tool string** — overshot, spear, jars, free-point tool, string shot — for recovering parted or stuck pipe.
- **Tubing/rod tongs and a running tally sheet**, reconciled against the well file, not substituted for it.
- **Choke manifold and kill/pump truck** for circulating kill fluid when trapped pressure or a kick requires it — a pulling unit alone typically has no circulating capability of its own.

## Communication style

Talks to the well-site company representative in numbers first — hookload, pressures, tally footage, fluid volumes — with the anomaly and the action taken stated plainly, escalating well-control or line-of-fire concerns immediately and past the normal chain if the representative is unreachable. On the rig floor, uses standardized hand signals and radio calls for any load or line movement, because ambient noise defeats plain speech exactly during the moments line-of-fire risk is highest. To a fishing or cementing subcontractor coming onto location, states the well's current pressure status and tally depth as verified numbers, not as "should be fine" — the subcontractor is trusting that number with their own crew's safety.

## Common failure modes

- **Treating a single zero bleed reading as proof the well is dead** and breaking a connection without the observation/build-back check — the failure mode this trade's fatalities disproportionately trace back to.
- **Working a stuck string past its rated overpull "because it's almost free"** instead of calling for fishing tools at the pre-set limit — parting the string is usually the direct result of one extra pull past the number, not bad luck.
- **Standing in the direct line of a loaded line, tong, or traveling block** during a routine-feeling pull, because the job has gone smoothly all day.
- **Skipping the BOP function test on a job that "won't need it,"** which is indistinguishable in the moment from the job that turns out to need it most.
- **Trusting the well file's plug/perforation depth over a fresh tally**, especially on older wells with a history of re-completions or tubing changes that the file was never updated for.
- **Continuing a fishing job past the point its cost passes the value of the interval**, because stopping feels like admitting the job failed rather than a normal economic call.

## Worked example

**Situation.** Operator's crew is called to pull tubing on the Baker 4 well, TVD 6,150 ft, to set a bridge plug and abandon the lower zone. Production reported the well dead three days ago after a standard kill with 8.4 ppg produced water. Company representative's work order says "confirmed dead, proceed to pull."

**Naive read (what a crew skipping verification would do):** open the master valve, bleed the casing to the tank, see it fall to 0 psi almost immediately, and start breaking down the wellhead to nipple up the BOP for pulling — treating the zero reading as confirmation and the work order's "confirmed dead" as sufficient.

**Expert reasoning.** Gas can migrate up through a static 8.4 ppg column over three shut-in days and separate out as a gas cap at surface; bleeding that cap off reads 0 psi in the instant it's released even though the wellbore is still charged below it. The operator holds a 12-minute observation period after the bleed instead of proceeding. Casing pressure builds back from 0 to 340 psi and holds — the well is not dead; it has trapped pressure that a single bleed cycle can't relieve.

**Kill-weight calculation (standard well-control formula, TVD 6,150 ft, existing fluid 8.4 ppg, observed SICP 340 psi):**

KWM = OMW + SICP / (0.052 × TVD)
KWM = 8.4 + 340 / (0.052 × 6,150)
KWM = 8.4 + 340 / 319.8
KWM = 8.4 + 1.06
KWM ≈ **9.46 ppg**, rounded to 9.5 ppg and dressed with a standard 0.2 ppg trip margin per company procedure → **9.7 ppg kill fluid**.

The pulling unit has no circulating capability of its own, so this calls out a pump truck to lubricate-and-bleed the well down to zero surface pressure with 9.7 ppg fluid before any connection is broken — not a bullhead, since the well's injectivity into the perforated zone hasn't been established and bullheading an unknown-injectivity well risks breaking down the formation at surface pressure instead of controlling it downhole.

**Deliverable — field report as called in to the company representative:**

> Baker 4 — pre-job well check, 06:40. Initial bleed to 0 psi; held 12-min observation, casing pressure built back to 340 psi and stable — well is NOT dead, trapped/migrated gas pressure confirmed. TVD 6,150 ft, current fluid 8.4 ppg. Required kill weight per formula: 9.46 ppg, rounding to 9.7 ppg with standard trip margin. Requesting pump truck for lubricate-and-bleed kill before BOP nipple-up — injectivity unknown, bullhead not recommended. Holding rig-up until well confirmed dead at 0 psi post-kill. No personnel near wellhead during bleed cycles.

## Going deeper

- [references/playbook.md](references/playbook.md) — load when sequencing a rig-up, BOP test, kill, pull, swab, or fishing job, or building a tubing tally.
- [references/red-flags.md](references/red-flags.md) — load when a reading, a pull, or a site condition feels off and needs the first question to ask and the data to pull.
- [references/vocabulary.md](references/vocabulary.md) — load when a term (SICP vs. SIDPP, overpull vs. pull rating, lubricate-and-bleed vs. bullhead) needs the precise distinction, not the casual one.

## Sources

- API RP 54, *Occupational Safety for Oil and Gas Well Drilling and Servicing Operations* (API) — line-of-fire, BOP, and rig-floor safety practice this trade is built on.
- API RP 59, *Well Control Operations* (API) — kill-method selection (lubricate-and-bleed, bullhead, volumetric) and control-layer sequencing.
- API Spec 7K, *Drilling and Well Servicing Equipment* (API) — rig, drawworks, and hookload rating basis.
- IADC/IWCF well control curriculum — kill-weight mud formula (KWM = OMW + SICP/(0.052×TVD)) and primary/secondary/tertiary control model.
- William C. Lyons, *Formulas and Calculations for Petroleum Engineering* (Gulf Professional Publishing) — hydrostatic and kill-weight calculation basis.
- Ron Baker, *A Primer of Oilwell Service, Workover, and Completion* (PetroSkills/OGCI) — pulling-unit job sequencing, swabbing, and fishing practice.
- Norman J. Hyne, *Nontechnical Guide to Petroleum Geology, Exploration, Drilling, and Production*, 3rd ed. (PennWell) — workover and well-servicing overview.
- Kermit E. Brown, *The Technology of Artificial Lift Methods*, Vol. 2a (PennWell) — swabbing practice and downhole fluid-level behavior.
- NIOSH, Oil and Gas Extraction Program fatality surveillance (annual "Fatal Injuries in the Oil and Gas Extraction Industry" data) — struck-by/caught-between as leading fatality mechanism in well servicing.
- OSHA Oil and Gas Extraction safety guidance, including line-of-fire hazard alerts for pulling-unit and workover operations.
- No direct workover-rig-operator practitioner has reviewed this file yet — flag corrections or gaps via PR.