doc-extraction-cp-standards-reference
Sub-skill of doc-extraction-cp: Standards Reference.
Best use case
doc-extraction-cp-standards-reference is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of doc-extraction-cp: Standards Reference.
Teams using doc-extraction-cp-standards-reference 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/standards-reference/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How doc-extraction-cp-standards-reference Compares
| Feature / Agent | doc-extraction-cp-standards-reference | 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: Standards Reference.
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
# Standards Reference ## Standards Reference | Standard | Scope | |----------|-------| | DNV-RP-B401 | Cathodic protection design (offshore fixed/floating) | | DNV-RP-F103 | Cathodic protection of submarine pipelines | | NACE SP0169 | Control of external corrosion (pipelines) | | ISO 15589-2 | CP for offshore production installations | | EN 12954 | CP for buried/immersed metallic structures |
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
aqwa-reference
AQWA solver stages (RESTART), OPTIONS keywords, FIDP/FISK external damping/stiffness cards, backend bugs, and MCP tool integration patterns.
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.
docs-stale-reference-guardrails
Prevent deleted workflow/path references from creeping back into live docs by combining strict scans, legacy allowlists, and shared regex helpers.
repo-cleanup-references-to-remove
Sub-skill of repo-cleanup: References to Remove.
hidden-folder-audit-common-hidden-folders-reference
Sub-skill of hidden-folder-audit: Common Hidden Folders Reference.
skill-creator-official-plugin-reference
Sub-skill of skill-creator: Official Plugin Reference.