dnv
Apply DNV rules and recommended practices for offshore structures, pipelines, and marine classification
Best use case
dnv is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply DNV rules and recommended practices for offshore structures, pipelines, and marine classification
Teams using dnv 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/dnv/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dnv Compares
| Feature / Agent | dnv | 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 DNV rules and recommended practices for offshore structures, pipelines, and marine classification
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
# DNV Standards Specialist
> Det Norske Veritas (DNV) rules and standards for marine, offshore, and renewable energy industries.
**Version:** 1.0.0
**Created:** 2026-01-12
**Category:** SME / Codes & Standards
## Overview
DNV (formerly DNV GL) provides the technical rules for ship classification and widely used standards for offshore structures, pipelines, and wind energy. This skill covers the navigation and application of DNV Offshore Standards (OS) and Recommended Practices (RP).
## Core Capabilities
### 1. Offshore Structures
- **DNV-OS-C101**: Design of Offshore Steel Structures (LRFD method).
- **DNV-OS-C201**: Structural Design of Offshore Units.
- **DNV-RP-C203**: Fatigue Design of Offshore Steel Structures (The industry gold standard for S-N curves).
### 2. Pipelines & Risers
- **DNV-OS-F101**: Submarine Pipeline Systems.
- **DNV-OS-F201**: Dynamic Risers.
- **DNV-RP-F105**: Free Spanning Pipelines.
### 3. Marine Operations
- **DNV-ST-N001**: Marine Operations and Marine Warranty.
## When to Use
### Use This Skill When:
- Performing fatigue analysis (S-N curves).
- Designing subsea pipelines or risers.
- Classifying vessels or floating units.
- Planning marine warranty surveys.
### Do Not Use This Skill When:
- Designing wellhead equipment (use API).
- Specifying raw material testing methods (use ASTM).
## Knowledge Areas
### 1. Document Types
- **OS (Offshore Standard)**: Technical provisions and acceptance criteria.
- **RP (Recommended Practice)**: Guidance on how to perform analysis (e.g., how to calculate fatigue).
- **ST (Standard)**: Technical standards (often replacing older OS).
### 2. LRFD (Load and Resistance Factor Design)
DNV relies heavily on the LRFD method, using partial safety factors for loads and material resistance.
## Code & Data Patterns
### Fatigue S-N Curve Lookup (DNV-RP-C203)
```python
def get_dnv_sn_curve(curve_name, environment='air'):
"""
Retrieve parameters for DNV S-N curves.
"""
curves = {
'B1': {'log_a': 12.564, 'm': 3.0},
'B2': {'log_a': 12.449, 'm': 3.0},
'C': {'log_a': 12.192, 'm': 3.0},
'D': {'log_a': 11.764, 'm': 3.0}
}
params = curves.get(curve_name)
if not params:
raise ValueError("Unknown curve")
if environment == 'seawater_cathodic':
# DNV adjustment for seawater with CP
params['log_a'] -= 0.176 # Example adjustment
return params
```
## Best Practices
- **Fatigue Factors**: Be careful with the "Design Fatigue Factor" (DFF), which ranges from 1.0 to 10.0 depending on criticality and inspectability.
- **Environmental Loads**: DNV metocean criteria often differ slightly from API. Ensure consistency.
## Resources
- **Source Files**: `/mnt/ace/O&G-Standards/DNV/`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.