neqsim-final-report-writing-style

Selects and applies prose_english or standard_engineering_english when generating final engineering reports.

4|2|Updated May 31, 2026
One-click install
npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-final-report-writing-style-equinor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neqsim-final-report-writing-style
Source: https://github.com/equinor/neqsim-community-skills/tree/main/skills/reporting/final-report-writing-style
Command: npx skills add https://github.com/equinor/neqsim-community-skills --skill neqsim-final-report-writing-style-equinor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Final engineering reports often mix interpretive narrative with procedural instructions, and applying one writing style uniformly produces unclear or inconsistent documents. This Skill routes final report content to the correct writing style based on the reader's task, with explicit user override and controlled per-section exceptions. ## Core Features & Use Cases - Automatic style routing: Chooses prose_english for interpretive and decision-oriented content, and standard_engineering_english for procedures, requirements, warnings, and equipment descriptions. - User override and section exceptions: Honors an explicit user style request and applies controlled section overrides in mixed reports. - Auditable selection record: Records the primary style, selection reason, and section overrides in results.json for reviewer traceability. - Use Case: After completing NeqSim calculations and validation, a reporting agent generates a final PDF report; this Skill selects prose_english for the executive summary while routing operating procedures to standard_engineering_english. ## Quick Start Ask the agent to generate the final engineering report and let it select the appropriate writing style, or explicitly request prose_english or standard_engineering_english for the document.

Frequently Asked Questions about neqsim-final-report-writing-style

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

FAQPage Schema
How do I choose a writing style for a final engineering report?▼

Choose by the reader's task: use prose_english when readers interpret evidence or make decisions, and standard_engineering_english when they follow procedures, limits, or requirements. An explicit user request always takes precedence over automatic selection.

When should the writing style selection happen in a reporting workflow?▼

Selection occurs only at the final reporting or document-revision step, after calculations, evidence review, and validation are complete. It must not run during analysis, working notes, ordinary chat, or code generation.

Can a report mix prose_english and standard_engineering_english?▼

Yes. Mixed reports use prose_english as the primary style with controlled section overrides applying standard_engineering_english to procedures, checklists, warnings, cautions, equipment descriptions, and method steps.

Does this skill make a document ASD-STE100 compliant?▼

No. The condensed standard_engineering_english style does not confer ASD-STE100 compliance. Deliverables requiring compliance must follow the full ASD-STE100 standard and its compliance workflow.

Does applying a writing style change technical content or results?▼

No. Style revision affects narrative expression only. Numbers, units, citations, uncertainty statements, findings, and the direction of recommendations must remain exactly unchanged.