CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The body is a well-structured overview: crisp critical directives, a sequenced workflow with an explicit error-recovery loop, and a clearly signaled one-level reference index. The main weaknesses are minor verbosity in the companion-skill-loading boilerplate and the fact that every cited reference file is missing from the bundle, which both blocks deep-dive navigation and leaves exact tool-call shapes unavailable. Strengths far outweigh the gaps.

Suggestions

Ship the six referenced files (references/runnable-shapes.md, create-and-execute.md, classconcept-and-fallbacks.md, compile-before-run.md, decision-matrix.md, common-failures.md) with the skill, or remove the dangling Reference Index entries — as delivered, every 'open when' pointer is unresolvable.

Include one minimal inline example of the actual mps_mcp_create_run_configuration call shape (key parameters and a sample nodeReference) so the happy path is executable without opening a reference file.

Tighten the 'Loading companion skills' paragraph to the essential rule (load named siblings from the same catalog; do not invent endpoints), cutting the loader-resolution detail that rarely applies.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no explaining what MPS or run configurations are), but the ~120-word 'Loading companion skills' meta-paragraph and rhetorical flourishes like 'a green IDE run / red stack trace in my hand' could be trimmed. This matches anchor 4 ('efficient; minor instances of over-explanation') rather than 5, where every token would earn its place.

4 / 5

Actionability

Concrete, specific guidance throughout: named tools with parameters ('mps_mcp_alter_nodes MAKE on the module, rebuild: true', 'waitForExit: true', 'modelReference vs nodeReference') and a named-error remediation. However, the exact call shapes are deferred to references/*.md files that are not present in the bundle, leaving minor gaps — anchor 4 rather than the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The Common Workflow is a clearly sequenced 4-step process with concrete parameters, an execution checkpoint (execute with 'waitForExit: true'), and an explicit error-recovery feedback loop ('On "Could not find or load main class", step 1 didn't reach classes_gen — re-run it'), structurally matching the anchor-5 validate-and-retry pattern. Not 4: the checkpoint and retry loop are explicit, not implicit.

5 / 5

Progressive Disclosure

The Reference Index is a well-signaled, one-level-deep overview with explicit 'open when' triggers per file, and nothing inlined that belongs in a separate file. But all six cited references/*.md paths (runnable-shapes.md, create-and-execute.md, classconcept-and-fallbacks.md, compile-before-run.md, decision-matrix.md, common-failures.md) do not exist in the bundle — no references/ directory is present — so navigation cannot actually resolve, matching anchor 4 ('good structure; minor organization gaps') rather than 5.

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.

The description is exemplary: concrete capabilities, an explicit 'Use when' clause with three trigger scenarios, verbatim symptom-based triggers for failure diagnosis, and a sharply distinct MPS niche. It is dense but every clause is informative rather than padded. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create and execute IDE run configurations', 'JUnit Tests for ITestCase', 'reusing or replacing an existing run config', 'diagnosing ClassNotFoundException, compileInMPS=false' — with comprehensive coverage of the skill's capabilities including failure diagnosis. Anchor 4 would apply if coverage had minor gaps, but the named error modes and config-reuse path close those gaps.

5 / 5

Completeness

Explicitly answers both: 'what' in the first sentence (create/execute Java Application and JUnit run configurations via MPS MCP) and 'when' via a concrete 'Use when...' clause listing three trigger scenarios plus diagnosis triggers. This matches the anchor-5 example structure; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered within the domain: 'launching DSL main-like roots', 'MPS test cases', 'run config', plus symptom terms ('ClassNotFoundException', 'not runnable through this tool') a user would quote verbatim, and synonyms across launching/running/executing. Anchor 4 ('a few natural terms missing') fits worse since no common domain trigger word is absent.

5 / 5

Distinctiveness Conflict Risk

Clear niche (MPS root nodes launched via MPS MCP) with highly distinct triggers — IMainClass, ClassConcept, ITestCase, compileInMPS=false — that no generic run/test skill would share. Minimal conflict risk; the MPS-specific jargon disambiguates even generic phrases like 'run tests'.

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.

Validation — 14 / 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

Path

.agents/skills/mps-run-configurations/SKILL.md

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.