neqsim-standard-engineering-english

Applies controlled-language writing rules inspired by ASD-STE100 to final engineering documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Final engineering reports, procedures, and safety instructions often suffer from inconsistent terminology, ambiguous sentences, and unclear instructions that readers can misinterpret. This Skill provides a concise controlled-language house style inspired by ASD-STE100 so that procedures, warnings, requirements, and summaries are written with stable terminology and unambiguous structure. ## Core Features & Use Cases - Controlled Terminology: Enforces one preferred term per concept, consistent grammatical roles, and a single spelling convention across the document. - Procedure and Safety Writing Rules: Conditions precede commands, one instruction per sentence, and warnings state the condition, hazard, and consequence. - Sentence and Paragraph Discipline: Targets of 20 words for procedural sentences and 25 for descriptive sentences, one topic per paragraph, and notes used for information only. - Use Case: After completing NeqSim process calculations, an engineer generates a final operating procedure and applies this style so every step is a short imperative sentence with conditions stated first and warnings clearly separated from notes. ## Quick Start Ask the assistant to rewrite the final engineering report or procedure using the standard_engineering_english style before delivering it to readers.

Frequently Asked Questions about neqsim-standard-engineering-english

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

FAQPage Schema
How do I write engineering procedures in Simplified Technical English?

Apply controlled-language rules: put conditions before commands, start each action with an imperative verb, keep one instruction per sentence, and limit procedural sentences to about 20 words. This Skill provides a condensed house style inspired by ASD-STE100 for exactly that purpose.

What is a controlled language for technical documentation?

A controlled language restricts vocabulary and grammar so each term has one meaning and sentences follow predictable structures. This Skill implements a compact house style inspired by ASD-STE100 covering terminology, sentence length, voice, and safety text.

Does this style make documents ASD-STE100 compliant?

No. The Skill is independently worded guidance inspired by ASD-STE100 and does not reproduce its dictionary or rules. Full compliance requires the complete current specification, approved dictionary, domain glossary, and a formal compliance review.

When should I not use controlled engineering English?

Avoid it for analysis notes, ordinary chat, source extraction, code, and narrative or interpretive writing where argument and clarity of reasoning matter most. For prose-oriented reporting, a narrative style such as neqsim-prose-english is more appropriate.

How should warnings and cautions be written in technical procedures?

State the condition or command, the hazard, and the consequence in every safety instruction. Use warning for risk of injury or death and caution for equipment damage only when that distinction matches the governing domain standard.