Performs root cause analysis on process equipment — compressor trips and vibration, pump and compressor efficiency loss, separator carryover, heat-exchanger fouling and U-value degradation, cooling-water and cooling-medium performance loss, valve and capacity limitations — using NeqSim's diagnostics framework, which…
Routes engineering requests to the most appropriate NeqSim specialist agent. Analyzes the user's question, classifies it by domain, and delegates to the right agent — or composes multi-agent pipelines for complex cross-discipline tasks. Use this when you're unsure which agent to pick.
Performs process safety simulations — vessel depressurization/blowdown, relief valve sizing (API 520/521), trapped-liquid fire rupture screening, fire case modeling, source term generation for consequence analysis (PHAST/FLACS/KFX), safety envelope calculations (hydrate, MDMT, CO2 freezing), and risk analysis with…
Takes a process simulation task description and delivers a complete, tested Jupyter notebook. Uses neqsimdevsetup for local development and produces Colab-compatible output. This is the fast path for getting working process simulation notebooks.
Solves process-engineering problems using the NeqSim Java API with proportional depth: quick answer-first calculations, notebook-backed studies, or full reports. Delivers auditable task folders with validation evidence, runner-executed notebooks/scripts, and reports when needed. When NeqSim lacks a needed capability…
Reads and extracts structured engineering data from technical documents and engineering images — equipment data sheets, design basis, heat & mass balance tables, technical requirements, well test reports, inspection reports, piping specifications, material certificates, standards documents, P&ID drawings, mechanical…
Coordinates screening-level utility-system DESIGN with NeqSim — sizes fired steam boilers, deaerators, vapour-compression refrigeration, on-site nitrogen generation, and multi-pressure steam networks, aggregates plant utility demands from a run flowsheet, and runs the agentic closed loop that optimizes a two-stage…
Agent-to-agent communication schema for NeqSim. USE WHEN: composing multi-agent pipelines where one agent's output feeds another agent's input. Defines structured result formats for fluid definitions, simulation results, and design outputs that agents can pass to each other.
Agentic closed-loop optimization of large multi-area NeqSim ProcessModel plants with convergence gating and equipment introspection. USE WHEN: an agent must optimize a live full-plant flowsheet (setpoints, compressor pressures, heater temperatures, routing fractions) across years/scenarios with surge/RVP/spec…
NeqSim API patterns and code recipes. USE WHEN: writing Java or Python code that uses NeqSim for thermodynamic calculations, process simulation, or property retrieval. Covers EOS selection, fluid creation, flash calculations, property access, equipment patterns, and unit conventions.
★not rated 156
changed 3d agoASkillSpector: pass60 tokens
originalApache-2.0
Autonomous observe-hypothesize-predict-test-discriminate loop for operational anomalies. USE WHEN: solving a PEPR action, root-cause or operational study where the symptom, driver or important relationships are NOT given up front. Uses neqsim.process.diagnostics.RelationshipGraph for lead-lag relationship discovery…
Structured inventory of NeqSim's capabilities by engineering discipline. USE WHEN: checking what NeqSim can do, planning implementations, assessing gaps for engineering tasks, or routing work to the right agent. Covers thermodynamics, process equipment, PVT, standards, mechanical design, flow assurance, safety, and…
CO2 capture, transport, storage (CCS) and hydrogen systems patterns for NeqSim. USE WHEN: modeling CO2 pipelines, injection wells, impurity effects on phase behavior, CO2 dense phase transport, hydrogen blending, electrolysis, or any CCS/H2 value chain analysis. Covers CO2 phase behavior, impurity management, well…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: