neqsim-standard-requirement-extraction skillA
neqsim-standard-requirement-extraction is agent-read markdown (skill) from equinor/neqsim: Extract and map engineering requirements from standards or approved standards.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Skill: NeqSim Standard Requirement Extraction ## Purpose Extract and map engineering requirements from standards or approved standards excerpts into a structured format that can support NeqSim book chapters, engineering reports, and design checks. Use this for NORSOK, DNV, API, ISO, IEC, ASME, and similar standards when clause-level traceability is needed. ## Inputs - A standards PDF or approved excerpt, when extraction is legally permitted. - Existing chapter text or `standards_map.json` to identify the target chapter and equipment context. - Optional OCR text for scanned standards. ## Workflow 1. Identify the standard code, revision, publisher, and license constraints. 2. Extract only requirement-level statements using keywords such as `shall`, `should`, `may`, `required`, and standard-specific forms. 3. Preserve section, clause, page, context-before, and context-after metadata. 4. Classify each item as mandatory, recommendation, permission, information, or ambiguous. 5. Link each item to chapters, equipment, or skills without copying large licensed text into public outputs. 6. Use `book-standards-map` to summarize the chapter-level standard relevance. …
Read the whole file at its exact version.
How to install
mdr add equinor/neqsim/neqsim-standard-requirement-extraction@git:20260919.77c34a0mdr add equinor/neqsim/neqsim-standard-requirement-extraction@sha256:55eae216115358cePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ousljwbw4jopflo7)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2449 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
equinor/neqsim · 155 stars · license Apache-2.0 · pushed 2026-09-24 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_ousljwbw4jopflo7 GET https://markdownregistry.com/api/v1/resolve?ref=equinor/neqsim/neqsim-standard-requirement-extraction GET https://markdownregistry.com/api/v1/blob/55eae216115358ce0703bb8aad3f9bd0528077d2a6ac6717bdadc496d4fc5c23
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.