CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-tests

Use when writing or modifying tests inside MPS `@tests` models — `NodesTestCase` (typesystem, constraints, scopes, dataflow), `GeneratorTest` (generator output against an expected model, match options, explicit generation plans), `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.

Quality

95%

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

92%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 an exemplary reference-skill overview: critical directives and a validated six-step workflow inline, with dense, verifiable MPS specifics (concept UUIDs, MCP tool signatures, action ids) and a well-signaled one-level-deep reference index. The only weakness is minor redundancy — failure-diagnosis detail repeated between Critical Directives, workflow step 6, and the common-failures reference. Actionability and workflow clarity are top-tier for an instruction-only skill.

Suggestions

Compress the deep failure-diagnosis detail in the fail-first directive (e.g. the '`Node: null vs <root>`' / `NO_GENERATORS` interpretation and `AssumptionViolatedException` causes) into a one-line pointer to `references/common-failures.md`, which already covers them.

State the `AssumptionViolatedException` skipped-vs-failed reporting nuance once (either Critical Directives or workflow step 6) and reference the other location instead of repeating it.

DimensionReasoningScore

Conciseness

The body is information-dense MPS-specific knowledge Claude would not have (concept UUIDs, MCP tool parameters, platform action ids, cell-id conventions) with essentially no explanation of already-known concepts, so it sits above anchor 3's 'some unnecessary explanation'. It falls short of anchor 5's 'every token earns its place' due to a few redundant spots: the `AssumptionViolatedException` skipped-vs-failed nuance appears in both the fail-first directive and workflow step 6, and deep failure-diagnosis detail like "`Node: null vs <root>` means no generator ran (`mps_mcp_generation` `PLAN` shows `NO_GENERATORS`…)" duplicates what `references/common-failures.md` covers.

4 / 5

Actionability

Guidance is copy-paste concrete throughout: exact MCP calls with parameters ("`mps_mcp_create_module(type="solution", …, facets="[\"tests\"]")`" with the self-describing JSON response), a concrete concept ref ("instantiate `SimpleNodeTest` (`c:8585453e-6bfb-4d80-98de-b16074f1d86c/1225978065297`)"), exact platform action ids ("`invoke action by id: $Undo` (`$Redo`, `$Copy`, `$Cut`, `$Paste`)") and cell-id conventions ("target `empty_<role>` for the caret — *not* `refNodeList_<role>`"). Every workflow step names the specific tool to use, matching anchor 5.

5 / 5

Workflow Clarity

The Common-Path Workflow is a clearly sequenced six-step process with an explicit validation checkpoint before running ("**Validate** with `mps_mcp_check_root_node_problems` on the new root") and concrete run instructions including how to read the output. Feedback loops are explicit: "A test written first must fail first, for the reason the change addresses… fix it and run again", plus failure-triage guidance for both editor and generator tests. This matches anchor 5's sequence + explicit validation + error-recovery loops.

5 / 5

Progressive Disclosure

The body stays an overview: critical directives and the common-path workflow inline, with a Reference Index that signals exactly when to open each of the ~11 one-level-deep `references/*.md` files (e.g. "Open `references/scopes-test.md` when writing **declarative** scope assertions", "Open `references/common-failures.md` when a test won't run…"). References are one level deep, consistently pathed, and the Related Skills section separates companion-skill loading from internal references — matching anchor 5's well-signaled, easy-to-navigate structure.

5 / 5

Total

19

/

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 dense and fully concrete: it names all five test-case types with their sub-capabilities, the assertion/annotation mechanisms, and the execution paths, then closes with explicit trigger clauses covering authoring, fixing, and interpreting test failures. It is tightly scoped to MPS `@tests` models, minimizing conflict with sibling MPS skills. No vague language, padding, or over-claims; third-person voice with a proper 'Use when' clause.

DimensionReasoningScore

Specificity

Every clause names a concrete capability with sub-capabilities: "`NodesTestCase` (typesystem, constraints, scopes, dataflow)", "`EditorTestCase` (intentions, actions, keystrokes, side-transforms, completion)", "`GeneratorTest` (generator output against an expected model, match options, explicit generation plans)", plus inline annotations, "label-based `node<label>` cross-references, caret markers", and run mechanics. Coverage is comprehensive with no padding — a clear match for the anchor-5 example's breadth, and clearly above anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

Both halves are explicit: the 'what' enumerates five test-case types with their capabilities and mechanisms, and the 'when' opens with "Use when writing or modifying tests inside MPS `@tests` models" and closes with "Reach for this skill whenever the task involves authoring or fixing tests in a `tests`-stereotype model, or interpreting failures from one". This mirrors the anchor-5 example's explicit what-plus-concrete-trigger structure; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Trigger phrasing spans the natural ways a user would ask — "writing or modifying tests", "authoring or fixing tests", "interpreting failures", "running tests via MCP / in MPS" — alongside domain terms users actually say ("typesystem", "constraints", "intentions", "migration scripts", "caret markers", "plain JUnit") and the `@tests` model identifier. Synonym coverage of the core trigger action is thorough, matching anchor 5 rather than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply bounded — tests inside MPS `@tests` models with named concepts (`NodesTestCase`, `GeneratorTest`, `MigrationTestCase`, `BTestCase`) — so it would not fire for the sibling MPS aspect skills (typesystem, constraints, migrations) or general JUnit work outside MPS. Minimal conflict risk, matching anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 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 missing

Warning

referenced_paths_exist

Referenced path issues: 20 missing

Warning

Total

13

/

16

Passed

Repository

JetBrains/MPS

Path

.agents/skills/mps-tests/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.