doc-extraction-yield-reality-wrk-1246-corpus-assessment
Sub-skill of doc-extraction: Yield Reality (WRK-1246 Corpus Assessment).
Best use case
doc-extraction-yield-reality-wrk-1246-corpus-assessment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of doc-extraction: Yield Reality (WRK-1246 Corpus Assessment).
Teams using doc-extraction-yield-reality-wrk-1246-corpus-assessment 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/yield-reality-wrk-1246-corpus-assessment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How doc-extraction-yield-reality-wrk-1246-corpus-assessment Compares
| Feature / Agent | doc-extraction-yield-reality-wrk-1246-corpus-assessment | 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: Yield Reality (WRK-1246 Corpus Assessment).
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
# Yield Reality (WRK-1246 Corpus Assessment) ## Yield Reality (WRK-1246 Corpus Assessment) WRK-1246 assessed deep extraction yield across 420K+ text-extractable documents. Only two content types have proven extraction yield from the current parsers: | Content type | Yield | Status | |-------------|-------|--------| | tables | 69-93% | **Production-ready** — primary extraction target | | figure_refs | 1-52% | **Partial** — metadata only, varies by stratum | | equations | 0% | Not yet implemented — parsers do not reliably detect | | constants | 0% | Not yet implemented — parsers do not reliably detect | | procedures | 0% | Not yet implemented — parsers do not reliably detect | | worked_examples | 0% | Not yet implemented — parsers do not reliably detect | These content types are NOT currently extractable from the corpus — they exist in the manifest schema (documented below) but the parsers do not reliably detect them. The schema is retained for future parser development.
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
ai-tool-assessment
Assess and report on AI tool subscriptions, usage patterns, and cost-effectiveness. Use for reviewing AI subscriptions, analyzing tool usage, optimizing AI spend.
risk-assessment
Perform probabilistic risk assessment with Monte Carlo simulations for offshore marine operations
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.
session-corpus-audit
Analyze session quality trends — identify high-churn patterns, report waste, flag sessions exceeding 500 tool calls
multi-tool-architecture-assessment
Systematic comparison of competing tools/approaches before committing to a multi-account, multi-tool architecture. Uses parallel subagents for research, system-state audit, and data quality analysis. Produces a decision matrix with explicit trade-offs.
legal-risk-assessment
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria