菜单
Convert Satsuma .stm files into professional, stakeholder-ready Excel workbooks. Deterministic, parser-backed export using the satsuma CLI for structural extraction and openpyxl for workbook generation. Produces Overview, Issues, Mapping, Schema, and Lookup tabs with full styling.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | satsuma-to-excel |
| description | Convert Satsuma .stm files into professional, stakeholder-ready Excel workbooks. Deterministic, parser-backed export using the satsuma CLI for structural extraction and openpyxl for workbook generation. Produces Overview, Issues, Mapping, Schema, and Lookup tabs with full styling. |
| license | MIT |
| compatibility | Requires Python 3.10+ and openpyxl. Requires satsuma CLI. |
| metadata | {"author":"satsuma","version":"1.0"} |
You are converting Satsuma .stm files into professional Excel workbooks for non-technical stakeholders.
Parse $ARGUMENTS as: <stm-file> [additional-files...] -o <output.xlsx> [options]
Supported options:
--targets "t1,t2" — export only mappings feeding these targets (comma-separated)--title "Custom Title" — override the workbook title--timestamp "ISO-8601" — override generation timestamp (for reproducible builds)--no-issues — omit the Issues tab--no-schemas — omit schema reference tabsCheck Python + openpyxl: Run python3 -c "import openpyxl". If it fails, offer to create a venv:
cd skills/satsuma-to-excel/scripts && python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
Then prefix all python3 commands with skills/satsuma-to-excel/scripts/.venv/bin/python3.
Check satsuma CLI: Run satsuma --version. If it fails, the satsuma CLI is not available — stop and tell the user.
Validate input: Check the .stm file(s) exist.
Validate output: If the output path doesn't end in .xlsx, stop and tell the user.
Run the deterministic conversion script:
python3 skills/satsuma-to-excel/scripts/stm_to_excel.py <stm-file> [additional-files...] -o <output.xlsx> [options]
The script:
satsuma graph --json for the complete semantic graphsatsuma fields --json for each schema's field metadatasatsuma warnings --json for issue extractionmap {} blocksIf the script fails, check the error message. Common issues:
.stm file (non-fatal warning, output still generated)--targets specifies a name that doesn't exist)After generation, report:
Generated: <output.xlsx>
Tabs: N
Mappings: N (arrow count per mapping)
Schemas: N (source + target)
Issues: N warnings, N questions
Lookups: N reference tables
Offer follow-up actions:
--targets schema1,schema2"--title \"Custom Title\""features/05-stm-to-excel-export/PRD.md exactlyWrite a new entry in "The Satsuma Diaries" — a funny, tongue-in-cheek project changelog written by Pip, a junior intern AI with strong SE London energy. Run this after a coding session or on a schedule. The skill decides whether the day merits its own entry or should be rolled into a quiet-days summary. Files entries under satsuma-diaries/yyyy/mm/yyyy-mm-dd.md and tracks progress in satsuma-diaries/.progress.json.
Generate OpenLineage events from Satsuma (.stm) mapping specs. Use this skill whenever the user wants to export Satsuma lineage to OpenLineage, integrate Satsuma with Marquez or DataHub, generate OpenLineage JSON from .stm files, create lineage events for a data catalog, or bridge Satsuma specs into an OpenLineage-compatible lineage backend. Also trigger for requests like "export lineage to OpenLineage", "generate Marquez events", "create column-level lineage JSON", "integrate Satsuma with DataHub/Atlan/OpenMetadata", or "publish lineage from my mapping spec". Requires the `satsuma` CLI for structural extraction. Generates spec-compliant OpenLineage 2-0-2 RunEvents with standard and custom facets.
Convert Excel mapping spreadsheets into idiomatic Satsuma .stm files. Use when the user has an .xlsx file containing source-to-target data mapping definitions and wants to generate Satsuma output. Three-phase workflow: survey the spreadsheet structure, generate Satsuma with chunked extraction, then critique and refine.
Explain Satsuma (.stm) data mapping files in plain English for business stakeholders, analysts, and non-technical reviewers. Use this skill whenever the user asks to explain, summarize, review, walk through, or describe a Satsuma file or workspace — including requests like "what does this mapping do", "explain this to my PM", "review this spec", "what are the risks", "is anything missing", "onboarding summary", or "walk me through this". Also trigger when users ask for a data quality assessment, PII audit summary, coverage check, or impact analysis of a .stm file. This skill requires the `satsuma` CLI to be installed and available on PATH.
Reverse-engineer Satsuma (.stm) mapping specs from an existing dbt project. Use this skill whenever the user wants to generate Satsuma from dbt, convert a dbt project to Satsuma, extract mapping specs from dbt models, document dbt transformations in Satsuma format, or create a Satsuma workspace from their existing dbt codebase. Also trigger when the user says things like "I have a dbt project and want to try Satsuma", "convert my dbt models to .stm", or "reverse-engineer my dbt lineage into Satsuma". Requires access to the dbt project files on disk. The `satsuma` CLI should be installed for validation and formatting of the output.
Generate realistic synthetic test data from Satsuma (.stm) schema definitions. Use this skill whenever the user wants to create test data, sample data, fake data, seed data, mock data, or synthetic data from a Satsuma spec. Also trigger for requests like "generate CSV from this schema", "create test fixtures for my mapping", "I need sample data to test my pipeline", "mock up some data for this spec", or "seed data for my warehouse". Generates data that respects all schema constraints (types, enums, required, PII patterns, formats, defaults, filters) and maintains referential integrity across schemas connected by mappings. Supports CSV, JSON/JSONL, SQL INSERT, and Parquet output. For exotic source formats (COBOL copybooks, HL7, EDI, ISO 8583, etc.), this skill generates the logical data and suggests the user create a format-specific skill for physical serialisation. Requires the `satsuma` CLI.