norsok
Apply NORSOK standards for Norwegian petroleum industry materials, safety, and structural design
Best use case
norsok is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply NORSOK standards for Norwegian petroleum industry materials, safety, and structural design
Teams using norsok should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/norsok/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How norsok Compares
| Feature / Agent | norsok | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply NORSOK standards for Norwegian petroleum industry materials, safety, and structural design
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# NORSOK Standards Specialist
> Norsk Sokkels Konkurranseposisjon (NORSOK) standards for the Norwegian petroleum industry.
**Version:** 1.0.0
**Created:** 2026-01-12
**Category:** SME / Codes & Standards
## Overview
NORSOK standards are developed by the Norwegian petroleum industry to ensure adequate safety, value adding, and cost effectiveness. They are known for being more stringent than international standards, particularly regarding materials and safety in harsh North Sea environments.
## Core Capabilities
### 1. Materials & Corrosion (M-Series)
- **M-001**: Materials selection.
- **M-501**: Surface preparation and protective coating.
- **M-601**: Welding and inspection of piping.
### 2. Drilling & Well (D-Series)
- **D-010**: Well integrity in drilling and well operations. (The global benchmark for well barriers).
### 3. Safety & Working Environment (S-Series)
- **S-001**: Technical Safety.
- **S-002**: Working Environment.
## When to Use
### Use This Skill When:
- Designing for the North Sea or harsh cold-climate environments.
- Defining Well Barrier Schematics (D-010).
- Specifying high-durability coating systems (M-501).
## Knowledge Areas
### 1. Well Barriers (D-010)
NORSOK D-010 defines the "Two Barrier Principle":
1. **Primary Barrier**: First line of defense (e.g., fluid column, packer).
2. **Secondary Barrier**: Back-up (e.g., BOP, Wellhead).
### 2. Material Data Sheets (MDS)
M-001 refers to specific MDSs that precisely define chemistry and testing for steel grades (e.g., "MDS D46" for Duplex Stainless Steel).
## Code & Data Patterns
### Barrier Status Check
```python
def check_barrier_status(primary_status, secondary_status):
"""
Evaluate well integrity based on NORSOK D-010 principles.
"""
if primary_status == "OK" and secondary_status == "OK":
return "GREEN: Healthy"
elif primary_status == "FAILED" and secondary_status == "OK":
return "ORANGE: Degraded (Single Barrier Failure)"
elif secondary_status == "FAILED":
return "RED: Unsafe (Secondary or Double Failure)"
else:
return "UNKNOWN"
```
## Best Practices
- **Strictness**: Assume NORSOK requirements exceed API/ISO unless proven otherwise.
- **Coatings**: M-501 systems (e.g., System 7 for submerged) are industry standards even outside Norway.
## Resources
- **Source Files**: `/mnt/ace/O&G-Standards/Norsok/`Related Skills
test-oversized-skill
A test fixture skill that exceeds 200 lines with multiple H2/H3 sections for split testing.
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
OrcaFlex Specialist Skill
```yaml
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
subagent-write-verification
Independently verify subagent-claimed file writes with filesystem and git checks before treating the artifact as real, before committing it, and before referencing the path in downstream prompts.
git-operation-serialization-preflight
Before any commit, stash, merge, reset, rebase, or checkout in a multi-agent or shared-checkout environment, run a bounded preflight to detect active git writers and stale index/config locks, then serialize the mutating step under a single-writer guarantee.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
llm-wiki-weekly-freshness
Class-level governance workflow for keeping llm-wiki-style markdown knowledge bases current, public-safe, graph/index-valid, and useful for code development. Use when reviewing llm-wiki architecture/content, scanning new LLM concepts, maintaining public knowledge graphs, producing an issue roadmap, or running recurring freshness cadence.
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.