api
Apply American Petroleum Institute codes and standards for offshore structures and production systems
Best use case
api is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply American Petroleum Institute codes and standards for offshore structures and production systems
Teams using api 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/api/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api Compares
| Feature / Agent | api | 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 American Petroleum Institute codes and standards for offshore structures and production systems
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
# API Standards Specialist
> American Petroleum Institute (API) codes and standards for oil & gas production, refining, and offshore structures.
**Version:** 1.0.0
**Created:** 2026-01-12
**Category:** SME / Codes & Standards
## Overview
API standards are the globally recognized benchmarks for the oil and gas industry. This skill focuses on the application, lookup, and programmatic compliance verification of API specifications (Specs), Recommended Practices (RPs), and Standards (Std).
## Core Capabilities
### 1. Offshore Structures (Series 2)
- **API 2RD**: Dynamic Risers for Floating Production Systems.
- **API 2INT-MET**: Interim Metocean Criteria.
- **API 2A-WSD**: Planning, Designing, and Constructing Fixed Offshore Platforms.
### 2. Equipment & Valves (Series 6)
- **API 6A**: Wellhead and Christmas Tree Equipment.
- **API 6D**: Pipeline Valves.
- **API 610**: Centrifugal Pumps.
### 3. Subsea Production (Series 17)
- **API 17D**: Subsea Wellhead and Tree Equipment.
- **API 17N**: Subsea Production System Reliability, Technical Risk, and Integrity Management.
## When to Use
### Use This Skill When:
- Specifying equipment for drilling or production operations.
- Designing offshore structures (fixed or floating).
- Verifying valve and pump requirements.
- Conducting risk assessments (API 17N, API 14C).
### Do Not Use This Skill When:
- Designing ship hulls (use Class Society rules like DNV/ABS).
- Checking material testing protocols (use ASTM).
- Checking European pressure vessel codes (use PED/EN).
## Knowledge Areas
### 1. Spec vs. RP vs. Std
- **Spec (Specification)**: Prescriptive requirements. "Shall" statements are mandatory. (e.g., API 6A).
- **RP (Recommended Practice)**: Guidance and best practices. "Should" statements. (e.g., API RP 2SK for Mooring).
- **Std (Standard)**: Established norms.
### 2. Digital Lookup
Use the `StandardsLookup` tool to find full documents.
Path: `/mnt/ace/O&G-Standards/API/`
## Code & Data Patterns
### Compliance Check Pattern
```python
def check_api_6a_compliance(pressure_rating, temp_class, material_class):
"""
Verify API 6A equipment rating.
"""
valid_pressures = [2000, 3000, 5000, 10000, 15000, 20000]
if pressure_rating not in valid_pressures:
return False, f"Invalid API 6A pressure rating: {pressure_rating}"
valid_temp_classes = ['K', 'L', 'P', 'R', 'S', 'T', 'U', 'V']
if temp_class not in valid_temp_classes:
return False, f"Invalid API 6A temp class: {temp_class}"
return True, "Compliant"
```
### Search Implementation
```python
from digitalmodel.modules.standards_lookup import StandardsLookup
def find_api_docs(query):
lookup = StandardsLookup()
# Filter for API specifically
results = [r for r in lookup.search(query) if "/API/" in r['path']]
return results
```
## Best Practices
- **Version Control**: Always check the "Effective Date" of the standard. API standards are updated frequently.
- **Addenda**: Check for published addenda or errata sheets which modify the base document.
- **Monogram**: Ensure equipment manufacturers hold a valid API Monogram license if required.
## Resources
- **Source Files**: `/mnt/ace/O&G-Standards/API/`
- **Official Site**: api.orgRelated 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.