neqsim: Skill for Claude Code

.github/skills/neqsim-tight-reservoir-test-design/SKILL.md

neqsim-tight-reservoir-test-design is a skill for Claude Code, Codex from equinor/neqsim. It costs 103 tokens per session (1,526 once invoked), scanned A, original, Apache-2.0.

A scientific workflow for deciding how to test a tight underground reservoir through an existing producing site. It combines fluid-property calculations, well and production models, chemistry checks, economics, and staged decision points.

In plain words
What is it for?
Use it to estimate stimulated-well performance and recoverable volume, plan test duration and samples, assess flowback chemistry, compare test outcomes, and evaluate the value of more information.
Why use it?
Tight reservoirs can have uncertain flow rates, recoverable volume, fluid behavior, and compatibility risks. This workflow brings those uncertainties together to judge whether a production test is worth running and how it should be designed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is equinor/neqsim's own configuration. It tells Claude Code and Codex how to work on neqsim itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything neqsim configures →

Reuse

Borrowing it

Nothing to install: this file belongs to equinor/neqsim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/equinor/neqsim/master/.github/skills/neqsim-tight-reservoir-test-design/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/equinor/neqsim

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for neqsim-tight-reservoir-test-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-tight-reservoir-test-design/github.svg)](https://agentmods.dev/skills/equinor/neqsim/neqsim-tight-reservoir-test-design)
Your own site
<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-tight-reservoir-test-design"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-tight-reservoir-test-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for neqsim-tight-reservoir-test-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/equinor/neqsim/neqsim-tight-reservoir-test-design"><img src="https://agentmods.dev/badge/skills/equinor/neqsim/neqsim-tight-reservoir-test-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.01526
Opus 5.5 $0.00041 $0.00610
Sonnet 5.5 $0.00021 $0.00305
Haiku 4.5 $0.00010 $0.00153

Measured 7d ago against content hash 5efaab03eb61, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

neqsim-tight-reservoir-test-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/neqsim-tight-reservoir-test-design/SKILL.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tight-reservoir test design and stage-gate screening

Reference implementation: task_solve/2026-10-09_ofc_rc7_shetland_chalk_further_development/step2_analysis/scripts (chalkmodel.py, econ.py, 04_fluid_compat.py, 05_economics_mc.py). Copy the pattern, not the numbers.

1. Order of work

  1. Public evidence first (Sodir resource reports, field news, EAGE/SPE abstracts), saved to references/literature. Sodir FactMaps wellbore layers (204, 205) answer "which wells found hydrocarbons in formation X"; page with resultOffset and filter client side (the WAF rejects LIKE '%..%' filters).
  2. Fluid from NeqSim: reservoir T, p, Psat (bubblePointPressureFlash), compressibility from density at p and p+10 bar, viscosity, Bo and GOR from a 3-stage flash, TVP of the stock-tank oil. These feed the well model.
  3. Well model: 1-D slab from the fracture face to the drainage boundary (area = zones x 2 faces x 2 xf x h x effectiveness, length L). Use finite differences with scipy.linalg.solve_banded, geometric time steps (dt/t about 5 %), pressure-dependent mobility and piecewise compressibility (single phase above Psat, gas expansion below). Validate against the closed-form series q = A (k/mu) dP (2/L) sum exp(-(2n+1)^2 pi^2 eta t / 4L^2) and the identity RF = c_t dP / S_o.
  4. Arps: fit the first-year window with free b, then extrapolate. A boundary-dominated well fitted in its transient window gives b about 1.4-1.7 and overstates EUR 2-2.4x (b = 1.0: 1.4-1.8x). Never book EUR from a test decline without a boundary or volume check.
  5. Test duration from the radius of investigation r = sqrt(4 eta t), eta = k / (mu phi c_t); single phase above Psat, 4x smaller eta below. A 6-month flow plus two build-ups sees 200-340 m for k = 0.1-0.3 mD; k = 0.05 mD needs well over a year.
  6. Flowback chemistry: acid (15 % HCl) reacts with CaCO3: 1 t HCl gives 1.37 t CaCO3 dissolved, 0.6 t CO2 and a spent brine of about 20 wt % CaCl2 (about 88 g/L Ca). Use AcidTreatmentSimulator for the cross-check and BrineMixingScaleEvaluator for mixing curves (formation water + seawater, + produced water, spent acid + produced water). BaSO4 is the first scale to watch when sulphate meets a barium-bearing water.
  7. Hydrate: SRK-CPA with the associated gas, lumped C7+ and free water; Wax: the Pedersen model needs an n-paraffin distribution, P/A pseudo-components do not converge, so report wax as a lab-data gap.
  8. Souring: bound H2S in gas by the fraction of injected sulphate reduced; SRB activity stops above about 80-90 C, so souring is a cooled-zone risk around injectors.
  9. Value: annual cash flow with the 2022 NCS tax (78 % marginal, direct expensing), Monte Carlo with common random numbers, tornado, break-even EUR per well (scale the well curve until NPV = 0), break-even oil price.
  10. Value of the test: bin the test-estimated EUR (lognormal error), take the best concept per bin, compare "test then decide" against "commit blind" and "do nothing"; sweep the measurement error. Make the test measure the candidate completion, not the old one.

Read the full file on GitHub · 38 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 38 lines · 103 tokens per session scan A 5efaab03eb61

Subscribe to this mod's changes

neqsim-tight-reservoir-test-design is a skill published in the GitHub repository equinor/neqsim (156 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 1,526 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-11.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens