CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-run-configurations

Create and execute IDE run configurations for MPS root nodes via MPS MCP — Java Application for `IMainClass` / `ClassConcept` with `main`, JUnit Tests for `ITestCase`. Use when launching DSL `main`-like roots, plain BaseLanguage `ClassConcept` mains, or MPS test cases from a node; reusing or replacing an existing run config; diagnosing `ClassNotFoundException`, `compileInMPS=false`, or "not runnable through this tool" failures.

70

Quality

87%

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

82%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 dense, token-efficient reference skill with concrete tool calls, a sequenced workflow with error recovery, and a well-signaled reference index. Main gap: the six referenced `references/*.md` files are absent from the bundle, so the progressive-disclosure navigation cannot be verified.

Suggestions

Ship the six referenced files under `references/` (runnable-shapes, create-and-execute, classconcept-and-fallbacks, compile-before-run, decision-matrix, common-failures) so the Reference Index links resolve.

Add one or two more error-recovery branches to the Common Workflow (e.g. non-root rejection, `compileInMPS=false` refusal) to widen the validation/feedback coverage.

Inline a minimal full call shape for `mps_mcp_create_run_configuration` (key params) so the skill is actionable without opening a reference.

DimensionReasoningScore

Conciseness

Lean ~40-line body that assumes Claude knows MPS; no padding explaining what MPS/generators are, and every directive and reference entry earns its place.

5 / 5

Actionability

Names concrete MCP tools and parameters (`mps_mcp_alter_nodes MAKE` with `rebuild: true`, `execute_run_configuration` with `waitForExit: true`, stable `configurationName`), but full call signatures are deferred to references, leaving minor gaps.

4 / 5

Workflow Clarity

The Common Workflow is a clear 4-step sequence with one explicit error-recovery feedback loop (step 4 on 'Could not find or load main class'); additional checkpoint/branch coverage would push it higher.

4 / 5

Progressive Disclosure

Well-structured overview with a dedicated Reference Index giving one-level-deep, trigger-signaled pointers to six reference files; however the referenced `references/*.md` files are not present in the bundle to verify, slightly weakening actual navigation.

4 / 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 precise, third-person description that clearly states both capability and trigger conditions with concrete domain terms and literal error strings. Only minor: a handful of generic synonyms could broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (create/execute run configs) with specific runnable shapes (`IMainClass`/`ClassConcept` with `main`, `ITestCase` JUnit) and concrete failure diagnostics, giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (create/execute IDE run configurations for MPS root nodes via MPS MCP, with the three shapes) and 'when' (an explicit 'Use when launching... reusing or replacing... diagnosing...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Strong natural-domain keywords (`run configurations`, `main`, `JUnit Tests`, `test cases`) plus literal error strings (`ClassNotFoundException`, `compileInMPS=false`, "not runnable through this tool") users would actually say; a few generic synonyms (e.g. 'run', 'execute', 'debug') are absent.

4 / 5

Distinctiveness Conflict Risk

A narrow, distinctive niche (MPS root-node run configs via MCP) with highly specific triggers and named error conditions, making collision with other skills unlikely.

5 / 5

Total

19

/

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: 8 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.