CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An exemplar reference skill: dense and domain-specific with no padding, concrete runnable commands and named concepts, a numbered workflow with explicit cheap-first and full-build validation checkpoints, and a well-organized one-level-deep reference index where every cited file exists. Among the strongest possible scores across all four content dimensions.

DimensionReasoningScore

Conciseness

Lean throughout: no generic PDF-style primers or concept explanations Claude already knows; every line is domain-specific (generated-Ant directives, Ivy fetch mechanics, missing-macro warnings). The at-a-glance diagram is dense and informative rather than padded.

3 / 3

Actionability

Concrete and executable throughout — explicit grep commands ('grep -r <plugin-name> build/'), runnable targets ('ant -f build/<projectName>.xml assemble', 'ant -f build/build.xml platform'), exact artefact paths, and named BuildProject/BuildLayout concepts to author. Step 3 names the precise concepts and markers (BuildJavaPlugin, BuildSource_JavaDependencyModule).

3 / 3

Workflow Clarity

The Common-Path Workflow is an explicit 8-step numbered sequence with validation built in: cheap-first directive (Critical Directives), an isolated smoke step (step 6) before the full build (step 7), and explicit verify-three-artefact-locations feedback via references/validation.md. Not a level above (no scale beyond 3); not a 2 because checkpoints are explicit rather than implied.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with a Reference Index pointing one level deep to 9 distinct, clearly-signaled references (all verified to exist), each prefaced with exactly when to open it. No deep nesting; content is appropriately split and easy to navigate. Scoring against the actual bundle structure confirms all referenced paths resolve to real files.

3 / 3

Total

12

/

12

Passed

Description

100%

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 high-quality description: third person, concrete actions, explicit 'Use when' trigger, and a clearly bounded MPS distribution-build niche with low conflict risk. It is long but every clause is substantive rather than padded fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions: 'bundling a new plain Java/Kotlin plugin', 'debugging packaging/layout issues in build/mps*.xml', 'tracing where per-plugin artefacts end up', and 'editing build.mps', plus coverage of three pipeline layers.

3 / 3

Completeness

Opens with an explicit 'Use when ...' clause listing four triggering situations (clear 'when'), and the rest of the sentence states precisely what the skill covers (clear 'what'), satisfying both halves.

3 / 3

Trigger Term Quality

Uses natural trigger phrasing a user would say ('bundling', 'debugging packaging/layout issues', 'tracing where artefacts end up') and surfaces concrete file/path tokens like build/mps*.xml and build.mps that a user debugging would mention.

3 / 3

Distinctiveness Conflict Risk

Scoped to MPS distribution-build packaging artefacts and the build.mps source of truth, a distinct niche unlikely to fire for adjacent concerns; the body further carves it apart from sibling skills (mps-build-language, mps-tests).

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
JetBrains/MPS
Reviewed

Table of Contents

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.