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

neqsim-hydrate-screening

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Educational hydrate risk screening placeholder with public assumptions. USE WHEN: a task needs a quick hydrate risk triage 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 hydrate-risk screening example.

    line 16
  2. Distinctive:

    When a user asks for a first-pass hydrate risk triage example.

    line 20
  3. Distinctive:

    When only pressure, temperature, and water presence are available.

    line 21
  4. Distinctive:

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

    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 56
  6. Distinctive:

    No hydrate phase equilibrium calculation is performed.

    line 76
  7. Distinctive:

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

    line 77
  8. Distinctive:

    No proprietary hydrate curves or company operating envelopes are included.

    line 78
  9. Distinctive:

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

    line 79

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

Use this skill for a quick, public hydrate-risk screening example. It is intentionally simple and should guide users toward validated NeqSim hydrate calculations for real work.

When to Use

  • When a user asks for a first-pass hydrate risk triage example.
  • When only pressure, temperature, and water presence are available.
  • When an agent should explain that validated NeqSim methods are required for real hydrate prediction.

Inputs

  • pressure: operating pressure in bar.
  • temperature: operating temperature in C.
  • water_present: boolean indicating whether free or condensed water may be present.

Outputs

  • risk_level: low, medium, or high.
  • margin_indicator: temperature margin in C above the placeholder hydrate boundary.
  • estimated_boundary: placeholder hydrate boundary temperature in C.
  • assumptions: public assumptions and required follow-up.

Engineering Method

The placeholder method estimates a simple pressure-dependent boundary and compares operating temperature to that boundary. If water is absent, risk is reported as low with an assumption note. If water is present, low margin gives higher risk.

This is not a thermodynamic hydrate model. Real hydrate calculations should use validated NeqSim methods with a defined fluid composition, water content, inhibitor basis, and operating envelope.

Python Usage Pattern

from hydrate_screening import HydrateScreener

screener = HydrateScreener()
result = screener.screen(pressure=80.0, temperature=4.0, water_present=True)

print(result.risk_level)
print(result.margin_indicator)
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

  • Pressure is positive and temperature is finite.
  • Water-present and water-absent cases are tested.
  • The placeholder boundary is documented as educational only.
  • Results are not used as inhibitor dosage, design margin, or operating limit.
  • Real hydrate work is redirected to validated NeqSim methods.

Common Mistakes

SymptomCauseFix
Low risk reported despite cold temperaturewater_present=False was assumedConfirm water phase, water dew point, and operating history
Treating margin as a design safety marginPlaceholder boundary is not thermodynamicUse validated NeqSim hydrate calculations
Missing composition effectsOnly pressure, temperature, and water flag were providedProvide full composition and inhibitor basis to NeqSim

Limitations

  • No hydrate phase equilibrium calculation is performed.
  • 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.

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.