doc-extraction-domain-sub-skills
Sub-skill of doc-extraction: Domain Sub-Skills.
Best use case
doc-extraction-domain-sub-skills is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of doc-extraction: Domain Sub-Skills.
Teams using doc-extraction-domain-sub-skills 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/domain-sub-skills/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How doc-extraction-domain-sub-skills Compares
| Feature / Agent | doc-extraction-domain-sub-skills | 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: Domain Sub-Skills.
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
# Domain Sub-Skills ## Domain Sub-Skills For domain-specific extraction heuristics, delegate to Layer 3 sub-skills: | Domain | Sub-skill | When to use | |--------|-----------|-------------| | Cathodic protection | [cp/SKILL.md](cp/SKILL.md) | DNV-RP-B401, F103, CP design documents | | Drilling riser | [drilling-riser/SKILL.md](drilling-riser/SKILL.md) | API RP 16Q, riser analysis reports | | Naval architecture | [naval-architecture/SKILL.md](naval-architecture/SKILL.md) | SNAME PNA, IMO stability, classification rules |
Related Skills
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.
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
extract-skills-from-hermes-sessions
Automatically analyze Codex session transcripts to identify and extract reusable skills using LLM analysis via OpenRouter
extract-skills-from-Codex-sessions
Automatically extract reusable skills from Codex session transcripts using LLM analysis and wire them into a Stop hook
engineering-solver-domain-recon
Deep reconnaissance of an engineering solver domain (OrcaWave, OrcaFlex, CalculiX, OpenFOAM, etc.) across a multi-repo ecosystem — map infrastructure, issues, skills, data artifacts, machine constraints, and solver queue state before planning work.
domain-gap-to-issue-roadmap
Deep multi-repo ecosystem audit → domain gap matrix → structured GitHub issue roadmap with epics. Use when the user wants to assess capabilities across repos and create a backlog of work items covering code, data, and documentation gaps.
engineering-domain-reconnaissance
Class-level external engineering domain reconnaissance: field development, external drive ingest planning, and source-to-artifact conversion.
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.