doc-extraction-cp-source-code-alignment

Sub-skill of doc-extraction-cp: Source Code Alignment.

5 stars

Best use case

doc-extraction-cp-source-code-alignment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of doc-extraction-cp: Source Code Alignment.

Teams using doc-extraction-cp-source-code-alignment 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

$curl -o ~/.claude/skills/source-code-alignment/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/doc-extraction/cp/source-code-alignment/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/source-code-alignment/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How doc-extraction-cp-source-code-alignment Compares

Feature / Agent	doc-extraction-cp-source-code-alignment	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: Source Code Alignment.

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

# Source Code Alignment

## Source Code Alignment


Extracted data should align with existing module constants:

| Module constant | Standard source |
|----------------|-----------------|
| `_B401_2021_CURRENT_DENSITIES` | DNV-RP-B401 Table 3-1 |
| `_B401_2021_COATING_CATEGORIES` | DNV-RP-B401 Section 3.4.6 |
| `_B401_2021_ANODE_CAPACITY` | DNV-RP-B401 Section 3.6 |
| `_B401_2021_POTENTIALS` | DNV-RP-B401 Section 2.4 |

Related Skills

llm-wiki-source-extraction-coverage

from vamseeachanta/workspace-hub

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.

worldenergydata-source-readiness

from vamseeachanta/workspace-hub

Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.

portable-baseline-pattern-extraction

from vamseeachanta/workspace-hub

Extract and separate portable baseline config from machine-specific overrides in multi-environment projects

parallel-array-alignment-pattern

from vamseeachanta/workspace-hub

Maintain index synchronization between parallel arrays when adding new entries to preserve label-path mappings

multi-source-tax-document-reconciliation

from vamseeachanta/workspace-hub

Verify generated tax forms against source documents by line-by-line comparison, not just totals

plan-draft-review-artifact-truthfulness-and-issue-body-alignment

from vamseeachanta/workspace-hub

Keep plan drafts truthful during adversarial review loops by verifying real provider artifact state on disk and aligning the GitHub issue body to the bounded plan tranche before claiming approval-readiness.