iso
Apply ISO standards for materials, corrosion, safety, and oil and gas industry compliance
Best use case
iso is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply ISO standards for materials, corrosion, safety, and oil and gas industry compliance
Teams using iso 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/iso/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How iso Compares
| Feature / Agent | iso | 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 ISO standards for materials, corrosion, safety, and oil and gas industry compliance
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
# ISO Standards Specialist
> International Organization for Standardization (ISO) codes for general engineering, materials, and safety.
**Version:** 1.0.0
**Created:** 2026-01-12
**Category:** SME / Codes & Standards
## Overview
ISO standards provide the universal framework for quality, safety, and specific technical systems. In the context of this repository, we focus on ISO standards adopted by the oil & gas industry (often harmonized with API) and general engineering specs.
## Core Capabilities
### 1. Materials & Corrosion
- **ISO 15156**: Materials for use in H2S-containing environments (NACE MR0175). Critical for "Sour Service".
- **ISO 898**: Mechanical properties of fasteners.
### 2. Pipeline & Drilling
- **ISO 13628**: Design and operation of subsea production systems (parallels API 17 series).
- **ISO 19900 series**: Petroleum and natural gas industries – General requirements for offshore structures.
### 3. Quality & Safety
- **ISO 9001**: Quality Management Systems.
- **ISO 14001**: Environmental Management.
## When to Use
### Use This Skill When:
- Selecting materials for sour service (H2S).
- Working on international projects where API is not the governing code.
- Specifying fasteners and bolts.
- Establishing quality management protocols.
## Knowledge Areas
### 1. ISO vs. API
Many ISO standards are "identical" or "modified" adoptions of API standards (e.g., ISO 13628-4 = API 17D). However, regional annexes may apply.
### 2. Sour Service (ISO 15156)
The definitive guide for preventing Sulfide Stress Cracking (SSC). It classifies materials based on H2S partial pressure and pH.
## Code & Data Patterns
### Sour Service Region Check
```python
def check_nace_region(pH, pH2S_psi):
"""
Determine severity region (0, 1, 2, 3) based on ISO 15156 / NACE MR0175.
(Simplified logic for demonstration)
"""
if pH2S_psi < 0.05:
return "Region 0 (No specific requirements)"
if pH > 3.5:
return "Region 1 (Low Severity)"
else:
return "Region 3 (High Severity - Strict Material Controls)"
```
## Best Practices
- **Harmonization**: Check if an API equivalent exists (e.g., API 6A vs ISO 10423).
- **Traceability**: ISO standards emphasize material traceability and certification (Type 3.1, 3.2 certs).
## Resources
- **Source Files**: `/mnt/ace/O&G-Standards/ISO/`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.