agentleFS
jskhermanjskherman/engg-skills/skills/separator-vessel-sizing/SKILL.md

separator-vessel-sizing

Skill7 starsChanged 6 months agoApache-2.0View on GitHub

Size two-phase (gas-liquid) separator vessels (vertical or horizontal) using the Souders-Brown vapor-velocity criterion, K-factor heuristics, and liquid holdup time. Use when sizing flash drums, knock-out drums, suction scrubbers, or compressor inlet drums for screening. Don't use for three-phase separators with explicit water-hydrocarbon holdup (requires separate residence times), cyclonic separators, or high-pressure liquid-liquid coalescers.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run vertical or horizontal.

    line 65
  2. Very specific:

    If quality x is known, use watkins-k to derive a more realistic K from fluids.separator.K_separator_Watkins instead of the rule-of-thumb …

    line 86
  3. Distinctive:

    If the holdup time check fails, increase L/D for horizontal or vessel diameter for vertical and rerun.

    line 89
  4. Very specific:

    Run the listed script with representative inputs and an --output file when a deterministic calculation is available.

    line 94
  5. Distinctive:

    Check result magnitudes against the stated assumptions, references, and a hand calculation or known operating range before reporting them.

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Two-Phase Separator Vessel Sizing

Overview

Implements the Souders-Brown velocity criterion with GPSA-style K-factor ranges (no proprietary table reproduced) for vertical and horizontal two-phase vessels. Liquid holdup time defaults to 5 minutes (typical operator-response horizon); override for your service.

Prerequisites

  1. uv available.
  2. On first use, the script writes LICENSE_NOTIFICATION.txt.

When to Use

  • Sizing a knock-out drum, flash drum, suction scrubber, or compressor inlet drum.
  • Screening vendor sizing or rating an existing vessel for new conditions.

Don't use for

  • Three-phase separators with explicit oil-water-gas residence time.
  • Cyclonic / vane / coalescer-only separators.
  • Tower-bottom sumps where downcomer hydraulics dominate.

Utility Scripts

  • uv run scripts/sizing.py vertical --vapor-volumetric 0.4 --liquid-volumetric 0.005 --rho-l 600 --rho-g 30 --demister --output /tmp/v.json
  • uv run scripts/sizing.py horizontal --vapor-volumetric 0.4 --liquid-volumetric 0.005 --rho-l 600 --rho-g 30 --demister --LD 4 --output /tmp/h.json
  • uv run scripts/sizing.py watkins-k --quality 0.6 --rho-l 600 --rho-g 30 --output /tmp/k.json

Procedure

  1. Get the vapor volumetric flow at operating P,T (from a flash, or from measured density and mass flow).
  2. Get the liquid volumetric flow.
  3. Decide demister or no demister (demister = ~50% smaller diameter for the same separation).
  4. Pick liquid holdup time: 5 min for operator response, 2 min for high reliability shutdown systems, 10 min for upstream / unattended skids.
  5. Pick L/D for horizontal: 3 (compact), 4 (default), 5 (long, high gas load).
  6. Run vertical or horizontal; check that the available liquid holdup meets requirement.

Pitfalls

  • Picking the K-factor at the top of the range without justifying it.
  • Sizing for max vapor flow but ignoring the relief contingency flow (which may govern the design).
  • Forgetting to add a demister allowance to tan-tan height (~0.3 m typical).
  • Using a vertical vessel for a high-liquid-loading service; horizontal is often better when liquid-to-vapor flow ratio is large.
  • Treating the diameter as exact; round up to standard pipe / fab sizes.
  • Reporting K without specifying horizontal vs vertical and with/without demister.
  • Forgetting that high-pressure systems need different K factors than atmospheric service (the GPSA chart trends with P).
  • Sizing on lab/measured density and forgetting that density at operating conditions can differ by 5-15%.

Fallback Strategies

  • If quality x is known, use watkins-k to derive a more realistic K from fluids.separator.K_separator_Watkins instead of the rule-of-thumb ranges.
  • If the holdup time check fails, increase L/D for horizontal or vessel diameter for vertical and rerun.

Verification

  • Run the listed script with representative inputs and an --output file when a deterministic calculation is available.
  • Confirm the JSON result contains ok: true, expected units, and no unhandled warnings.
  • Check result magnitudes against the stated assumptions, references, and a hand calculation or known operating range before reporting them.

References

  • references/k_factor_ranges.md — K-factor ranges and citations.
  • GPSA Engineering Data Book (procure separately).
  • API 12J — Specification for Oil and Gas Separators.

Anti-Patterns

  • Treating the vessel as final design without HAZOP, relief, or vendor review.
  • Specifying tan-tan height without showing the holdup calculation.
  • Picking K to fit a pre-existing nozzle size rather than to meet the separation duty.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.