Agent skill

Migrate Oracle Forms

by mendixlabs in mendixlabs/mxcli

Assess and migrate Oracle Forms applications to Mendix — .fmb forms to pages, PL/SQL to microflows, and a staged migration strategy.

Apache-2.0Auto-check passedDatabases

Install Migrate Oracle Forms

skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-oracle-forms -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mendixlabs/mxcli migrate-oracle-forms --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/migrate-oracle-forms .claude/skills/migrate-oracle-forms && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
migrate-oracle-forms
GitHub stars
128
Token cost
~3.4k tokens
SKILL.md length
827 words
Files
1
Skills in repo
75
Repo updated
First seen
Licence
Apache-2.0

At a glance

Assess and migrate Oracle Forms applications to Mendix — .fmb forms to pages, PL/SQL to microflows, and a staged migration strategy.

  • Works in 4 steps: Data Model: Oracle tables → Mendix… → Business Logic: PL/SQL… → User Interface: Forms blocks/items →… → …
  • Converting an Oracle Forms system
  • SKILL.md covers When to Use This Skill, Migration Overview, Reserved Word Conflicts and Script Organization, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Migrate Oracle Forms is an agent skill from mendixlabs/mxcli. Assess and migrate Oracle Forms applications to Mendix — .fmb forms to pages, PL/SQL to microflows, and a staged migration strategy. Use when analysing or converting an Oracle Forms system.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering SQL. It works with SQL. The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.

When your agent uses it

  • Converting an Oracle Forms system
  • Tasks that involve SQL

Example prompts

  • “/migrate-oracle-forms”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Data Model: Oracle tables → Mendix entities
  2. Business Logic: PL/SQL triggers/procedures → Mendix microflows
  3. User Interface: Forms blocks/items → Mendix pages/widgets
  4. Navigation: Form canvases → Mendix page navigation

What it can do on your machine

Read from SKILL.md and the folder at commit a924d11. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are mdl and sql).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Migrate Oracle Forms loads about 3.4k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 827 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mendixlabs/mxcli at commit a924d11, republished under its Apache-2.0 licence (© mendixlabs). 827 words, ~3,418 tokens.

Download SKILL.mdSave it as .claude/skills/migrate-oracle-forms/SKILL.md (or your agent's skills folder).
name
migrate-oracle-forms
description
Assess and migrate Oracle Forms applications to Mendix — .fmb forms to pages, PL/SQL to microflows, and a staged migration strategy. Use when analysing or converting an Oracle Forms system.

Oracle Forms to Mendix Migration Skill

This skill provides comprehensive guidance for migrating Oracle Forms applications to Mendix using MDL (Mendix Definition Language).

When to Use This Skill

Use this skill when:

  • Converting Oracle Forms (.fmb) applications to Mendix
  • Translating PL/SQL logic to Mendix microflows
  • Mapping Oracle Forms UI elements to Mendix widgets
  • Planning a migration strategy for legacy Oracle Forms systems

Migration Overview

Oracle Forms migration to Mendix involves:

  1. Data Model: Oracle tables → Mendix entities
  2. Business Logic: PL/SQL triggers/procedures → Mendix microflows
  3. User Interface: Forms blocks/items → Mendix pages/widgets
  4. Navigation: Form canvases → Mendix page navigation

Reserved Word Conflicts

Most common words (check, text, format, value, type, index, status, select, etc.) now work unquoted as attribute names in MDL. Only structural keywords (create, delete, begin, end, return, entity, module) need quoting.

Naming Best Practices

While most words are no longer reserved, using descriptive names is still recommended for clarity:

Oracle Forms FieldRecommended Mendix NameNotes
checkcheck or CheckStatusWorks unquoted
texttext or TextContentWorks unquoted
formatformat or FormatTypeWorks unquoted
valuevalue or FieldValueWorks unquoted
NameName or ItemNameWorks unquoted (not a keyword)
typetype or ItemTypeWorks unquoted
create"create" or CreatedByRequires quoting (structural keyword)
delete"delete" or IsDeletedRequires quoting (structural keyword)
Example
mdl
mdl 1;
create persistent entity MyModule.FormField (
  check: boolean default false,  -- Works unquoted
  text: string(500),             -- Works unquoted
  format: string(50),            -- Works unquoted
  CheckFlag: boolean default false, -- Renamed alternative (also fine)
  TextContent: string(500), -- Renamed
  FormatType: string(50)    -- Renamed
);

Script Organization

Execution Order Dependencies

MDL scripts execute statements sequentially. Items created in one statement can be referenced in subsequent statements within the same script execution.

Key Insight: Microflows and pages created earlier in the script are tracked and can be resolved by later statements.

mdl
mdl 1;
-- ============================================
-- PHASE 1: Domain Model (Entities & Associations)
-- ============================================

create persistent entity MyModule.Customer (
  CustomerCode: string(50),
  CustomerName: string(200),
  Email: string(200),
  IsActive: boolean default true
);

create persistent entity MyModule.Order (
  OrderNumber: string(50),
  OrderDate: datetime,
  TotalAmount: decimal
);

create association MyModule.Order_Customer
from MyModule.Order to MyModule.Customer
type reference;

-- ============================================
-- PHASE 2: Microflows (Business Logic)
-- ============================================

/**
 * Validates and saves a customer record
 * Replaces Oracle Forms POST-INSERT/POST-UPDATE triggers
 */
create microflow MyModule.ACT_Customer_Save ($Customer: MyModule.Customer)
returns boolean as $success
begin
  declare $success boolean = false;

  -- Validation (replaces WHEN-VALIDATE-ITEM)
  if $Customer/CustomerCode = empty then
    validation feedback $Customer/CustomerCode message 'Customer code is required';
    return false;
  end if;

  commit $Customer;
  set $success = true;
  return $success;
end;

-- ============================================
-- PHASE 3: Pages (User Interface)
-- ============================================

-- Now this page can reference the microflow created above
create page MyModule.Customer_Edit (
  Title: 'Edit Customer',
  Layout: Atlas_Core.PopupLayout,
  Params: ( $Customer: MyModule.Customer )
) {
  dataview dvCustomer (DataSource: $Customer) {
    textbox txtCode (Label: 'Customer Code', Attribute: CustomerCode)
    textbox txtName (Label: 'Name', Attribute: CustomerName)
    textbox txtEmail (Label: 'Email', Attribute: Email)
    footer {
      -- Reference to the microflow created in Phase 2
      actionbutton btnSave (Caption: 'Save', Action: call microflow MyModule.ACT_Customer_Save(Customer = $Customer), ButtonStyle: Primary)
      actionbutton btnCancel (Caption: 'Cancel', Action: close page)
    }
  }
};

Validation Feedback

VALIDATION FEEDBACK Syntax

CRITICAL: VALIDATION FEEDBACK requires an attribute path, not just a message.

WRONG:

mdl
validation feedback 'Customer code is required';  -- Missing attribute!

CORRECT:

mdl
-- Syntax: VALIDATION FEEDBACK $entity/attribute MESSAGE 'message'
validation feedback $Customer/CustomerCode message 'Customer code is required';
validation feedback $Order/OrderDate message 'Order date cannot be in the future';
Mapping Oracle Forms Validation
Oracle FormsMendix MDL
when-VALIDATE-item triggerif ... validation feedback in microflow
raise FORM_TRIGGER_FAILUREvalidation feedback + return false
message('error text')validation feedback $entity/attribute message 'error text'
Complete Validation Pattern
mdl
mdl 1;
/**
 * Validates order before save
 * Replaces Oracle Forms WHEN-VALIDATE-RECORD trigger
 */
create microflow MyModule.ACT_Order_Validate ($Order: MyModule.Order)
returns boolean as $IsValid
begin
  declare $IsValid boolean = true;

  -- Required field validation
  if $Order/OrderNumber = empty then
    validation feedback $Order/OrderNumber message 'Order number is required';
    set $IsValid = false;
  end if;

  -- Date validation
  if $Order/OrderDate > [%CurrentDateTime%] then
    validation feedback $Order/OrderDate message 'Order date cannot be in the future';
    set $IsValid = false;
  end if;

  -- Cross-field validation
  if $Order/TotalAmount < 0 then
    validation feedback $Order/TotalAmount message 'Total amount cannot be negative';
    set $IsValid = false;
  end if;

  return $IsValid;
end;

PL/SQL to Microflow Mapping

Data Manipulation
Oracle PL/SQLMendix MDL
insert into table ...$var = create Module.Entity (...)
update table set ...change $var (...) + commit $var
delete from table ...delete $var
select ... into ...retrieve $var from Module.Entity where ...
commitcommit $var
rollbackBuilt-in with error handlers
Control Flow
Oracle PL/SQLMendix MDL
if ... then ... elsif ... else ... end ifif ... then ... else ... end if
for ... loop ... end looploop $item in $list begin ... end loop
while ... loop ... end loopNot directly supported; use recursive microflow
CURSORretrieve $list from ... then loop
EXCEPTION when ... thenon error begin ... end error
Example: PL/SQL to MDL

Oracle PL/SQL:

sql
declare
  v_count NUMBER := 0;
  v_total NUMBER := 0;
begin
  for rec in (select * from orders where status = 'PENDING') loop
    v_count := v_count + 1;
    v_total := v_total + rec.amount;

    update orders set status = 'PROCESSED' where id = rec.id;
  end loop;

  commit;
  DBMS_OUTPUT.PUT_LINE('Processed ' || v_count || ' orders, total: ' || v_total);
EXCEPTION
  when OTHERS then
    rollback;
    raise;
end;

Mendix MDL:

mdl
mdl 1;
create microflow MyModule.ACT_ProcessPendingOrders ()
returns string as $Result
begin
  declare $count integer = 0;
  declare $Total decimal = 0;
  declare $Result string = '';

  -- Retrieve pending orders (replaces CURSOR) — retrieve creates $OrderList,
  -- never declare a list variable first (CE0053/CE0038, MDL040)
  retrieve $OrderList from MyModule.Order
    where status = 'PENDING';

  -- Process each order (replaces FOR LOOP)
  loop $Order in $OrderList
  begin
    set $count = $count + 1;
    set $Total = $Total + $Order/Amount;

    change $Order (status = 'PROCESSED');
    commit $Order on error begin
      log error 'Failed to process order: ' + $Order/OrderNumber;
    end error;
  end loop;

  log info 'Processed ' + toString($count) + ' orders, total: ' + toString($Total);
  set $Result = 'Processed ' + toString($count) + ' orders';
  return $Result;
end;

UI Component Mapping

Oracle Forms Items to Mendix Widgets
Oracle Forms ItemMendix WidgetMDL Syntax
Text ItemText InputINPUT 'name' attribute attr
Display ItemTexttext 'content'
Check BoxCheck Boxcheckbox 'name' attribute attr
Radio GroupRadio ButtonsRADIO 'name' attribute attr
List Item (LOV)Drop-downdropdown 'name' attribute attr
Push ButtonButtonbutton 'name' on CLICK ...
Tab CanvasTab ContainerTAB_CONTAINER (TAB 'name' (...))
Oracle Forms Blocks to Mendix DataViews

Oracle Forms Block → Mendix DataView:

mdl
-- Single-record block
dataview source $Customer (
  INPUT 'Code' attribute CustomerCode,
  INPUT 'Name' attribute CustomerName
)

-- Multi-record block (tabular)
datagrid source $OrderList (
  column 'OrderNumber' attribute OrderNumber,
  column 'OrderDate' attribute OrderDate,
  column 'Amount' attribute TotalAmount
)
Master-Detail Pattern

Oracle Forms Master-Detail → Mendix:

mdl
-- check-skip: shorthand pseudo-syntax sketch of the migrated page, not runnable
-- MDL. See create-page / overview-pages for real page syntax.
create page MyModule.CustomerOrders
layout Atlas_Default
title 'Customer Orders'
parameter $Customer: MyModule.Customer
widgets (
  -- Master block
  dataview source $Customer (
    INPUT 'Code' attribute CustomerCode readonly,
    INPUT 'Name' attribute CustomerName readonly
  ),

  -- Detail block (orders for this customer)
  datagrid 'OrderGrid' source database MyModule.Order
    where '[MyModule.Order_Customer = $Customer]' (
    column 'OrderNumber' attribute OrderNumber,
    column 'OrderDate' attribute OrderDate,
    column 'Amount' attribute TotalAmount
  )
);
/
Show full SKILL.md (328 more words)Show less

Triggers to Microflows

Common Trigger Mappings
Oracle Forms TriggerMendix Implementation
when-NEW-FORM-INSTANCEPage load microflow (data source)
when-NEW-RECORD-INSTANCEOnChange microflow on data source
when-VALIDATE-itemOnChange microflow or validation in save
when-VALIDATE-RECORDValidation microflow before save
post-queryMicroflow data source with transformation
PRE-insert / PRE-updateBefore commit event handler
post-insert / post-updateAfter commit event handler
key-commitSave button action microflow
on-erroron error begin ... end error blocks

Migration Checklist

Before starting migration:

  • Export Oracle Forms XML (.xml) or use Forms2XML utility
  • Document all triggers and their purposes
  • Map database tables to Mendix entities
  • Identify LOVs and map to enumerations
  • Check for structural keyword conflicts (Create, Delete, Begin, End, Return)

During migration:

  • Create entities first (Phase 1)
  • Create microflows second (Phase 2)
  • Create pages last (Phase 3) - they can reference microflows
  • Test validation patterns thoroughly
  • Use validation feedback $entity/attribute message 'message' for all validations

After migration:

  • Run mxcli check script.mdl -p app.mpr --references
  • Open in Mendix Studio Pro to verify
  • Test all validation scenarios
  • Verify master-detail relationships work correctly

Common Migration Errors

ErrorCauseFix
"Parse error: mismatched input 'Create'"Structural keyword as attributeUse "create" (quoted) or rename
"microflow not found"Referenced before createdMove microflow definition before page
"page not found"Referenced before createdMove page definition earlier
"VALIDATION FEEDBACK requires attribute"Missing attribute pathUse validation feedback $entity/attribute message 'msg'
CE0117 "Error in expression"Missing module prefixUse fully qualified names

Tips for Success

  1. Plan attribute names carefully: Most words work unquoted; only structural keywords (create, delete, begin, end, return) need quoting
  2. Organize scripts by phase: Entities → Microflows → Pages
  3. Test incrementally: Migrate one form at a time
  4. Keep validation close to logic: Embed validation in save microflows
  5. Document mappings: Track which Oracle Forms items map to which Mendix elements
  6. Use meaningful names: ACT_Customer_Save not SUB_SAVE
  7. Leverage CRUD generation: Use /create-crud skill for standard operations

© mendixlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/mendix/migrate-oracle-forms of mendixlabs/mxcli.

Open the folder on GitHubat commit a924d11

Compare with similar skills

Migrate Oracle Forms next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Migrate Oracle Forms compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Migrate Oracle Forms this skillmendixlabs/mxcli128—~3.4kAutomated safety check: PassApache-2.0
Evolving The Data ModelTriliumNext/Trilium38k—~2.1kAutomated safety check: PassAGPL-3.0
SQL Optimization Patternsynulihao/AgentSkillOS61710 repos~3.3kAutomated safety check: PassNone
SQL PortabilityHL7/sql-on-fhir150—~512Automated safety check: PassCustom licence
DB Migrationskurealnum/dotfiles290—~820Automated safety check: PassNone
Contact FilterChatbotXIO/ChatbotX878—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Evolving The Data Model

    TriliumNext/Trilium

    A skill your agent uses when adding a DB migration or a new column/field to a Becca entity in Trilium ("add a migration", "new column on notes/attributes", "ALTER TABLE", "add a field to…

    38k GitHub stars~2.1k tokensUpdated today
    DatabasesAuto-check passed
  • SQL Optimization Patterns

    ynulihao/AgentSkillOS

    Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries.

    617 GitHub starsUsed in 10 repos~3.3k tokens
    DatabasesAuto-check passed
  • SQL Portability

    HL7/sql-on-fhir

    Analyse whether a SQL query is portable across database implementations using sqlglot transpilation.

    150 GitHub stars~512 tokensUpdated yesterday
    DatabasesAuto-check passed
  • DB Migrations

    kurealnum/dotfiles

    A skill your agent uses when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration…

    290 GitHub stars~820 tokensUpdated 5 mo ago
    DatabasesAuto-check passed
  • Contact Filter

    ChatbotXIO/ChatbotX

    Work with the ChatbotX contact filter system — the shared filter model behind the contacts list, conversations, and broadcast audiences.

    878 GitHub stars~2.5k tokensUpdated today
    DatabasesAuto-check passed
  • Add Utils Function

    MichealWayne/fe-tools

    Add or modify utility functions in fe-tools. An agent skill from MichealWayne/fe-tools.

    207 GitHub stars~602 tokensUpdated 29 days ago
    DatabasesAuto-check passed

More from mendixlabs/mxcli

All 75 skills in this repo
  • Mendix Odata Pushdown

    mendixlabs/mxcli

    Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…

    128 GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Mendix Vega Charts

    mendixlabs/mxcli

    Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.

    128 GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Agents

    mendixlabs/mxcli

    Author Mendix AI agent documents in MDL — Model, Knowledge Base, Consumed MCP Service and Agent, with variables, tools and multi-line prompts.

    128 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Mendix Bulk Oql Dml

    mendixlabs/mxcli

    Run set-based INSERT, UPDATE and DELETE against Mendix entities through OQL statements, which the runtime supports and Studio Pro cannot author.

    128 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Mock REST APIs

    mendixlabs/mxcli

    Stand up an HTTP endpoint you control instead of a live third-party API, and point the Mendix app at it — Prism from an OpenAPI contract, a constant swap, or a forward proxy.

    128 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • REST Client

    mendixlabs/mxcli

    Call external REST APIs from Mendix — the three approaches (inline REST CALL, consumed REST client document, generated from OpenAPI) and how to choose.

    128 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed

Works with

Categories

Questions about Migrate Oracle Forms

What does Migrate Oracle Forms do?

Assess and migrate Oracle Forms applications to Mendix — .fmb forms to pages, PL/SQL to microflows, and a staged migration strategy. Migrate Oracle Forms is an agent skill from mendixlabs/mxcli.fmb forms to pages, PL/SQL to microflows, and a staged migration strategy.

When should I use Migrate Oracle Forms?

Migrate Oracle Forms fits situations like: converting an Oracle Forms system; tasks that involve SQL.

How do I install Migrate Oracle Forms in Claude Code?

Run `npx skills add mendixlabs/mxcli --skill migrate-oracle-forms -a claude-code`. Or copy the skill folder (.claude/skills/mendix/migrate-oracle-forms in mendixlabs/mxcli) into .claude/skills/migrate-oracle-forms in your project. Claude Code loads it when a task matches its description.

How do I install Migrate Oracle Forms in Codex?

Run `npx skills add mendixlabs/mxcli --skill migrate-oracle-forms -a codex`. Or copy the skill folder (.claude/skills/mendix/migrate-oracle-forms in mendixlabs/mxcli) into .agents/skills/migrate-oracle-forms in your project. Codex loads it when a task matches its description.

Can I use Migrate Oracle Forms in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill migrate-oracle-forms -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-oracle-forms, .gemini/skills/migrate-oracle-forms, .github/skills/migrate-oracle-forms and .opencode/skills/migrate-oracle-forms in your project.

What does Migrate Oracle Forms need to run?

SKILL.md names no scripts, command-line tools or credentials: Migrate Oracle Forms is instructions for the agent only.

Does Migrate Oracle Forms access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Migrate Oracle Forms safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Migrate Oracle Forms use?

Migrate Oracle Forms is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Migrate Oracle Forms use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Migrate Oracle Forms?

Skills that share tags, products or a category with Migrate Oracle Forms: Evolving The Data Model (TriliumNext/Trilium, 38k stars), SQL Optimization Patterns (ynulihao/AgentSkillOS, 617 stars), SQL Portability (HL7/sql-on-fhir, 150 stars) and DB Migrations (kurealnum/dotfiles, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Migrate Oracle Forms?

mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on October 7, 2026.

Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.