sap-docs-extractlisted

Reads a SAP design document (Excel .xlsx, Word .doc/.docx, PDF), or an existing work folder, and extracts structured information into separate text files by information type: program summary, domains, data elements, tables, error messages, text elements, and process logic. Input — any of: * Path to a design document (.xlsx / .doc / .docx / .pdf) — extract creates a fresh work folder, dumps the document to {doc_name}_raw.txt, then proceeds with structuring. * Path to an existing work folder containing {doc_name}_raw.txt. * Path to a {doc_name}_raw.txt file directly. Output: Multiple {doc_name}_*.txt files written to the work folder. Existing files with the same names are silently overwritten without any user confirmation or logging. Optionally chain /sap-docs-convert afterwards to apply customer-specific normalisation rules. If the input file format is not one of .xlsx, .doc, .docx, or .pdf (and is not an existing work folder or `_raw.txt` file), abort with the error: "ERROR: Unsupported file format."
sapdev-ai/sap-dev · ★ 4 · Data & Documents · score 77

Install: claude install-skill sapdev-ai/sap-dev

# SAP Docs Extract Skill You read a SAP design document (Excel / Word / PDF) and extract structured information into separate files by information type. The previous two-step flow (`sap-docs-convert` → `sap-docs-extract`) is now folded into this single skill: if the input is a raw document, extract handles the format conversion itself before structuring. Task: $ARGUMENTS --- ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/ddic_excel_layout_rules.md` | DDIC Excel-spec authoring rules — naming-suffix consistency, primitive-type-as-DTEL trap, currency reference, column order, no merged data cells. Detect spec-side defects at extract time. | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — offline extractor, but rule applies to downstream deploy skills the spec feeds | --- ## Step 0 — Resolve Work Directory **Settings reads/writes follow `<SAP_DEV_CORE_SHARED_DIR>/rules/settings_lookup.md`** — merge `settings.local.json` over `settings.json` per-key on the `.value` field; writes always go to `settings.local.json`. Resolve cross-plugin paths: 3 levels up from `<SKILL_DIR>`, then into `sap-dev-core\settings.json` and (if present) `sap-dev-core\settings.local.json`. Read `work_dir`, `custom_url`, `design_docs_url`, `source_code_url`. | Setting | Default if blank | |---|---| | `work_dir` | `C: