CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-tests

Use when writing or modifying tests inside MPS `@tests` models — `NodesTestCase` (typesystem, constraints, scopes, dataflow, generator output), `EditorTestCase` (intentions, actions, keystrokes, side-transforms, completion), `MigrationTestCase` (migration scripts), `BTestCase` (plain JUnit on hand-written Java/Kotlin runtime), inline annotations such as `has error` / `has type` / `ScopesTest`, label-based `node<label>` cross-references, caret markers, and running tests via MCP / in MPS. Reach for this skill whenever the task involves authoring or fixing tests in a `tests`-stereotype model, or interpreting failures from one.

78

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.

A well-structured reference skill: concise, highly actionable with concrete MCP calls and concept refs, a sequenced workflow with validation checkpoints, and exemplary progressive disclosure pointing to verified one-level-deep reference files.

DimensionReasoningScore

Conciseness

Lean and dense with specifics — no padding or explanation of concepts Claude already knows; each directive (stereotype rules, used languages, facet requirements, abstract-concept gotcha) earns its place.

3 / 3

Actionability

Concrete, executable guidance throughout: named MCP tool calls ('mps_mcp_create_model', 'mps_mcp_create_root_node', 'mps_mcp_parse_java_and_insert', 'mps_mcp_check_root_node_problems'), UUID concept refs, and exact role/cell conventions ('empty_<role>' not 'refNodeList_<role>').

3 / 3

Workflow Clarity

The numbered 'Common-Path Workflow' sequences test-type selection through add-root, mark-assertions, validate (step 5 'mps_mcp_check_root_node_problems'), and run, with an explicit pre-run validation checkpoint and run-configuration guidance.

3 / 3

Progressive Disclosure

Clear overview body with a well-signaled one-level-deep 'Reference Index' of 10 real files (all verified present in ./references/), each prefixed with 'Open X when Y' navigation cues; content is appropriately split rather than inlined.

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 specific, well-triggered, third-person description that clearly states both the capability set and the use conditions, scoped to a distinct MPS testing niche. No over-claims or fluff.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities across named test classes ('NodesTestCase (typesystem, constraints, scopes, dataflow, generator output)', 'EditorTestCase (intentions, actions, keystrokes...)', 'MigrationTestCase', 'BTestCase'), plus inline annotations, label-based cross-references, caret markers, and running via MCP/in MPS — multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (the test classes and artefacts it covers) and when, opening with 'Use when writing or modifying tests...' and closing with 'Reach for this skill whenever the task involves authoring or fixing tests in a tests-stereotype model, or interpreting failures from one.'

3 / 3

Trigger Term Quality

Natural user phrasing is well covered: 'writing or modifying tests', 'authoring or fixing tests', 'interpreting failures', and 'tests-stereotype model' — terms a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to MPS '@tests' models with specific JetBrains MPS test concepts; written in third person; very unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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

relative_links

Relative link issues: 1 suspicious

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.