Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Build and start the Mendix app in Docker, and restart it after changes.
Install Run App
$ npx skills add mendixlabs/mxcli --skill run-app -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mendixlabs/mxcli run-app --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/run-app .claude/skills/run-app && rm -rf skills-srcUse ~/.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/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .claude/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-appType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mendixlabs/mxcli --skill run-app -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mendixlabs/mxcli run-app --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mendix/run-app .agents/skills/run-app && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .agents/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill run-app -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mendixlabs/mxcli run-app --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mendix/run-app .cursor/skills/run-app && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .cursor/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mendixlabs/mxcli.git --path .claude/skills/mendix/run-app--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mendixlabs/mxcli --skill run-app -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mendixlabs/mxcli run-app --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mendix/run-app .gemini/skills/run-app && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .gemini/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mendixlabs/mxcli run-appInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mendixlabs/mxcli --skill run-app -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mendix/run-app .github/skills/run-app && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .github/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill run-app -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mendixlabs/mxcli run-app --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mendix/run-app .opencode/skills/run-app && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-app" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/run-app into .opencode/skills/run-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-app", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-app- GitHub stars
- 128
- Token cost
- ~1.5k tokens
- SKILL.md length
- 479 words
- Files
- 1
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Build and start the Mendix app in Docker, and restart it after changes.
- Works in 2 steps: mxcli is local — always use ./mxcli, not… → Docker is available — check with docker ps
- Restart the app in a container
- SKILL.md covers When to Use This Skill, Prerequisites Check, Quick Start: One Command and After Making MDL Changes, plus 6 more sections
- Calls docker
What it does
Run App is an agent skill from mendixlabs/mxcli. Build and start the Mendix app in Docker, and restart it after changes. Use when asked to run, launch or restart the app in a container. For the fast inner loop prefer run-local.
Its SKILL.md is about 1.5k 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 DevOps & Cloud, covering Containers. It works with Docker. 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
- Restart the app in a container
- Tasks that involve Containers
Example prompts
- “/run-app”
Requirements
- Docker
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- mxcli is local — always use ./mxcli, not mxcli
- Docker is available — check with docker ps
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
Shell commands in SKILL.md call:
docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
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
Run App loads about 1.5k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 479 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:178
ng `docker init` and written to `.docker/.env`. Subsequent `docker run/up/reload` commands read from that `.env` automat
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). 479 words, ~1,476 tokens.
Download SKILL.mdSave it as
.claude/skills/run-app/SKILL.md (or your agent's skills folder).- name
- run-app
- description
- Build and start the Mendix app in Docker, and restart it after changes. Use when asked to run, launch or restart the app in a container. For the fast inner loop prefer run-local.
Run App Skill
This skill builds and starts the Mendix application in Docker.
When to Use This Skill
Use this when:
- The user asks to run, start, or launch the app
- The user asks to rebuild and restart after making changes
- The user wants to test their changes in a running environment
Prerequisites Check
Before running, verify:
- mxcli is local — always use
./mxcli, notmxcli - Docker is available — check with
docker ps
Everything else (MxBuild, runtime, Docker stack) is auto-downloaded/initialized by docker run.
In an agent session, prefer the Docker-free loop (skill run-local): it is
a background service you manage in one call per question — never with nohup,
sleep/grep/curl polling loops, or pkill:
./mxcli run --local --watch --detach -p app.mpr # returns once it serves
./mxcli exec change.mdl -p app.mpr && ./mxcli run wait -p app.mpr # applied / failed
./mxcli run status -p app.mpr # one line
./mxcli run stop -p app.mpr # nothing left behindUse the Docker path below when you need container parity.
Quick Start: One Command
# Setup, build, and start — handles everything automatically
./mxcli docker run -p MxCliDemoApp2.mpr --waitThis single command:
- Downloads MxBuild (if not cached)
- Downloads the Mendix runtime (if not cached)
- Initializes the Docker stack (if not already done)
- Builds the PAD package
- Starts the containers in the background
- Waits for "Runtime successfully started" (with
--wait)
The app is available at: http://localhost:8080
Admin console: http://localhost:8090 (password: AdminPassword1!)
After Making MDL Changes
Model/page/security changes (microflows, entities, pages, navigation):
# 1. apply MDL changes to the project
./mxcli exec changes.mdl -p MxCliDemoApp2.mpr
# 2. Rebuild and hot reload (no restart, keeps database)
./mxcli docker build -p MxCliDemoApp2.mpr --skip-check
./mxcli docker reload -p MxCliDemoApp2.mprUse docker reload for most changes — it reloads the model in ~100ms without restarting.
Use docker run --fresh only when schema changes are destructive (dropped entities/attributes):
./mxcli docker run -p MxCliDemoApp2.mpr --fresh --waitCSS/theme changes only (no rebuild needed):
# Instant CSS hot reload — pushes to all connected browsers
./mxcli docker reload -p MxCliDemoApp2.mpr --cssOr simply hard-refresh the browser (Cmd+Shift+R / Ctrl+Shift+R) — the volume mount means compiled CSS is immediately available on disk after mxcli docker build.
Step-by-Step Alternative
If you prefer more control over individual steps:
# First-time setup (cached, run once per devcontainer)
./mxcli setup mxbuild -p MxCliDemoApp2.mpr
./mxcli setup mxruntime -p MxCliDemoApp2.mpr
./mxcli docker init -p MxCliDemoApp2.mpr
# build and start
./mxcli docker build -p MxCliDemoApp2.mpr
./mxcli docker up -p MxCliDemoApp2.mpr --detach --waitQuery Data (OQL)
Once the app is running, test OQL queries against the live runtime:
# run OQL queries (read-only preview mode)
./mxcli oql -p MxCliDemoApp2.mpr "select Name from MyModule.Customer"
# json output for piping
./mxcli oql -p MxCliDemoApp2.mpr --json "SELECT count(c.ID) FROM MyModule.Order AS c"Existing projects: If you get "Action not found: preview_execute_oql", re-initialize the Docker stack to pick up the required JVM flag:
./mxcli docker init -p MxCliDemoApp2.mpr --force
Show full SKILL.md (178 more words)Show less
Monitoring
# view live logs
./mxcli docker logs -p MxCliDemoApp2.mpr --follow
# view last 50 lines
./mxcli docker logs -p MxCliDemoApp2.mpr --tail 50
# open a shell in the Mendix container
./mxcli docker shell -p MxCliDemoApp2.mprLook for this line to confirm successful startup:
Mendix runtime successfully started, the application is now available.Stop
# Stop containers (keeps database data)
./mxcli docker down -p MxCliDemoApp2.mpr
# Stop and wipe database
./mxcli docker down -p MxCliDemoApp2.mpr --volumesRunning Multiple Projects
When running multiple Mendix apps simultaneously, each project needs unique ports. Use --port-offset to shift all ports:
# First project (default ports: 8080/8090/5432)
./mxcli docker run -p project1/app.mpr --wait
# Second project (ports: 8081/8091/5433)
./mxcli docker init -p project2/app.mpr --port-offset 1
./mxcli docker run -p project2/app.mpr --wait| Offset | App | Admin | DB |
|---|---|---|---|
| 0 | 8080 | 8090 | 5432 |
| 1 | 8081 | 8091 | 5433 |
| 2 | 8082 | 8092 | 5434 |
The offset is applied once during docker init and written to .docker/.env. Subsequent docker run/up/reload commands read from that .env automatically.
Note: If the Docker stack was already initialized, re-run init with
--force:./mxcli docker init -p app.mpr --port-offset 1 --force
Architecture Note
The containers run inside a Docker-in-Docker daemon inside the devcontainer — they are not visible in Docker Desktop on the host. Port forwarding (8080, 8090) is handled by VS Code automatically.
The build output (.docker/build/) is volume-mounted into the container — no Docker image rebuild needed. After mxcli docker build:
- CSS/theme changes: Hard-refresh the browser — files are already on disk via the mount
- Model changes: Run
mxcli docker reload— hot reloads the model in ~100ms, no restart needed - Destructive schema changes: Restart with
mxcli docker up --freshto recreate the database
© 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/run-app of mendixlabs/mxcli.
Open the folder on GitHubat commit a924d11
Compare with similar skills
Run App 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run App this skillmendixlabs/mxcli | 128 | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 15k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
Omnigent Docker Compose Deploy
omnigent-ai/omnigent
Brings up the Omnigent server and Postgres as a Docker compose stack on any Docker host, and covers the Dockerfile's runtime and host build targets for extending it to a new platform.
More from mendixlabs/mxcli
All 75 skills in this repoMendix 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…
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.
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.
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.
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.
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.
Related
Works with
Categories
Questions about Run App
What does Run App do?
Build and start the Mendix app in Docker, and restart it after changes. Run App is an agent skill from mendixlabs/mxcli. Build and start the Mendix app in Docker, and restart it after changes.
When should I use Run App?
Run App fits situations like: restart the app in a container; tasks that involve Containers.
How do I install Run App in Claude Code?
Run `npx skills add mendixlabs/mxcli --skill run-app -a claude-code`. Or copy the skill folder (.claude/skills/mendix/run-app in mendixlabs/mxcli) into .claude/skills/run-app in your project. Claude Code loads it when a task matches its description.
How do I install Run App in Codex?
Run `npx skills add mendixlabs/mxcli --skill run-app -a codex`. Or copy the skill folder (.claude/skills/mendix/run-app in mendixlabs/mxcli) into .agents/skills/run-app in your project. Codex loads it when a task matches its description.
Can I use Run App 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 run-app -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-app, .gemini/skills/run-app, .github/skills/run-app and .opencode/skills/run-app in your project.
What does Run App need to run?
Going by SKILL.md and its folder, Run App needs the command-line tools its instructions call (docker). Our summary lists: Docker.
Does Run App access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Run App safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Run App use?
Run App 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 Run App use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Run App?
Skills that share tags, products or a category with Run App: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run App?
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.