mainframe-ai
Overview
Use this skill when a task involves AI-assisted IBM z/OS or mainframe analysis, operations support, or modernization planning. The upstream project, W00t3k/mainframe-ai, is oriented around mainframe assistant workflows.
Compatibility: IBM z/OS, COBOL, JCL, and mainframe operations.
Workflow
- Establish the operating context: z/OS subsystem, batch job, dataset, CICS transaction, Db2 object, VSAM file, or COBOL program.
- Gather read-only evidence first, including JCL, PROC definitions, SYSOUT snippets, job history, abend codes, copybooks, and runbooks.
- Translate mainframe artifacts into explicit operational facts: job purpose, inputs, outputs, schedules, dependencies, and failure modes.
- For modernization tasks, map each artifact to a target disposition: retain, document, wrap, automate, convert, or retire.
- Produce operator-safe next steps with commands or code clearly separated from analysis.
Guardrails
- Treat production mainframe actions as high risk. Prefer read-only inspection and require human approval before suggesting state-changing commands.
- Preserve dataset naming, generation data group behavior, job restart semantics, and security controls.
- Do not infer abend root cause from a code alone; correlate with JCL, logs, program changes, and data conditions.
- Check the upstream repository before relying on any command examples or assistant integration details.
Expected Output
Return an evidence-backed mainframe analysis with affected artifacts, operational interpretation, modernization options, risks, and next actions.
1---2name: mainframe-ai3description: Use AI assistance for IBM z/OS and mainframe modernization tasks from the mainframe-ai project.4license: MIT5---67# mainframe-ai89## Overview1011Use this skill when a task involves AI-assisted IBM z/OS or mainframe analysis, operations support, or modernization planning. The upstream project, [W00t3k/mainframe-ai](https://github.com/W00t3k/mainframe-ai), is oriented around mainframe assistant workflows.1213Compatibility: IBM z/OS, COBOL, JCL, and mainframe operations.1415## Workflow16171. Establish the operating context: z/OS subsystem, batch job, dataset, CICS transaction, Db2 object, VSAM file, or COBOL program.182. Gather read-only evidence first, including JCL, PROC definitions, SYSOUT snippets, job history, abend codes, copybooks, and runbooks.193. Translate mainframe artifacts into explicit operational facts: job purpose, inputs, outputs, schedules, dependencies, and failure modes.204. For modernization tasks, map each artifact to a target disposition: retain, document, wrap, automate, convert, or retire.215. Produce operator-safe next steps with commands or code clearly separated from analysis.2223## Guardrails2425- Treat production mainframe actions as high risk. Prefer read-only inspection and require human approval before suggesting state-changing commands.26- Preserve dataset naming, generation data group behavior, job restart semantics, and security controls.27- Do not infer abend root cause from a code alone; correlate with JCL, logs, program changes, and data conditions.28- Check the upstream repository before relying on any command examples or assistant integration details.2930## Expected Output3132Return an evidence-backed mainframe analysis with affected artifacts, operational interpretation, modernization options, risks, and next actions.
autohandai