doc-extraction-cp-anode-formulae
Sub-skill of doc-extraction-cp: Anode Formulae (+3).
Best use case
doc-extraction-cp-anode-formulae is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of doc-extraction-cp: Anode Formulae (+3).
Teams using doc-extraction-cp-anode-formulae 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/anode-formulae/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How doc-extraction-cp-anode-formulae Compares
| Feature / Agent | doc-extraction-cp-anode-formulae | 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?
Sub-skill of doc-extraction-cp: Anode Formulae (+3).
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
# Anode Formulae (+3)
## Anode Formulae
Equations for anode mass, current output, resistance, and utilisation.
**Detection heuristics**:
- Keywords: "anode mass", "current capacity", "utilisation factor", "anode resistance"
- Symbols: `M_a`, `C_a`, `u`, `R_a`, `I_a`
- Units: kg, Ah/kg, ohm, ampere
- Geometric terms: "length", "radius", "cross-section"
**Key extraction fields**:
```yaml
- content_type: equations
domain: cathodic_protection
sub_type: anode_formula
data:
name: "Anode current output"
expression: "I_a = (E_c - E_a) / R_a"
variables:
- {symbol: I_a, name: "anode current output", units: A}
- {symbol: E_c, name: "structure protection potential", units: V}
- {symbol: E_a, name: "anode closed-circuit potential", units: V}
- {symbol: R_a, name: "anode resistance", units: ohm}
source: "DNV-RP-B401 Section 4.3"
```
**Anode resistance formulae** (by geometry):
- Flush-mounted: McCoy's formula — `R = ρ / (2π × S)` where S = shape factor
- Stand-off: Dwight's formula — depends on length/radius ratio
- Bracelet: Peterson's formula — for cylindrical anodes on pipelines
## Coating Breakdown Factors
Linear degradation model: `f_c(t) = f_ci + k × t`, clamped at 1.0.
**Detection heuristics**:
- Keywords: "coating breakdown", "breakdown factor", "coating category"
- Symbols: `f_c`, `f_ci`, `k`, `t`
- Pattern: table with Category I/II/III rows, f_ci and k columns
- Section reference: typically Section 3.4 in B401
**Key extraction fields**:
```yaml
- content_type: constants
domain: cathodic_protection
sub_type: coating_breakdown
data:
name: "Coating Category I breakdown parameters"
values:
f_ci: {value: 0.05, units: dimensionless, description: "Initial breakdown factor"}
k: {value: 0.020, units: "1/year", description: "Degradation rate"}
applicability:
category: "I"
description: "High quality >= 300 um epoxy"
source: "DNV-RP-B401 Section 3.4.6"
```
**Category definitions** (B401-2021):
| Category | f_ci | k | Description |
|----------|------|---|-------------|
| I | 0.05 | 0.020 | High quality ≥300 μm epoxy |
| II | 0.10 | 0.030 | Anti-friction thin film / PTFE |
| III | 0.25 | 0.050 | Standard quality paint system |
| bare | 1.00 | 0.000 | No coating — bare steel |
## Design Life Tables
Design life parameters for CP system sizing.
**Detection heuristics**:
- Keywords: "design life", "service life", "lifetime", "years"
- Pattern: table with years in one column, other parameters varying
- Often cross-referenced with temperature and environmental severity
- Section reference: typically early sections of B401/F103
**Key extraction fields**:
```yaml
- content_type: tables
domain: cathodic_protection
sub_type: design_life
data:
title: "CP design life parameters"
columns: [design_life_years, mean_current_density, final_current_density]
applicability:
temperature_band: ">12-17°C"
environment: "seawater"
source: "DNV-RP-B401 Table 3-2"
```
## Current Density Values
Design current densities by zone and environmental condition.
**Detection heuristics**:
- Keywords: "current density", "mean current density", "initial current density", "final current density"
- Units: mA/m², A/m²
- Pattern: table indexed by zone (submerged/splash/atmospheric) and temperature
- Distinction between coated and bare steel values
**Key extraction fields**:
```yaml
- content_type: constants
domain: cathodic_protection
sub_type: current_density
data:
name: "Mean design current density — submerged, coated"
current_density_type: mean # mean | initial | final
value: 0.060
units: "A/m²"
applicability:
zone: submerged
temperature_range: ">12-17°C"
surface_condition: coated
source: "DNV-RP-B401 Table 3-1"
```
**Structured discriminator**: Always include `current_density_type` (one of
`mean`, `initial`, `final`) — do not encode the type only in the `name` field.
**Zone classification**:
| Zone | Description | Temperature dependency |
|------|-------------|----------------------|
| Submerged | Below splash zone, permanently immersed | Yes — 4 temperature bands |
| Splash | Tidal and wave action zone | No — fixed values |
| Atmospheric | Above splash, exposed to marine atmosphere | No — fixed values |Related Skills
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.
portable-baseline-pattern-extraction
Extract and separate portable baseline config from machine-specific overrides in multi-environment projects
doc-extraction-naval-architecture
Layer 3 domain sub-skill for extracting naval architecture data from SNAME PNA, IMO stability codes, IACS structural rules, and classification society guidelines. Provides detection heuristics for stability constants, resistance equations, hull form coefficients, hydrostatic curves, IMO stability criteria, and structural scantling tables. type: reference
doc-extraction-drilling-riser
Layer 3 domain sub-skill for extracting drilling riser data from API RP 16Q, DNV-RP-C205, and riser analysis reports. Provides detection heuristics for VIV parameters, kill/choke line specs, and BOP stack configurations. type: reference
doc-extraction
Classify and extract structured content from engineering documents using a 3-layer taxonomy: generic content types, engineering patterns, and domain sub-skills. Use when ingesting standards, reports, or technical manuals into structured data for downstream analysis. type: reference
gmail-email-to-repo-extraction
Extract structured data from Gmail inbox emails, enrich with domain-specific classification, legal-scan against deny list, commit to appropriate repo, then optionally delete originals.
gmail-data-extraction
Extract structured data from Gmail emails using REST API (no pip dependencies). Covers inbox scanning, subject line regex extraction, email text parsing, thread-aware drafting, and legal-scan-before-commit workflow.
orcawave-analysis-orcfxapi-result-extraction
Sub-skill of orcawave-analysis: OrcFxAPI Result Extraction (+3).
orcaflex-extreme-analysis-basic-extreme-extraction
Sub-skill of orcaflex-extreme-analysis: Basic Extreme Extraction (+1).
doc-extraction-yield-reality-wrk-1246-corpus-assessment
Sub-skill of doc-extraction: Yield Reality (WRK-1246 Corpus Assessment).
doc-extraction-unit-detection-and-normalization
Sub-skill of doc-extraction: Unit Detection and Normalization (+4).
doc-extraction-output-schema
Sub-skill of doc-extraction: Output Schema.