neqsim-agent-handoff

Standardize agent-to-agent handoffs in NeqSim pipelines with JSON payloads.

138|60|Updated Dec 5, 2018
One-click install
npx skills add https://github.com/equinor/neqsim --skill neqsim-agent-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neqsim-agent-handoff
Source: https://github.com/equinor/neqsim/tree/main/.github/skills/neqsim-agent-handoff
Command: npx skills add https://github.com/equinor/neqsim --skill neqsim-agent-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficient cross-agent communication in NeqSim pipelines by standardizing handoff payloads, ensuring consistent data formats and traceability.

Core Features & Use Cases

  • Schema-driven handoffs: fluid_definition, process_simulation, mechanical_design, flow_assurance, safety_analysis
  • Structured, code-ready payloads with explicit fields and source attribution
  • Easy integration into agent workflows to reduce miscommunication and data loss

Quick Start

Format your results as a JSON payload according to the active handoff schema and submit it to the orchestrator.

Frequently Asked Questions about neqsim-agent-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize agent-to-agent handoffs in a NeqSim pipeline?

NeqSim agent handoffs are standardized by formatting agent outputs into JSON payloads that conform to predefined schemas like fluid_definition and process_simulation, ensuring traceability and consistent data formats across multi-agent workflows.

What schemas are available for structuring NeqSim fluid definitions and process simulations?

Available schemas include fluid_definition, process_simulation, mechanical_design, flow_assurance, and safety_analysis, each providing explicit fields and source attribution for structured cross-agent communication in NeqSim pipelines.

How do I format NeqSim simulation results for the next agent in a workflow?

Format your process simulation results as a JSON payload according to the active handoff schema and submit it to the orchestrator, providing explicit fields, documentation, and traceability for the receiving agent.

Can I use structured JSON payloads to pass mechanical design data between NeqSim agents?

Yes, you can pass mechanical design data between NeqSim agents by structuring it as a JSON payload that conforms to the mechanical_design schema, which provides explicit fields and source attribution for accurate cross-agent communication.

Why do I need a schema-driven handoff format for multi-agent NeqSim workflows?

Schema-driven handoffs are needed in multi-agent NeqSim workflows to reduce miscommunication and data loss by enforcing consistent data formats, explicit fields, and traceability across fluid definitions, simulations, and designs.