agentleFS
equinorequinor/neqsim-community-skills/skills/field-development/neqsim-reservoir-depletion-screening/SKILL.md

neqsim-reservoir-depletion-screening

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Educational reservoir tank-depletion vs time screening with gas/oil and water-cut evolution. USE WHEN: a task needs a public, screening-level pressure-decline and production profile over time from a recoverable volume and offtake rate before detailed NeqSim SimpleReservoir or reservoir-engineering modelling.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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 screening of how a reservoir develops with time.

    line 16
  2. Distinctive:

    When a user wants a first look at how reservoir pressure declines over field life.

    line 26
  3. Distinctive:

    When an early production/decline profile is needed before a reservoir model exists.

    line 27
  4. Distinctive:

    When an agent needs an upstream "reservoir vs time" feed for a production-routing or arrival-pressure screening chain.

    line 28
  5. Distinctive:

    No confidential data or proprietary methods are included.

    line 125

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

Reservoir Depletion Screening

Use this skill for a quick, public screening of how a reservoir develops with time. Given a recoverable volume, an offtake rate, and an initial and abandonment pressure, it produces a year-by-year profile of reservoir pressure, cumulative production, recovery factor, water cut, and hydrocarbon/water rates. It is intentionally simple and should guide users toward the validated NeqSim SimpleReservoir tank model (runTransient) and the NeqSim MCP runReservoir workflow for real depletion behaviour.

When to Use

  • When a user wants a first look at how reservoir pressure declines over field life.
  • When an early production/decline profile is needed before a reservoir model exists.
  • When an agent needs an upstream "reservoir vs time" feed for a production-routing or arrival-pressure screening chain.

Inputs

  • fluid_type: gas or oil.
  • initial_pressure_bara: reservoir pressure at start of production.
  • abandonment_pressure_bara: pressure at which production stops (screening).
  • recoverable_volume_sm3: recoverable hydrocarbon volume at standard conditions.
  • offtake_rate_sm3_per_day: constant screening offtake (hydrocarbon) rate.
  • years: number of years to simulate.
  • time_step_years: time-step size (default 1.0 year).
  • initial_water_cut_fraction: water cut at start (default 0).
  • water_cut_rise_per_year: linear water-cut rise per year (default 0).

Outputs

  • steps: per-step year, pressure_bara, cumulative_production_sm3, recovery_factor, water_cut_fraction, hydrocarbon_rate_sm3_per_day, water_rate_sm3_per_day, and depleted flag.
  • final_pressure_bara, final_recovery_factor.
  • plateau_years: years before production can no longer be sustained (or None).
  • years_to_abandonment: first year the reservoir reaches abandonment (or None).
  • depletion_warning: ok, watch, or high.
  • neqsim_available: whether the optional NeqSim package is importable.
  • assumptions: public assumptions and required follow-up.

Engineering Method

Reservoir pressure declines linearly with recovery factor between the initial and abandonment pressure: P = Pi - (Pi - Pabn) * (Gp / Vrec). Cumulative production Gp accrues at the constant offtake rate each step until the recoverable volume is reached or the abandonment pressure is hit. Water cut follows a supplied linear trend, and the water rate is derived from the hydrocarbon rate and the water-cut fraction. The verdict is high once the reservoir is depleted, watch past a configurable recovery-factor threshold, otherwise ok.

This skill performs no PVT, aquifer, injection, or coning physics. It is a transparent placeholder that must be replaced by a validated NeqSim reservoir tank model for any quantitative use.

Python Usage Pattern

from reservoir_depletion_screening import ReservoirDepletionModel

model = ReservoirDepletionModel()
result = model.evaluate(
    fluid_type="gas",
    initial_pressure_bara=300.0,
    abandonment_pressure_bara=80.0,
    recoverable_volume_sm3=20.0e9,
    offtake_rate_sm3_per_day=8.0e6,
    years=15,
    initial_water_cut_fraction=0.05,
    water_cut_rise_per_year=0.03,
)

for step in result.steps:
    print(step.year, step.pressure_bara, step.recovery_factor, step.water_cut_fraction)
print(result.depletion_warning)

Validated NeqSim Path

This screening is a placeholder. For real reservoir-vs-time behaviour use:

  • NeqSim SimpleReservoir with addGasProducer / addOilProducer / addWaterInjector / addGasInjector and a runTransient(deltat) time loop.
  • NeqSim MCP runReservoir for an orchestrated reservoir tank simulation.
  • The enterprise well-production-routing-agent for live-data, IPR + tubing, and Beggs & Brills arrival modelling.

Escalation

Escalate any watch or high verdict, and any quantitative use, to a validated NeqSim reservoir model and qualified reservoir-engineering review.

Validation Checklist

  • Inputs are validated and within stated ranges.
  • Examples use public data only.
  • Screening assumptions are stated explicitly.
  • Limitations are respected.
  • Quantitative use is escalated to validated NeqSim models.

Common Mistakes

SymptomCauseFix
Unrealistic resultInputs outside the screening rangeKeep inputs within the stated bounds
Misused for designScreening output taken as finalEscalate to validated NeqSim models

Limitations

  • Educational screening only; not a validated design method.
  • No confidential data or proprietary methods are included.
  • Escalate any quantitative or design use to validated NeqSim workflows.

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.