agentleFS
equinorequinor/neqsim-community-skills/skills/flow-assurance/neqsim-hydrate-margin-check/SKILL.md

neqsim-hydrate-margin-check

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Educational hydrate operating-margin screening placeholder with public assumptions. USE WHEN: a task needs a quick check of whether an operating point keeps a safe temperature margin above a hydrate equilibrium temperature and should be directed to validated NeqSim methods for real calculations.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for a quick, public check of whether a process or pipeline operating point keeps a temperature margin above a known hydrate …

    line 16
  2. Distinctive:

    When a user asks whether an operating temperature stays clear of the hydrate region.

    line 20
  3. Distinctive:

    When a validated NeqSim hydrate equilibrium temperature is already available.

    line 21
  4. Distinctive:

    When an agent should explain that validated NeqSim methods are required for real hydrate prediction and inhibitor design.

    line 22
  5. Very specific:

    If the optional neqsim Python package is available, the result records that fact so an agent can recommend moving to validated NeqSim …

    line 60
  6. Distinctive:

    No hydrate phase equilibrium calculation is performed in this skill.

    line 81
  7. Distinctive:

    No salinity, methanol, MEG, kinetics, composition, or transient effects are included.

    line 82
  8. Distinctive:

    No proprietary hydrate curves or company operating envelopes are included.

    line 83
  9. Distinctive:

    Not suitable for flow assurance design, inhibitor dosage, or operating-limit decisions.

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Hydrate Margin Check

Use this skill for a quick, public check of whether a process or pipeline operating point keeps a temperature margin above a known hydrate equilibrium temperature. It is intentionally simple and should guide users toward validated NeqSim hydrate calculations for real work.

When to Use

  • When a user asks whether an operating temperature stays clear of the hydrate region.
  • When a validated NeqSim hydrate equilibrium temperature is already available.
  • When an agent should explain that validated NeqSim methods are required for real hydrate prediction and inhibitor design.

Inputs

  • operating_temperature: operating temperature in C.
  • hydrate_equilibrium_temperature: hydrate equilibrium (formation) temperature in C from a validated NeqSim calculation.
  • min_margin: configurable minimum acceptable margin in C (constructor, default 3.0).

Outputs

  • hydrate_margin_c: operating temperature minus the hydrate equilibrium temperature in C.
  • subcooling_c: subcooling into the hydrate region in C, zero when the operating point is outside the region.
  • margin_warning: ok, watch, or high.
  • neqsim_available: whether the optional NeqSim package is importable.
  • assumptions: public assumptions and required follow-up.

Engineering Method

The placeholder method computes the hydrate margin as operating_temperature - hydrate_equilibrium_temperature. A non-positive margin means the operating point is inside the hydrate region and is flagged high. A small positive margin below min_margin is flagged watch. A larger margin is flagged ok.

This is not a thermodynamic hydrate model. The hydrate equilibrium temperature must come from a validated NeqSim hydrate calculation with a defined fluid composition, water content, inhibitor basis, and operating envelope.

Python Usage Pattern

from hydrate_margin_check import HydrateMarginModel

model = HydrateMarginModel(min_margin=3.0)
result = model.evaluate(
    operating_temperature=10.0,
    hydrate_equilibrium_temperature=8.0,
)

print(result.hydrate_margin_c)
print(result.margin_warning)
print(result.assumptions)

If the optional neqsim Python package is available, the result records that fact so an agent can recommend moving to validated NeqSim hydrate workflows. If not, the example still runs with fallback placeholder logic.

Validation Checklist

  • Operating and hydrate equilibrium temperatures are finite.
  • The hydrate equilibrium temperature came from a validated NeqSim calculation.
  • In-region and out-of-region cases are tested.
  • The minimum margin is documented as a configurable public guideline only.
  • Results are not used as inhibitor dosage, design margin, or operating limit.
  • Real hydrate work is redirected to validated NeqSim methods and qualified review.

Common Mistakes

SymptomCauseFix
Margin looks safe but hydrates still formHydrate equilibrium temperature was guessedUse a validated NeqSim hydrate equilibrium temperature
Margin warning never triggersmin_margin set too lowUse a service-appropriate operating margin and confirm with flow assurance review
Missing inhibitor effectInhibitor was not included in the NeqSim basisProvide the inhibitor basis to NeqSim and recompute the hydrate temperature

Limitations

  • No hydrate phase equilibrium calculation is performed in this skill.
  • No salinity, methanol, MEG, kinetics, composition, or transient effects are included.
  • No proprietary hydrate curves or company operating envelopes are included.
  • Not suitable for flow assurance design, inhibitor dosage, or operating-limit decisions.

Related NeqSim Functionality

This educational screening corresponds to validated, rigorous functionality in the NeqSim Java library that a qualified engineer should use for design-grade work:

  • neqsim.thermo.system.SystemSrkCPAstatoil — CPA equation of state for water-bearing natural gas.
  • neqsim.thermodynamicoperations.ThermodynamicOperations#hydrateFormationTemperature() — rigorous hydrate equilibrium temperature and margin to operating conditions.

In Python the same classes are reachable through the neqsim package (for example from neqsim import jneqsim).

References

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.