agentleFS
jskhermanjskherman/engg-skills/skills/sour-gas-amine-treating/SKILL.md

sour-gas-amine-treating

Skill7 starsChanged 6 months agoApache-2.0View on GitHub

Screening-level mass-balance helpers for aqueous amine sweetening units (DEA, MDEA, MEA, DGA): rich/lean loading, required amine circulation, and loading envelope warnings. Use when sanity-checking circulation rate, pickup, or rich loading on a sweetening unit. Don't use for rate-based reactive simulation (use ProMax, ProTreat, Aspen Amines), foaming / corrosion prediction, or rigorous absorber tray-by-tray design.

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 circulation; the script returns required amine molar and mass flow, and the solution mass flow at the chosen wt%.

    line 67
  2. Distinctive:

    Verify the result against the existing pump capacity and lean amine exchanger duty.

    line 69
  3. Very specific:

    If acid gas load is unknown, use vle-flash-calculations to estimate H2S/CO2 partial pressures and flow.

    line 94
  4. Very specific:

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

    line 99
  5. Distinctive:

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

    line 101

≈ “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

Sour Gas Amine Treating (Screening)

Overview

Lightweight mass-balance helpers for aqueous amine sweetening:

  • Lean/rich loading in mol acid gas per mol amine from measured flows.
  • Required lean amine mass flow for a target rich loading.
  • Warning if rich loading exceeds widely cited envelopes (corrosion risk).

This skill is for screening, troubleshooting, and operator-discussion support. It does NOT model the absorber rate-based kinetics, the regenerator stripping behaviour, or the corrosion-loading interaction.

Prerequisites

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

When to Use

  • Estimating required amine circulation for a known acid gas load.
  • Checking whether observed rich loading is in the safe envelope.
  • Cross-checking a vendor sizing for a sweetening unit.

Don't use for

  • Rate-based simulation of the absorber or regenerator (use ProMax, ProTreat, Aspen Amines).
  • Predicting foaming, corrosion, or heat-stable salt formation.
  • Selecting the amine itself (DEA vs MDEA vs blends): consult vendor recommendations and operating history.

Utility Scripts

  • uv run scripts/amine.py loading --acid-gas-mol-s 0.5 --amine-mol-s 5 --output /tmp/loading.json
  • uv run scripts/amine.py circulation --acid-gas-mol-s 0.5 --rich 0.40 --lean 0.05 --amine DEA --wt-fraction 0.30 --output /tmp/circ.json

Procedure

  1. From the inlet sour-gas composition and flow, compute the acid-gas molar load (H2S + CO2). Use vle-flash-calculations if needed.
  2. Decide a target rich loading (typical envelopes: DEA 0.35-0.45 mol/mol, MDEA 0.40-0.55 mol/mol). Cross-check against vendor envelope.
  3. Decide a lean loading (regenerator performance dependent; typical 0.01-0.10 mol/mol).
  4. Run circulation; the script returns required amine molar and mass flow, and the solution mass flow at the chosen wt%.
  5. Verify the result against the existing pump capacity and lean amine exchanger duty.

Pitfalls

  • Treating "loading" as wt%; loading is mol acid gas per mol amine. They are very different quantities.
  • Using a single rich loading for H2S+CO2 mixed streams without thinking about the relative absorption rates (DEA absorbs both; MDEA preferentially absorbs H2S over CO2).
  • Forgetting that the rich loading envelope depends on amine concentration: higher wt% generally lower allowable loading due to corrosion.
  • Sizing circulation only for the average case and ignoring upsets (e.g. feed sulfur swings).
  • Assuming the lean amine is at the stripper outlet condition; lean amine cooler and pump can change concentration (e.g. cold lean amine may contain dissolved gases that re-vapourise in the absorber).
  • Using mass balance loading without checking the regenerator's actual performance (it may not strip to the assumed lean loading).
  • Ignoring heat-stable salt accumulation in long-run operation.

Fallback Strategies

  • For rigorous design, surface to the user that a rate-based simulator is required.
  • If acid gas load is unknown, use vle-flash-calculations to estimate H2S/CO2 partial pressures and flow.

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/loading_envelopes.md — published rich loading envelopes and caveats.
  • GPSA Engineering Data Book (Section 21 — Hydrocarbon Treating).
  • Kohl & Nielsen, Gas Purification (5th ed).

Anti-Patterns

  • Reporting "amine circulation 100 GPM" without stating lean and rich loadings.
  • Picking the rich loading from the top of the envelope without an operating margin.
  • Using this skill output to specify a tower without rigorous review.

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.