neqsim-prose-english

Write direct, concrete prose for final engineering reports and generated summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering reports and AI-generated summaries often suffer from vague wording, passive constructions, canned openings, decorative formatting, and hidden uncertainty. This Skill provides style guidance, derived from George Orwell's "Politics and the English Language" plus house rules against common AI formatting habits, to produce clear and honest final-report prose. ## Core Features & Use Cases - Plain-language rewriting rules: Replace stock phrases, inflated diction, euphemisms, and abstract noun chains with concrete actors, actions, and measured facts. - AI formatting guardrails: Remove decorative bold text, em dashes, canned openings and closings, and forced symmetrical list structures. - Validation checklist and mistake table: Verify that claims, quantities, uncertainty, and responsibility survive the editing process. - Use Case: After completing a NeqSim process simulation, use this Skill to write the executive summary and conclusion so the report states findings, evidence, and uncertainty directly instead of sounding machine-generated. ## Quick Start Use the prose_english style to rewrite the executive summary of my simulation report in direct, concrete language.

Frequently Asked Questions about neqsim-prose-english

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

FAQPage Schema
How do I write a clear executive summary for an engineering report?▼

Decide the claim, evidence, actor, and consequence before drafting, then state them directly with measured quantities ahead of adjectives. This Skill provides rewriting rules and a validation checklist to keep the summary concrete and honest.

How to remove AI-sounding formatting from generated reports?▼

Apply the house rules in this Skill: remove decorative bold text, em dashes, canned openings like "This comprehensive report explores", generic closing offers, and forced symmetrical lists. Let the evidence determine paragraph structure instead of a fixed template.

When should I use prose_english versus standard engineering English?▼

Use prose_english for interpretive final-report prose such as summaries, discussions, and conclusions. Use neqsim-standard-engineering-english for procedures, warnings, equipment instructions, and tightly controlled technical descriptions.

Does plain language writing reduce technical precision?▼

No. The guidance keeps necessary technical terms and defines them once for the audience, and it forbids making sentences vivid at the cost of technical accuracy. Quantitative statements must retain value, unit, basis, and uncertainty.

What are the limitations of this writing style guidance?▼

It does not validate calculations, evidence, citations, or compliance, and it is not a controlled language like ASD-STE100. It must not override mandatory regulatory wording, contractual terminology, report templates, or accessibility requirements.