CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-aspect-migrations

Use when authoring or debugging MPS migration scripts that upgrade user models after a language definition changes — covers jetbrains.mps.lang.migration (MigrationScript class-based, PureMigrationScript declarative, MoveConcept/MoveContainmentLink/MoveReferenceLink/MoveProperty, ordering via OrderDependency, data exchange via putData/getData, RefactoringLog, ConceptMigrationReference) and jetbrains.mps.lang.script Enhancement Scripts (MigrationScript with MigrationScriptPart_Instance, ExtractInterfaceMigration, FactoryMigrationScriptPart, CommentMigrationScriptPart) — when a model needs version-gated upgrade, concept rename or removal, link or property rename, instance-level transformation, or composition of migration steps.

Quality

87%

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 dense, expert-level reference with strong gotcha-oriented directives, a well-sequenced workflow with explicit validation feedback loops, and excellent reference signaling. The main gaps are the absence of any inline executable example and the fact that every referenced file is missing from the bundle as provided.

Suggestions

Trim the generic "Loading companion skills" paragraph to a sentence and split the longest Critical Directives bullets so each states one rule.

Inline one minimal verified JSON snippet (e.g., a PureMigrationScript concept rename) so the workflow is executable before opening references/json-blueprints.md.

Ship the referenced files — all nine references/*.md paths cited in the Reference Index are absent from the bundle as provided.

DimensionReasoningScore

Conciseness

Dense, load-bearing directives with no padding ("fromVersion is the version migrated FROM — and both forms get it from a node factory"), but the generic "Loading companion skills" paragraph and a few very long Critical Directives bullets could be trimmed.

4 / 5

Actionability

Concrete MCP commands with parameters ("mps_mcp_update_module(moduleName = \"<language>\", operation = \"SYNC_VERSION\")", "MAKE (rebuild=true)") but all executable JSON examples are deferred to references/json-blueprints.md, so nothing copy-paste-ready is inline.

4 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation and feedback loops: "If migrationProblems in its response is not empty, fix the listed scripts' fromVersion and sync again", and check_root_node_problems → MAKE → run migration on a test model.

5 / 5

Progressive Disclosure

Exemplary one-level-deep reference index with per-entry "open when" triggers and a "Start here" routing entry, but none of the nine referenced references/*.md files exist in the provided bundle, so navigation cannot actually be completed.

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 strong description with explicit what/when trigger phrases, comprehensive concrete coverage of both jetbrains.mps.lang.migration and Enhancement Scripts, and a clearly distinct niche. Its only weakness is that dense internal concept names crowd out a few natural user-facing trigger synonyms.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities comprehensively: "authoring or debugging MPS migration scripts", "concept rename or removal, link or property rename, instance-level transformation, or composition of migration steps", covering both migration languages' feature sets.

5 / 5

Completeness

Explicitly answers both: what ("authoring or debugging MPS migration scripts that upgrade user models after a language definition changes") and when ("Use when authoring or debugging... when a model needs version-gated upgrade, concept rename or removal...").

5 / 5

Trigger Term Quality

Natural phrases like "migration scripts", "upgrade user models", "concept rename", and "language definition changes" are present, but a few natural variations ("migrate models", "language version bump") are missing amid heavy internal jargon like "MoveContainmentLink" and "ConceptMigrationReference".

4 / 5

Distinctiveness Conflict Risk

Clear niche — MPS model migrations via two named languages with concept lists — that would not naturally trigger for other MPS aspect skills; conflict risk is minimal.

5 / 5

Total

19

/

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: 11 missing

Warning

referenced_paths_exist

Referenced path issues: 27 missing

Warning

Total

13

/

16

Passed

Repository

JetBrains/MPS

Path

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