neqsim-standard-requirement-extraction SKILL.md skillA
neqsim-standard-requirement-extraction from equinor/neqsim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add equinor/neqsim/neqsim-standard-requirement-extraction@git:20260919.77c34a0Pins git:20260919.77c34a0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- equinor/neqsim
- Path
.github/skills/neqsim-standard-requirement-extraction/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260919.77c34a0, committed Sep 19, 2026
- Size
- 2,449 bytes
- Repository stars
- 167
- License
- Apache-2.0
Extract and map engineering requirements from standards or approved standards.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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@sha256:55eae216115358ceThe line at the top of this page pins the label git:20260919.77c34a0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ousljwbw4jopflo7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 19, 2026.
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 · 167 stars · license Apache-2.0 · pushed 2026-11-08 · 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 AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.