菜单
Guides agents through mainframe data modernization and offload workflows. Use when migrating or exposing data from COBOL, JCL, VSAM, IMS, DB2 for z/OS, or batch-oriented mainframe estates into modern lakes, warehouses, streaming systems, and governed data products.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Forces replay-safe rollout plans, reconciliation gates, and rollback paths before executing any data backfill or historical reprocessing. Use when running /backfill, rerunning pipelines, repairing publish windows, or any work that risks double-counting or downstream corruption.
Helps agents classify data engineering work, choose the right preset and skill bundle, and pick the safest next command. Use when starting a session, triaging an ambiguous request, or deciding how to proceed.
Guides agents through resiliency testing for data platforms. Use when designing or running failure drills, recovery validation, failover tests, replay-safety checks, dependency outage exercises, or fault injection for pipelines and publishes.
Guides agents through production data incidents. Use when a pipeline fails, publishes bad data, misses an SLA, partially loads, corrupts state, or requires rollback, replay, or stakeholder communication.
Enforces production Kafka guardrails including non-breaking schema evolution, dead-letter queues for poison messages, and acks=all producer durability. Use when designing or changing Kafka topics, producers, consumers, schema registry policies, or streaming recovery paths.
Guides agents to wire Model Context Protocol servers for live data platform observability including Spark execution plans, OOM diagnosis, Kafka consumer lag, and orchestration run state. Use when agents need cluster metrics, streaming lag, or job diagnostics instead of blind code changes.
| name | mainframe-modernization-and-data-offload |
| description | Guides agents through mainframe data modernization and offload workflows. Use when migrating or exposing data from COBOL, JCL, VSAM, IMS, DB2 for z/OS, or batch-oriented mainframe estates into modern lakes, warehouses, streaming systems, and governed data products. |
Use this skill when a modernization effort involves mainframe systems, batch schedules, and legacy data structures rather than only modern ETL tooling. It helps agents design offload, replication, contract mapping, coexistence, reconciliation, and cutover paths for mainframe-origin data.
COBOL, JCL, VSAM, IMS, or DB2 for z/OS data flowsDo not treat mainframe modernization as only a transport problem. Semantics, batch windows, restart behavior, and operational dependencies matter.
Inventory the legacy behavior. Capture:
Define the modernization target. Decide:
Design parity and reconciliation. Require:
Plan coexistence and cutover. Cover:
Validate operational readiness. Check restart, failure recovery, performance windows, and support responsibilities before moving critical consumers.
| Rationalization | Reality |
|---|---|
| "We only need to copy the files out." | Mainframe jobs often encode business rules, restart behavior, and sequencing that must be preserved or redesigned. |
| "Schema mapping is straightforward once we read the copybook." | Field semantics, packed decimals, dates, and code tables often require careful domain translation. |
| "We can switch consumers after one successful run." | Mainframe modernization usually needs parity evidence and a deliberate coexistence period. |