mps-distribution-build

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured reference skill: tight directives, a sequenced workflow with built-in cheap validation, and excellent progressive disclosure via a one-level reference index. Actionability and inline error-recovery detail are slightly limited by deferring granular authoring to the reference files.

Suggestions

Add a one-line inline error-recovery hint to the smoke step (e.g. 'if `assemble` fails, check that `ant -f build/build.xml platform` has run and that the new BuildProject is wired into the `mps` aggregator') so the feedback loop does not require opening references/validation.md.

Tighten the Reference Index by collapsing each entry to a single 'Open <file> when <trigger>' sentence to reduce redundancy with the workflow steps that already cite the same files.

Include a minimal inline build.mps authoring skeleton (BuildProject/BuildLayout/BuildJavaPlugin shape) so the core action is copy-paste ready without opening references/build-mps-authoring.md.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no Ant/jar primers), but the Reference Index entries and some overlap between workflow-step pointers and the index leave minor instances that could be trimmed.	4 / 5
Actionability	Provides concrete, runnable commands (`grep -r <plugin-name> build/`, `ant -f build/<projectName>.xml assemble`, `build/run_build.sh`) with a running example, but defers granular build.mps authoring detail to references, leaving minor gaps in the body itself.	4 / 5
Workflow Clarity	A clear 8-step sequence with an explicit cheap smoke-step validation before the full build satisfies the batch-operation validation requirement; the detailed error-recovery feedback loop is deferred to references/validation.md rather than stated inline.	4 / 5
Progressive Disclosure	A clear overview with a well-signaled, one-level-deep Reference Index (each entry an 'Open ... when ...' pointer) and content appropriately split between body and reference files, making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely states both capabilities and trigger conditions for a well-scoped technical niche. The only soft spot is trigger-term synonym coverage, which is good but not exhaustive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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`' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' ('covers the generated Ant pipeline, plugin-to-distribution wiring, and the per-plugin / aggregator / distribution layers') and 'when' (a 'Use when...' clause with four concrete trigger scenarios).	5 / 5
Trigger Term Quality	Good keyword coverage across several 'Use when...' triggers with file references (`build/mps*.xml`, `build.mps`), but few synonyms for the core concepts keep it just below the comprehensive-synonym bar of a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (MPS distribution build / plugin bundling) with file-specific triggers unlikely to fire for unrelated skills, so conflict risk is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 14 missing	Warning

	Total	14 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-distribution-build/SKILL.md
Commit: c74b207

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.