CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-build-language

Use when authoring or modifying MPS Build Language scripts (`BuildProject` roots) — the declarative DSL that generates Ant `build.xml` to package MPS language plugins, IDEA plugins, plain Java modules, standalone IDE/RCP distributions, module tests, or `run code from solution` tasks. Covers build solution setup, macros, project/external/Java dependencies, MPS module declarations (`BuildMps_Language` / `_Solution` / `_Generator`), groups, layouts, IDEA-plugin declarations, MPS settings, and the workflow language. Trigger terms: `BuildProject`, `BuildMps_*`, `BuildLayout_*`, `jetbrains.mps.build`, `build.mps` solution, `internalBaseDirectory`, `compactBuildScriptFileName`, Ant target generation, `mps_home`, `idea_home`.

75

Quality

94%

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

88%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, concise, and highly actionable reference skill body with a clear multi-step workflow and excellent progressive-disclosure signaling. Its main weakness is that the many references/*.md files it points to are absent from the bundle, breaking the navigation it advertises.

Suggestions

Ship the referenced bundle files (references/solution-setup.md, buildproject-skeleton.md, plugins-and-macros.md, etc.); the body depends on them for skeletons and detailed guidance but none exist in the bundle.

Inline at least one minimal copy-paste BuildProject JSON skeleton in the body so the core workflow is executable even before opening references/buildproject-skeleton.md.

Add an explicit validate->fix->retry checkpoint in the Common-Path Workflow (e.g. after Make, verify build.xml was written and re-run Load required information on .mpl/.msd changes) rather than deferring all failure handling to references/common-failures.md.

DimensionReasoningScore

Conciseness

The body is dense and high-signal, assuming Claude's domain competence without explaining what MPS or Ant are; every directive and step carries actionable information with no padding.

5 / 5

Actionability

The 10-step workflow is concrete with exact concept/role names, menu paths (Ctrl-F9, right-click -> Run), and an `ant -Dmps_home=...` command, but the copy-paste JSON skeletons it points to live in reference files that are not present in the bundle, leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced 10-step Common-Path Workflow with implicit checkpoints via the Critical Directives (e.g. 'generate languages first', 're-run Load required information'), but explicit validate->fix->retry feedback loops are deferred to references/common-failures.md rather than inlined.

4 / 5

Progressive Disclosure

Excellent structure and one-level-deep signaling via a detailed Reference Index mapping each task to a specific references/*.md file, but per the rubric's bundle-structure rule this is penalized because none of the ~15 referenced files actually exist in the bundle.

4 / 5

Total

17

/

20

Passed

Description

100%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, highly specific description that explicitly covers both what the skill does and when to use it, with comprehensive natural and technical trigger terms. Third-person voice is maintained throughout with no over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('package MPS language plugins, IDEA plugins, plain Java modules, standalone IDE/RCP distributions, module tests, or run code from solution tasks') plus a detailed 'Covers...' enumeration of concrete artifacts, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (declarative DSL that generates Ant build.xml to package...) and 'when' ('Use when authoring or modifying MPS Build Language scripts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive trigger list including the exact identifiers a user in this domain would cite: BuildProject, BuildMps_*, BuildLayout_*, jetbrains.mps.build, internalBaseDirectory, compactBuildScriptFileName, mps_home, idea_home.

5 / 5

Distinctiveness Conflict Risk

Highly niche domain (MPS Build Language) with concept-specific identifiers and UUIDs, giving a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 28 missing

Warning

Total

14

/

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.