Official agent skill

Mps Distribution Build

OfficialApache-2.0Auto-check passedMobile

Install Mps Distribution Build

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a claude-code

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

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build --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/JetBrains/MPS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/mps-distribution-build .claude/skills/mps-distribution-build && 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/

Paste into Claude Code

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .claude/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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

$skill-installer install https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build

Type 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.

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/mps-distribution-build .agents/skills/mps-distribution-build && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .agents/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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.

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/mps-distribution-build .cursor/skills/mps-distribution-build && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .cursor/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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

$ gemini skills install https://github.com/JetBrains/MPS.git --path .agents/skills/mps-distribution-build

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/mps-distribution-build .gemini/skills/mps-distribution-build && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .gemini/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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.

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build

Installs 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).

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/mps-distribution-build .github/skills/mps-distribution-build && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .github/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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.

skills CLI

$ npx skills add JetBrains/MPS --skill mps-distribution-build -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS mps-distribution-build --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/mps-distribution-build .opencode/skills/mps-distribution-build && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mps-distribution-build" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/mps-distribution-build into .opencode/skills/mps-distribution-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mps-distribution-build", 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: mps-distribution-build
GitHub stars: 1.7k
Token cost: ~2.4k tokens
SKILL.md length: 924 words
Files: 10 (incl. references)
Skills in repo: 41
Repo updated: Oct 9, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Works in 8 steps: Diagnose where the plugin currently is.… → Pick a shape. Model it like… → Author in build.mps. Add a BuildProject… → …
Bundling a new plain Java/Kotlin plugin into MPS distribution archives
SKILL.md covers Loading companion skills, Critical Directives, Common-Path Workflow — Bundle… and Pipeline at a Glance, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mps Distribution Build is an agent skill from JetBrains/MPS, published by the product's own GitHub organization. Use when bundling a new plain Java/Kotlin plugin into MPS distribution archives, debugging packaging/layout issues in build/mps.xml, tracing where per-plugin artefacts end up, or editing plugins/mps-build/solutions/mpsBuild/models/build.mps (the source of truth that generates every build/mps.xml). The skill covers the generated Ant pipeline, plugin-to-distribution wiring, and the per-plugin / aggregator / distribution layers.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/architecture.md`, `references/build-mps-authoring.md` and `references/build-mps-source-of-truth.md`).

It sits in Mobile, covering Android development. It works with Kotlin and Java. The repository describes itself as: JetBrains Meta programming System. The licence is Apache-2.0.

When your agent uses it

Bundling a new plain Java/Kotlin plugin into MPS distribution archives
Debugging packaging/layout issues in build/mps.xml
Tracing where per-plugin artefacts end up
Editing plugins/mps-build/solutions/mpsBuild/models/build.mps (the source of truth that generates every build/mps.xml)

Example prompts

“/mps-distribution-build”

Workflow steps

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

Diagnose where the plugin currently is. grep -r build/ (empty → no generated Ant script). Look under build/artifacts//…
Pick a shape. Model it like mpsHttpSupportPlugin (Option A, preferred — full Ant compile pipeline) or like mcpserver / terminal (Option B…
Author in build.mps. Add a BuildProject with the right BuildLayout (Java/Kotlin source roots, META-INF/plugin.xml, jar packaging…
Wire it into the aggregator. Edit the mps aggregator BuildProject so it imports ${artifacts.}, copies ${artifacts.}/ into…
Regenerate build.mps. A new build/.xml will appear; build/mps.xml and build/mpsDistribution.xml will be updated by the same regeneration.
Smoke step (no full build). Run ant -f build/.xml assemble in isolation. Pre-run ant -f build/build.xml platform once so the IDEA jars…
Full build via build/run_build.sh. Verify the three artefact locations in references/validation.md.
If the plugin has a test/ source root, add a sibling test-only BuildProject (Tests) — see references/test-suite-wiring.md.

What it can do on your machine

Read from SKILL.md and the folder at commit 3e9cfcd. 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.
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

Mps Distribution Build loads about 2.4k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 924 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~115
When it runs · the whole SKILL.md, loaded when a task matches: ~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~7.9k

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 JetBrains/MPS at commit 3e9cfcd, republished under its Apache-2.0 licence (© JetBrains). 924 words, ~2,364 tokens.

Download SKILL.mdSave it as .claude/skills/mps-distribution-build/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.

name: mps-distribution-build
description: Use when bundling a new plain Java/Kotlin plugin into MPS distribution archives, debugging packaging/layout issues in `build/mps*.xml`, tracing where per-plugin artefacts end up, or editing `plugins/mps-build/solutions/mpsBuild/models/build.mps` (the source of truth that generates every `build/mps*.xml`). The skill covers the generated Ant pipeline, plugin-to-distribution wiring, and the per-plugin / aggregator / distribution layers.
type: reference

MPS Distribution Build — Ant Pipeline & Plugin Bundling

Loading companion skills

Companion names in this skill are lazy dependencies: load only those relevant to the current task. If this skill came from an MCP server, use the host's skill loader to resolve the companion's unique discovered entry URI on the same host-assigned originating server. If the host has no server-backed skill loader, stop and report that limitation; do not silently fall back to a filesystem copy. If this skill came from a filesystem catalog, load the named sibling from that same catalog at <skills-root>/<skill-name>/SKILL.md, even if remote skill loaders are also available. Do not invent a tool name or server endpoint.

This skill explains how the generated Ant scripts under build/mps*.xml assemble MPS distribution archives, and how to add a new plain Java/Kotlin plugin module (e.g. plugins/mcp-tools) so it ends up in the produced archives. Authoring the model that generates these Ant scripts is covered separately by mps-build-language — this skill focuses on the output side and the plugin-bundling touchpoints.

Critical Directives

The Ant files are generated. All build/mps*.xml files carry . Do not hand-edit them as a permanent solution — author the change in plugins/mps-build/solutions/mpsBuild/models/build.mps and regenerate.
A new per-plugin BuildProject is invisible to the distribution until it is also wired into the mps aggregator BuildProject and mpsDistribution. A plugin can build into build/artifacts/<projectName>/ but never enter the final zip if mps.xml is not updated.
IDEA platform jars under <MPS>/lib/ and <MPS>/plugins/<idea-plugin>/lib/ are fetched by build.xml platform (Ivy via getDependencies.xml). They do not exist on a clean checkout, and no BuildProject declares the fetch. Every per-plugin script implicitly requires ant -f build/build.xml platform to have already run.
There is no ${idea.plugins.dir} macro — do not invent one. Reference fetched IDEA-plugin jars via ${basedir}/plugins/<idea-plugin>/lib/ (matches the IDEA project libraries under .idea/libraries/*.xml).
The test/ source root is not part of the production jar. Test compilation belongs in a sibling test-only BuildProject (cf. mpsTesting.xml), not layered onto the production jar.
Validate cheap first: regenerate, then run ant -f build/<projectName>.xml assemble in isolation before running the full build/run_build.sh.

Common-Path Workflow — Bundle a New Plain Java/Kotlin Plugin

Running example: bundling plugins/mcp-tools (a JAVA_MODULE with Kotlin sources, depending on com.intellij.mcpServer).

Diagnose where the plugin currently is. grep -r <plugin-name> build/ (empty → no generated Ant script). Look under build/artifacts/<projectName>/, build/artifacts/mps/plugins/<x>/, and the final ${build.number}*.zip to find which layer is missing it. See references/diagnostics.md.
Pick a shape. Model it like mpsHttpSupportPlugin (Option A, preferred — full Ant compile pipeline) or like mcpserver / terminal (Option B — pre-built, copied from <MPS>/plugins/<x>/ by mpsStandalone). See references/plugin-bundling-options.md.
Author in build.mps. Add a BuildProject <projectName> with the right BuildLayout (Java/Kotlin source roots, META-INF/plugin.xml, jar packaging, dependencies via BuildSource_JavaDependencyModule / …ExternalJar). Carry the BuildJavaPlugin marker so the generator emits a plain compile pipeline. Depend on mpsBootstrapCore (and likely mpsCore / mpsWorkbench). See references/build-mps-authoring.md.
Wire it into the aggregator. Edit the mps aggregator BuildProject so it imports ${artifacts.<projectName>}, copies ${artifacts.<projectName>}/<plugin-folder> into ${build.layout}/plugins/<plugin-folder>, and invokes the new Ant file in its buildDependents. Add the same <ant antfile="build/<projectName>.xml" …/> line to mpsDistribution.xml's buildDependents.
Regenerate build.mps. A new build/<projectName>.xml will appear; build/mps.xml and build/mpsDistribution.xml will be updated by the same regeneration.
Smoke step (no full build). Run ant -f build/<projectName>.xml assemble in isolation. Pre-run ant -f build/build.xml platform once so the IDEA jars exist on disk.
Full build via build/run_build.sh. Verify the three artefact locations in references/validation.md.
If the plugin has a test/ source root, add a sibling test-only BuildProject (<projectName>Tests) — see references/test-suite-wiring.md.

Show full SKILL.md (349 more words)Show less

Pipeline at a Glance

build.xml                              build.txt              dependencies.properties
   │                                       │                          │
   ├─ platform              ───────────► Ivy fetches IDEA + libs into <MPS>/lib, <MPS>/plugins/*
   │   (getDependencies.xml)
   │
   ├─ getResourcesAndBuildAll
   │     └─ mpsDistribution.xml buildDependents
   │            ├─ mpsTrueBootstrap.xml  ──┐
   │            ├─ mpsBootstrapCore.xml    │  per-plugin Ant scripts
   │            ├─ mpsCore.xml             │  (compile + jar + layout into
   │            ├─ mpsWorkbench.xml        │   build/artifacts/<projectName>/)
   │            ├─ mpsBuild.xml            │
   │            ├─ mpsTesting.xml          │
   │            ├─ mpsPlugins.xml          │
   │            ├─ mpsJava.xml             │
   │            ├─ mpsHttpSupportPlugin.xml│
   │            ├─ mpsKotlinPlugin.xml     │
   │            ├─ mpsContextActionsTool.xml│
   │            ├─ … (30+ files)          ─┘
   │            └─ mps.xml                 (aggregates into build/artifacts/mps/)
   │
   └─ assemble
         └─ mpsDistribution.xml assemble   (zips/tars into build/artifacts/mpsDistribution/)

mps-build-language — when you are authoring or editing the build language model itself, not just consuming its output.
mps-tests — when the plugin you are bundling has a JUnit / MPS test suite that must run in CI.
mps-ide-plugin — when the new module is an MPS IDE plugin (plugin.xml, actions, tool windows). Bundling and IDE-plugin authoring are independent steps.
mps-aspect-generator — when the failure is in MPS generation rather than packaging.

Reference Index

Open references/architecture.md for the long form of "how Ant files compose" — entry point build/build.xml targets, the three layers of generated scripts (mpsTrueBootstrap.xml/mpsBootstrapCore.xml/per-plugin files; mps.xml aggregator; mpsStandalone.xml), and the final distribution layer mpsDistribution.xml with its per-platform archives. Open when you need to know where a particular file lives in the pipeline or what its buildDependents does.
Open references/build-mps-source-of-truth.md when editing plugins/mps-build/solutions/mpsBuild/models/build.mps — explains the BuildProject structure, the meaning of opaque concept indices (1l3spW, 398b33, TrG5h, turDy, 2DA0ip, 1l3spV, 10PD9b), and how regeneration writes the build/*.xml files.
Open references/plugin-bundling-options.md to choose between Option A (full Ant compile pipeline like mpsHttpSupportPlugin) and Option B (pre-built drop into mpsStandalone). Includes the rationale for picking Option A for new MPS-authored plugins.
Open references/build-mps-authoring.md when adding the new BuildProject to build.mps — BuildLayout shape, BuildSource_JavaModule / BuildSource_JavaContentRoot, the BuildJavaPlugin marker, dependency chain through mpsBootstrapCore, and the convention for referencing fetched IDEA-plugin jars via ${basedir}/plugins/<idea-plugin>/lib/.
Open references/diagnostics.md when a plugin is missing from the distribution and you need to figure out which layer dropped it — three-step diagnosis using grep, build/artifacts/<projectName>/, and build/artifacts/mps/plugins/<x>/.
Open references/validation.md for the two-stage validation procedure (cheap ant -f build/<projectName>.xml assemble smoke step, then full build/run_build.sh) and the three artefact locations to verify after a full build.
Open references/touchpoint-checklist.md for the table of files modified by adding a new Option A plugin — what is hand-edited (build.mps), what is regenerated (build/<projectName>.xml, build/mps.xml, build/mpsDistribution.xml), and what stays unchanged (plugins/<plugin>/META-INF/plugin.xml, .iml).
Open references/test-suite-wiring.md when the new plugin has a test/ source root that must run in CI — sibling test-only BuildProject, JUnit launcher, and …Tests.xml aggregator wiring.
Open references/key-files.md for the quick reference of every build file mentioned anywhere in this skill, with one-line descriptions.

Files

SKILL.md and 9 other files (references) in .agents/skills/mps-distribution-build of JetBrains/MPS.

SKILL.md
references/architecture.md
references/build-mps-authoring.md
references/build-mps-source-of-truth.md
references/diagnostics.md
references/key-files.md
references/plugin-bundling-options.md
references/test-suite-wiring.md
references/touchpoint-checklist.md
references/validation.md

Open the folder on GitHubat commit 3e9cfcd

Compare with similar skills

Mps Distribution Build 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.

Mps Distribution Build compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Mps Distribution Build this skillJetBrains/MPS	1.7k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Build Teaql Appteaql/teaql-agent-kit	2.8k	—	~4.6k	Automated safety check: Pass	MIT	13 days ago
Find Untested Sourcesmicrosoft/testfx	1k	2 repos	~3.3k	Automated safety check: Pass	MIT	today
Android Maps Ktxgooglemaps/android-maps-ktx	360	—	~897	Automated safety check: Pass	Apache-2.0	2 days ago
Code StyleJetBrains/intellij-community	21k	—	~795	Automated safety check: Pass	Custom licence	today
Jugg Android Dev Loopniki914/zafiro	235	—	~2k	Automated safety check: Pass	MIT	today

Similar skills

Build Teaql App
teaql/teaql-agent-kit
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.
2.8k GitHub stars~4.6k tokensUpdated 13 days ago
MobileAuto-check passed
Find Untested Sources
microsoft/testfx
Official
MANDATORY for static source-to-test pairing: find or list source files/modules without corresponding tests, or suggest test locations from repository structure.
1k GitHub starsUsed in 2 repos~3.3k tokens
MobileAuto-check passed
Android Maps Ktx
googlemaps/android-maps-ktx
Provides idiomatic Kotlin extension (KTX) patterns, reactive Flow event streams, and multi-subscriber shareIn rules for Google Maps SDK for Android and its Utility Library.
360 GitHub stars~897 tokensUpdated 2 days ago
MobileAuto-check passed
Code Style
JetBrains/intellij-community
Official
Apply IntelliJ Kotlin and Java code style when writing or reviewing.
21k GitHub stars~795 tokensUpdated today
MobileAuto-check passed
Jugg Android Dev Loop
niki914/zafiro
A skill your agent uses when editing source files (Java/Kotlin/XML/layout/AndroidManifest/Gradle) in a Android project, or when user asks to build/deploy/verify an Android app.
235 GitHub stars~2k tokensUpdated today
MobileAuto-check passed
Android Audio E2E
hyochan/react-native-nitro-sound
Build and run device-backed Android end-to-end checks for react-native-nitro-sound permissions, recording, playback, listeners, pause/resume, seek, speed, audio focus, lifecycle behavior, and rapid…
961 GitHub stars~814 tokensUpdated 10 days ago
MobileAuto-check passed

More from JetBrains/MPS

All 41 skills in this repo

Mps Language Analysis
JetBrains/MPS
Official
Analyze an MPS language by name — discover concepts, properties, references, children, aspects (editor/constraints/behavior), metadata, and answer type questions (is A a subtype of B, common…
1.7k GitHub stars~1.8k tokensUpdated today
Auto-check passed
Mps Node Editing
JetBrains/MPS
Official
Add, update, or delete MPS nodes using JSON blueprints — covers the unified blueprint format, staged construction for large subtrees, validation, and reference repair.
1.7k GitHub stars~5.1k tokensUpdated today
Auto-check passed
Mps Project Management
JetBrains/MPS
Official
Open an MPS project in a running or freshly started MPS instance when MCP tools fail because no project is open (welcome screen), close an open project with mpsmcpcloseproject, or create a new empty…
1.7k GitHub stars~2.2k tokensUpdated today
Auto-check passed
Mps MCP Workflow
JetBrains/MPS
Official
Complete JetBrains MPS workflow guide for DSL projects — models, languages, generators, node JSON blueprints, type queries, validation, MPS MCP tool usage, and the index of companion skills.
1.7k GitHub stars~6.6k tokensUpdated today
Auto-check passed
Bugfix Workflow
JetBrains/MPS
Official
Structured MPS bugfix workflow driven by a YouTrack issue ID — preflight tool checks, version/branch derivation, parallel-agent problem analysis, solution design, branch creation, implementation…
1.7k GitHub stars~4.4k tokensUpdated today
Auto-check passed
Mps Aspect Structure Concepts
JetBrains/MPS
Official
Define concepts, interface concepts, enumerations, and constrained data types in an MPS language's structure aspect.
1.7k GitHub stars~2.8k tokensUpdated today
Auto-check passed

Works with

Questions about Mps Distribution Build

What does Mps Distribution Build do?

A skill your agent uses when bundling a new plain Java/Kotlin plugin into MPS distribution archives, debugging packaging/layout issues in build/mps.xml, tracing where per-plugin artefacts end up, or…. Mps Distribution Build is an agent skill from JetBrains/MPS, published by the product's own GitHub organization.xml).

When should I use Mps Distribution Build?

Mps Distribution Build fits situations like: bundling a new plain Java/Kotlin plugin into MPS distribution archives; debugging packaging/layout issues in build/mps.xml; tracing where per-plugin artefacts end up; editing plugins/mps-build/solutions/mpsBuild/models/build.mps (the source of truth that generates every build/mps.xml).

How do I install Mps Distribution Build in Claude Code?

Run `npx skills add JetBrains/MPS --skill mps-distribution-build -a claude-code`. Or copy the skill folder (.agents/skills/mps-distribution-build in JetBrains/MPS) into .claude/skills/mps-distribution-build in your project. Claude Code loads it when a task matches its description.

How do I install Mps Distribution Build in Codex?

Run `npx skills add JetBrains/MPS --skill mps-distribution-build -a codex`. Or copy the skill folder (.agents/skills/mps-distribution-build in JetBrains/MPS) into .agents/skills/mps-distribution-build in your project. Codex loads it when a task matches its description.

Can I use Mps Distribution Build 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 JetBrains/MPS --skill mps-distribution-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mps-distribution-build, .gemini/skills/mps-distribution-build, .github/skills/mps-distribution-build and .opencode/skills/mps-distribution-build in your project.

What does Mps Distribution Build need to run?

SKILL.md names no scripts, command-line tools or credentials: Mps Distribution Build is instructions for the agent only.

Does Mps Distribution Build 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 Mps Distribution Build 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 Mps Distribution Build use?

Mps Distribution Build 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 Mps Distribution Build use?

About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.

What are the alternatives to Mps Distribution Build?

Skills that share tags, products or a category with Mps Distribution Build: Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), Find Untested Sources (microsoft/testfx, 1k stars), Android Maps Ktx (googlemaps/android-maps-ktx, 360 stars) and Code Style (JetBrains/intellij-community, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mps Distribution Build?

JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/MPS, which has 1,661 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.

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

Install Mps Distribution Build

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MPS Distribution Build — Ant Pipeline & Plugin Bundling

Loading companion skills

Critical Directives

Common-Path Workflow — Bundle a New Plain Java/Kotlin Plugin

Pipeline at a Glance

Related Skills

Reference Index

Files

Compare with similar skills

Similar skills

More from JetBrains/MPS

Related

Questions about Mps Distribution Build