Agent skill

Migrate K2 Nintex

by mendixlabs in mendixlabs/mxcli

Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.

Apache-2.0Auto-check passedDocuments & Office

Install Migrate K2 Nintex

skills CLI
$ npx skills add mendixlabs/mxcli --skill migrate-k2-nintex -a claude-code

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

GitHub CLI
$ gh skill install mendixlabs/mxcli migrate-k2-nintex --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-k2-nintex .claude/skills/migrate-k2-nintex && 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-k2-nintex
GitHub stars
128
Token cost
~4.1k tokens
SKILL.md length
1,161 words
Files
1
Skills in repo
72
Repo updated
First seen
Licence
Apache-2.0

At a glance

Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.

  • Works in 11 steps: K2 Package (.kspx) → Legacy Project Files → K2 APIs → …
  • Converting a K2 application
  • SKILL.md covers When to Use This Skill, Understanding K2 Application…, Export and Package Options and Migration Strategy, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Migrate K2 Nintex is an agent skill from mendixlabs/mxcli. Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Use when analysing or converting a K2 application.

Its SKILL.md is about 4.1k 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 Documents & Office. It works with Microsoft SharePoint. 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 a K2 application

Example prompts

  • “/migrate-k2-nintex”

Workflow steps

11 steps, taken from the step headings in SKILL.md.

  1. K2 Package (.kspx)
  2. Legacy Project Files
  3. K2 APIs
  4. Inventory SmartObjects
  5. Inventory SmartForms
  6. Inventory Workflows
  7. Map Rules and Logic
  8. Domain Model
  9. Business Logic (Microflows)
  10. Pages
  11. Security

What it can do on your machine

Read from SKILL.md and the folder at commit 20a6c89. 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 sql, markdown and csharp).

    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 K2 Nintex loads about 4.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,161 words of instructions outside code blocks.

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

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 20a6c89, republished under its Apache-2.0 licence (© mendixlabs). 1,161 words, ~4,105 tokens.

Download SKILL.mdSave it as .claude/skills/migrate-k2-nintex/SKILL.md (or your agent's skills folder).
name
migrate-k2-nintex
description
Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Use when analysing or converting a K2 application.

K2/Nintex to Mendix Migration Skill

This skill provides comprehensive guidance for assessing and migrating K2 (now Nintex K2) applications to Mendix using MDL (Mendix Definition Language).

When to Use This Skill

Use this skill when:

  • Analyzing K2/Nintex applications for migration to Mendix
  • Converting SmartObjects to Mendix domain models
  • Mapping SmartForms Views to Mendix pages
  • Translating K2 Workflows to Mendix microflows or workflows
  • Planning a migration strategy for legacy K2 systems

Understanding K2 Application Architecture

K2 applications are fundamentally different from Mendix in how they're stored and structured.

K2 Storage Model

Key Difference: K2 applications are server-side/database-stored, not file-based like Mendix. All K2 project elements and data are saved into the K2 database, not as files. This is one of the key challenges for migration.

AspectK2/NintexMendix
StorageServer database.mpr file (SQLite)
VersioningServer-managedGit-based (MPR v2)
Export format.kspx package.mpk package
Project fileNo single file.mpr project file
K2 Artifact Types

A K2 application is composed of several artifact types:

SmartObjects

Middle layer between data providers (SQL, SAP, SharePoint) and data consumers (forms, workflows, reports). They abstract data from LOB systems.

SmartObject TypeDescriptionMendix Mapping
SmartBoxStores data in K2's own databasePersistable Entity
SQL ConnectorConnects to SQL Server tablesExternal Database Connector
SAP ConnectorConnects to SAP systemsOData/REST Integration
SharePoint ConnectorConnects to SharePoint listsREST Client
Service ObjectExposes services/methodsMicroflow/Java Action
SmartForms

Browser-based forms composed of Views and Forms:

SmartForms ElementDescriptionMendix Mapping
ViewReusable collection of controls + rules bound to SmartObjectsSnippet or Page Section
FormContainer for views, accessible via URLPage
ControlUI element (text, date, dropdown, etc.)Widget
RuleEvent-driven logic ("when button clicked, execute method")Nanoflow or Microflow
Workflows

Process definitions with steps, tasks, branching logic:

Workflow ElementDescriptionMendix Mapping
WorkflowFull process definitionWorkflow or Microflow chain
ActivityIndividual step in workflowMicroflow activity or User Task
TaskHuman task requiring user actionUser Task
Destination RuleRouting logic for tasksDecision (microflow)
DatafieldWorkflow data variableParameter or Variable

Export and Package Options

There's no single "project file" like Mendix's .mpr. Your options for extracting K2 app definitions:

1. K2 Package (.kspx)

The K2 Package and Deployment tool packages K2 artifacts (SmartObjects, forms, views, workflows) into a single file with a .kspx extension. This is the primary mechanism for moving apps between environments.

How to export:

K2 Management Site → Solutions → Package → export
2. Legacy Project Files

Older K2 Studio / K2 for Visual Studio projects used:

File TypeExtensionContents
Project file.k2projProject structure and references
Workflow definition.kprxWorkflow definition
SmartObject definition.sodxSmartObject schema
3. K2 APIs

SmartObject Runtime API and management APIs can be used programmatically to extract definitions:

csharp
// Example: Programmatic SmartObject extraction
using SourceCode.SmartObjects.Client;

SmartObjectClientServer server = new SmartObjectClientServer();
server.CreateConnection();
SmartObject so = server.GetSmartObject("CustomerSO");
// Extract properties, methods, etc.

Migration Strategy

For a K2 → Mendix migration, approach it in layers:

Layer 1: Data Model (SmartObjects → Entities)
SmartObject TypeMigration Approach
SmartBox SmartObjectsDirect translation to Mendix persistable entities
SQL Connector SmartObjectsOptions: (a) Import data to Mendix, (b) External Database Connector
Service SmartObjectsMicroflows that call external services

Example MDL:

sql
mdl 1;
-- SmartBox SmartObject "Customer" → Mendix Entity
create persistent entity CRM.Customer (
  CustomerCode: string(50),
  CustomerName: string(200),
  Email: string(200),
  Phone: string(50),
  IsActive: boolean default true,
  CreatedDate: autocreateddate
);

-- SmartBox SmartObject "Order" → Mendix Entity
create persistent entity CRM.Order (
  OrderNumber: string(50),
  OrderDate: datetime,
  status: CRM.OrderStatus,  -- Enumeration
  TotalAmount: decimal
);

-- SmartObject relationship → Association
create association CRM.Order_Customer
from CRM.Order to CRM.Customer
type reference;
Layer 2: UI (SmartForms → Pages)

SmartForms Views map to Mendix pages/snippets. The rules system (event-driven, "when X happens, do Y") maps well to Mendix's nanoflow/microflow-on-events pattern.

SmartForms ControlMendix Widget
Text BoxTEXTBOX
Text AreaTEXTAREA
Drop-down ListCOMBOBOX
Date PickerDATEPICKER
Check BoxCHECKBOX
Radio ButtonRADIOBUTTONS
Data LabelDYNAMICTEXT
ButtonACTIONBUTTON
List ViewLISTVIEW or DATAGRID
SubviewSNIPPETCALL
Tab ControlTab container pattern
SmartForms Rules to Mendix Events
SmartForms RuleMendix Implementation
When Control is ClickedButton action microflow/nanoflow
When View is InitializedPage data source microflow
When Control Value ChangesOnChange nanoflow
When Data LoadsData source microflow
Execute SmartObject MethodMicroflow calling entity operations
Transfer DataVariable assignment in microflow
Show/Hide ControlConditional visibility
Enable/Disable ControlEditable expression

Example MDL (SmartForm View → Mendix Page):

sql
mdl 1;
create page CRM.Customer_Edit
(
  params: ( $Customer: CRM.Customer ),
  title: 'Edit Customer',
  layout: Atlas_Core.PopupLayout
)
{
  dataview dvCustomer (datasource: $Customer) {
    -- Text Box controls
    textbox txtCode (label: 'Customer Code', attribute: CustomerCode)
    textbox txtName (label: 'Customer Name', attribute: CustomerName)
    textbox txtEmail (label: 'Email', attribute: Email)
    textbox txtPhone (label: 'Phone', attribute: Phone)

    -- Check Box control
    checkbox chkActive (label: 'Active', attribute: IsActive)

    -- Button bar (SmartForms action buttons)
    footer {
      actionbutton btnSave (caption: 'Save', action: save changes, buttonstyle: primary)
      actionbutton btnCancel (caption: 'Cancel', action: cancel changes)
    }
  }
};
Layer 3: Process (Workflows → Microflows/Workflows)

K2 Workflows translate to Mendix microflows or the Workflow module:

K2 Workflow ElementMendix Mapping
StartMicroflow start / Workflow start
Task (human)User Task activity
Reference (call SmartObject)Microflow activities (Create, Change, Retrieve)
DecisionDecision (split/merge)
Send EmailEmail activity
Generate DocumentGenerate document microflow
Web Service CallREST/Web service call
ScriptJava action or expressions
EndEnd event / Microflow return
EscalationScheduled event or timer
Destination RuleMicroflow logic for task assignment
Show full SKILL.md (459 more words)Show less
Task Allocation Mapping
K2 Destination RuleMendix User Task
Specific UserUser by association
RoleXPath targeting user role
ManagerMicroflow calculating manager
QueueFirst user from filtered list

Example MDL (K2 Task → Mendix Microflow):

sql
mdl 1;
-- K2 Task "Review Order" → Mendix microflow for task handling
create microflow CRM.ACT_Order_SubmitForReview ($Order: CRM.Order)
begin
  -- Update status (like K2 "Set Status")
  change $Order (status = CRM.OrderStatus.PendingReview);
  commit $Order;

  -- Show page for review (like K2 "Task" with form)
  show page CRM.Order_Review (Order = $Order);
end;

-- K2 Decision "Order > $5000?" → Mendix microflow with decision
create microflow CRM.ACT_Order_ProcessApproval ($Order: CRM.Order)
returns boolean as $Approved
begin
  declare $Approved boolean = false;

  if $Order/TotalAmount > 5000 then
    -- Route to manager (K2 Destination Rule equivalent)
    call microflow CRM.ACT_Order_SubmitForManagerReview (Order = $Order);
  else
    -- Auto-approve (K2 "Go To" equivalent)
    change $Order (status = CRM.OrderStatus.Approved);
    commit $Order;
    set $Approved = true;
  end if;

  return $Approved;
end;

Assessment Workflow

When assessing a K2 application for migration:

Step 1: Inventory SmartObjects

Export SmartObject definitions and categorize:

markdown
| SmartObject Name | type | data source | entity count | Mendix mapping |
|------------------|------|-------------|--------------|----------------|
| CustomerSO | SmartBox | K2 DB | single | CRM.Customer entity |
| OrderSO | SmartBox | K2 DB | single | CRM.Order entity |
| EmployeeSO | sql | HR database | single | Integration or import |
| SAPOrderSO | SAP | SAP ERP | multiple | odata service |
Step 2: Inventory SmartForms

Document all forms and views:

markdown
| Form Name | views Used | SmartObjects | Mendix mapping |
|-----------|------------|--------------|----------------|
| Customer Entry | CustomerView, AddressView | CustomerSO, AddressSO | Customer_Edit page |
| Order Dashboard | OrderListView, FilterView | OrderSO | Order_Overview page |
| Order Entry | OrderHeaderView, LineItemsView | OrderSO, OrderLineSO | Order_Edit page |
Step 3: Inventory Workflows

Document all workflows and their complexity:

markdown
| workflow Name | Tasks | Activities | Complexity | Mendix mapping |
|---------------|-------|------------|------------|----------------|
| Order Approval | 3 | 12 | Medium | microflow chain |
| New Employee Onboarding | 8 | 25 | High | workflow module |
| Leave request | 2 | 6 | Low | microflows only |
Step 4: Map Rules and Logic

Extract business rules from SmartForms rules and workflow logic:

markdown
| rule ID | Location | description | Mendix Implementation |
|---------|----------|-------------|----------------------|
| R-001 | CustomerView | Email format validation | validation microflow |
| R-002 | OrderWorkflow | Orders > $5000 need manager approval | decision in microflow |
| R-003 | LineItemsView | Auto-calculate line total | on-change nanoflow |

Migration Execution Order

Execute migration in this order to manage dependencies:

Phase 1: Domain Model
sql
-- 1. Enumerations first (no dependencies)
create enumeration CRM.OrderStatus (
  Pending 'Pending',
  Approved 'Approved',
  Rejected 'Rejected',
  Completed 'Completed'
);

-- 2. Entities (may reference enumerations)
create persistent entity CRM.Customer (...);
create persistent entity CRM.Order (...);

-- 3. Associations (reference entities)
create association CRM.Order_Customer from CRM.Order to CRM.Customer type reference;
Phase 2: Business Logic (Microflows)
sql
-- Core CRUD microflows
create microflow CRM.ACT_Customer_Save ($Customer: CRM.Customer)
begin
  -- Validation (from SmartForms rules)
  if $Customer/Email = empty then
    validation feedback $Customer/Email message 'Email is required';
    return false;
  end if;

  commit $Customer;
  return true;
end;

-- Workflow logic
create microflow CRM.ACT_Order_Submit ($Order: CRM.Order)
begin
  -- Workflow start logic
  ...
end;
Phase 3: Pages
sql
-- Overview pages
create page CRM.Customer_Overview (...);

-- Edit pages (can reference microflows from Phase 2)
create page CRM.Customer_Edit (...);
Phase 4: Security
sql
mdl 1;
-- Module roles matching K2 roles
create module role CRM.Manager description 'Can approve orders and manage customers';
create module role CRM.User description 'Can create and edit own records';

-- Access rules
grant create, delete, read *, write * on entity CRM.Order to CRM.Manager;
grant create, read *, write * on entity CRM.Order to CRM.User where [System.owner = '[%CurrentUser%]'];

Common Challenges and Solutions

Challenge 1: Server-Side Storage

Problem: K2 stores everything in a database, no single project file.

Solution: Use K2 Package (.kspx) export or K2 APIs to extract definitions. Work with K2 administrators to get comprehensive exports.

Challenge 2: SmartObject Connectors

Problem: SmartObjects may connect to external systems (SQL, SAP, SharePoint).

Solutions:

Connector TypeMendix Options
SQL DirectExternal Database Connector or data migration
SAPSAP BAPI Connector, OData, or REST
SharePointREST integration via Microsoft Graph API
Web ServiceREST/SOAP consumption
Challenge 3: Complex Rules

Problem: SmartForms rules are event-driven and can be deeply nested.

Solution: Map each rule to appropriate Mendix mechanism:

event-based UI logic → nanoflows
validation → validation microflows + validation feedback
data manipulation → microflows
Complex calculations → microflow expressions
Challenge 4: Workflow Participants

Problem: K2 uses destination rules for task assignment that may be complex.

Solution: Implement participant logic in microflows:

sql
mdl 1;
-- K2 Destination Rule "Route to Manager" → Mendix microflow
create microflow CRM.SUB_GetManager ($Employee: HR.Employee)
returns HR.Employee as $Manager
begin
  retrieve $Manager from HR.Employee
    where [HR.Employee_Reports = $Employee];
  return $Manager;
end;

Pre-Migration Checklist

Before starting migration:

  • Obtain K2 Package (.kspx) export for all artifacts
  • Get SmartObject documentation or extract via APIs
  • Document all SmartForms views and their rules
  • Map workflow steps and decision logic
  • Identify external system integrations (SQL, SAP, SharePoint)
  • Understand K2 security/role model
  • Plan for data migration (SmartBox data → Mendix entities)

During migration:

  • Create entities in dependency order
  • Create enumerations before entities that use them
  • Create microflows before pages that reference them
  • Test validation rules thoroughly
  • Verify workflow logic paths

After migration:

  • Run mxcli check script.mdl -p app.mpr --references
  • Open in Mendix Studio Pro to verify
  • Test all workflow scenarios
  • Validate data migration completeness

Investigation Tips

If you have access to K2:

  1. K2 Management Site: Export packages and view SmartObject schemas
  2. K2 Designer: View SmartForms rules in detail
  3. K2 Workspace: Examine workflow definitions
  4. SQL Server: Query K2 database for SmartBox data and metadata
  5. K2 API: Programmatically extract definitions for automation

If you have a .kspx file, it can potentially be parsed (it's a ZIP-based format) to extract XML definitions of the artifacts inside.

© 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-k2-nintex of mendixlabs/mxcli.

Open the folder on GitHubat commit 20a6c89

Compare with similar skills

Migrate K2 Nintex 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 K2 Nintex compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Migrate K2 Nintex this skillmendixlabs/mxcli128—~4.1kAutomated safety check: PassApache-2.0
Colleague DistillationZhixiangLuo/10xProductivity478—~2.1kAutomated safety check: NotesMIT
Msgraphcodemie-ai/codemie-code294—~4.1kAutomated safety check: PassApache-2.0
aai-cli Microsoft 365aai-labs/agent-barn109—~1.2kAutomated safety check: PassApache-2.0
Workiqmicrosoft/work-iq1k—~15kAutomated safety check: PassCustom licence
Analyze Document Librarypnp/sharepoint-skills131—~899Automated safety check: PassMIT

Similar skills

  • Colleague Distillation

    ZhixiangLuo/10xProductivity

    Distill a colleague into a reusable AI skill (work + persona) using tool connections — Slack, Slack AI, Jira, GHE, Bitbucket, Confluence, SharePoint, Teams, Outlook, Notion, Linear, Google Docs, and…

    478 GitHub stars~2.1k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Msgraph

    codemie-ai/codemie-code

    Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…

    294 GitHub stars~4.1k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • aai-cli Microsoft 365

    aai-labs/agent-barn

    Guides work with Outlook, OneDrive, SharePoint, Teams, Excel, To Do and Planner through aai-cli's Microsoft Graph commands, starting from which service owns the data.

    109 GitHub stars~1.2k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Workiq

    microsoft/work-iq

    Official

    WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.

    1k GitHub stars~15k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Analyze Document Library

    pnp/sharepoint-skills

    Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.

    131 GitHub stars~899 tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed
  • Broken Link Auditor

    pnp/sharepoint-skills

    Audits SharePoint pages, news posts, and hyperlink fields for broken or risky links and saves a self-contained HTML link-health report to the site.

    131 GitHub stars~2.5k tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed

More from mendixlabs/mxcli

All 72 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
  • Business Events

    mendixlabs/mxcli

    Define event-driven APIs over Kafka with Mendix business event services — publish and subscribe contracts, CREATE/DROP/DESCRIBE.

    128 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Catalog Search

    mendixlabs/mxcli

    Search the Mendix Catalog platform service registry (catalog.mendix.com) from the CLI to find services published across an organisation.

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

Questions about Migrate K2 Nintex

What does Migrate K2 Nintex do?

Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Migrate K2 Nintex is an agent skill from mendixlabs/mxcli. Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows.

When should I use Migrate K2 Nintex?

Migrate K2 Nintex fits situations like: converting a K2 application.

How do I install Migrate K2 Nintex in Claude Code?

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

How do I install Migrate K2 Nintex in Codex?

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

Can I use Migrate K2 Nintex 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-k2-nintex -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-k2-nintex, .gemini/skills/migrate-k2-nintex, .github/skills/migrate-k2-nintex and .opencode/skills/migrate-k2-nintex in your project.

What does Migrate K2 Nintex need to run?

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

Does Migrate K2 Nintex 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 K2 Nintex 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 K2 Nintex use?

Migrate K2 Nintex 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 K2 Nintex use?

About 4.1k tokens (SKILL.md is roughly 16k 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 K2 Nintex?

Skills that share tags, products or a category with Migrate K2 Nintex: Colleague Distillation (ZhixiangLuo/10xProductivity, 478 stars), Msgraph (codemie-ai/codemie-code, 294 stars), aai-cli Microsoft 365 (aai-labs/agent-barn, 109 stars) and Workiq (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Migrate K2 Nintex?

mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 72 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.