Skip to content
Agent Orchestration
Skill

/mainframe-removal

Apply mainframe dependency transformations to COBOL code using a pre-generated transformation guide. Converts CICS/VSAM constructs to standard COBOL.

BOOST
From plugin
extensions
17185 skills4 commands
Install
$ npx -y skills add openhands/extensions --skill mainframe-removal --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/mainframe-removal

Context preview

The summary Claude sees to decide when to auto-load this skill.

Apply mainframe dependency transformations to COBOL code using a pre-generated transformation guide. Converts CICS/VSAM constructs to standard COBOL.

SKILL.md

mainframe-removal.SKILL.md
name: mainframe-removal
description: Apply mainframe dependency transformations to COBOL code using a pre-generated transformation guide. Converts CICS/VSAM constructs to standard COBOL.
license: MIT
compatibility: Requires GnuCOBOL (cobc) for verification
triggers:
  - remove mainframe
  - cobol transformation
  - cics removal
  - standard cobol

Apply the transformations from a transformation guide to convert mainframe-specific COBOL to standard COBOL.

**Prerequisite**: A transformation guide must exist (see `cobol-mainframe-planning` skill).

Transformation Requirements

Data Operations

  • Replace each CICS/VSAM construct with its standard COBOL equivalent per the plan
  • Add FILE STATUS checks after EVERY file operation:
  • Check for success (00) before proceeding
  • Handle "not found" (23) distinctly from I/O errors (3x)
  • Handle "file not exists" (35) at OPEN time
  • Add explicit CLOSE statements in all code paths (including error paths)

UI/Terminal Operations (BMS maps, SEND/RECEIVE)

  • Replace with simple stubs or ACCEPT/DISPLAY statements
  • Do NOT spend time replicating screen layouts
  • Focus on preserving data flow, not UI fidelity

Error Handling

  • Replace CICS RESP/RESP2 checks with equivalent FILE STATUS logic
  • Replace HANDLE CONDITION with explicit status checking after operations
  • Ensure error paths don't leave files open

See [references/cics-transformation-examples.md](references/cics-transformation-examples.md) for before/after code examples.

Verification

After transformation:

  • Code MUST compile without errors
  • Test with valid input → should execute core business logic
  • Test with missing/invalid files → should fail gracefully, not crash

Preserve

  • All original business logic
  • Data transformations and calculations
  • Validation rules

Checklist

  • [ ] All EXEC CICS commands replaced
  • [ ] FILE STATUS declared for all files
  • [ ] FILE STATUS checked after every I/O operation
  • [ ] CLOSE statements in all code paths
  • [ ] Code compiles successfully
  • [ ] Basic test execution passes
Read more
Ships withextensions

This repository is the public extensions registry for OpenHands. It contains reusable, shareable skills, plugins, and Agent Canvas Apps that customize agent behavior and interfaces. Skills overview docs: SDK skill guide:

Get the whole plugin

Other skills on extensions.