NE

neqsim_standard_requirement_extraction

Extracts and classifies engineering requirements from technical standards for design verification.

Install

mkdir -p .claude/skills/neqsim-standard-requirement-extraction && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14875" && unzip -o skill.zip -d .claude/skills/neqsim-standard-requirement-extraction && rm skill.zip

Installs to .claude/skills/neqsim-standard-requirement-extraction

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Extract and map engineering requirements from standards or approved standards
77 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Extract requirement-level statements from standards
  • Preserve section, clause, page, and context metadata
  • Classify requirements as mandatory, recommendation, permission, information, or ambiguous
  • Link requirements to chapters, equipment, or skills
  • Summarize chapter-level standard relevance

How it works

The skill identifies standard codes, extracts requirement statements using keywords, preserves metadata, classifies items, and links them to relevant chapters or equipment.

Inputs & outputs

You give it
Standards PDF or approved excerpt, existing chapter text, optional OCR text
You get back
Structured JSON with extracted requirements and metadata

When to use neqsim_standard_requirement_extraction

  • Extract requirements from PDF standards
  • Map standards to chapters
  • Verify design against requirements
  • Classify engineering standards

About this skill

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.

Output Schema

{
  "standard": "NORSOK D-010",
  "revision": "latest-confirmed",
  "source": "approved local excerpt",
  "requirements": [
    {
      "id": "REQ-001",
      "level": "mandatory",
      "clause": "5.2",
      "topic": "well barriers",
      "text_excerpt": "short allowed excerpt or paraphrase",
      "context": "why it matters for the chapter",
      "mapped_chapters": ["ch14_drilling_and_wells"],
      "status": "candidate"
    }
  ]
}

Safety Rules

  • Respect standards copyright and license restrictions.
  • Prefer clause references and paraphrased summaries for public artifacts.
  • Do not claim compliance from keyword extraction alone; human review is needed.
  • Mark OCR-derived requirements as needs-human-check until reviewed.

Book Uses

  • Chapter 7: separator and vessel design.
  • Chapter 11: facility architecture, power systems, and design basis.
  • Chapter 13: subsea and SURF systems.
  • Chapter 14: wells and barriers.
  • Chapter 21: NCS regulation and standards governance.
  • Chapter 23: CO2 transport and injection integrity.

When not to use it

  • When extraction is not legally permitted due to license constraints
  • When human review of OCR-derived requirements is not possible
  • When claiming compliance solely based on keyword extraction

Limitations

  • Requires legal permission for extraction from standards
  • Does not claim compliance from keyword extraction alone
  • OCR-derived requirements need human review

How it compares

This skill automates the detailed extraction and classification of engineering requirements from standards, providing a structured output for design checks, unlike manual review.

Compared to similar skills

neqsim_standard_requirement_extraction side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
neqsim_standard_requirement_extraction (this skill)01moNo flagsIntermediate
legal-risk-assessment36moNo flagsIntermediate
lex03moReviewAdvanced
endo-avoid-sympathomimetic-cvd01moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

legal-risk-assessment

anthropics

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

336

lex

Anhvu1107

ALWAYS use this when the request matches LEX: Centralized ''Truth Engine'' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.

00

endo-avoid-sympathomimetic-cvd

dromlakhani

Recommends using non‑sympathomimetic agents (lorcaserin, orlistat) for pharmacological weight loss in patients with cardiovascular disease. Triggers include clinician questions such as “What weight‑loss medication is safest for this patient with coronary artery disease?” or “Should I avoid phentermi

00

contract-review

anthropics

Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.

728

literature-review

K-Dense-AI

Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).

5591,298

openalex-database

davila7

Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.

48202

Search skills

Search the agent skills registry