CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

85%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise overview with a clear validated workflow and excellent progressive disclosure through a one-level-deep reference index. The only gap is that concrete executable examples live entirely in referenced files rather than the body itself.

Suggestions

Include one short in-situ JSON blueprint snippet (e.g. a minimal PureMigrationScript move) so the body is copy-paste-ready without first opening a reference.

Consider adding an explicit "if validation reports problems, fix and re-run" feedback loop in step 6 to make the validate→fix→retry cycle explicit.

DimensionReasoningScore

Conciseness

The body is lean (~40 lines) with no general-knowledge padding; directives, a numbered workflow, and a reference index each earn their tokens and assume Claude's competence.

3 / 3

Actionability

It names concrete tools (mps_mcp_create_model, mps_mcp_check_root_node_problems) and reference files for blueprints, but the body itself contains no in-situ executable code or copy-paste examples — all concrete syntax is offloaded to references.

2 / 3

Workflow Clarity

A clear 6-step sequence includes an explicit validation checkpoint (step 6: check root node problems then run on a test model) plus Critical Directives guardrails, matching the anchor for explicit validation steps.

3 / 3

Progressive Disclosure

A concise overview points to a well-organized Reference Index where each entry states when to open it and links one level deep; all cited reference files (form-selection, lang-migration-reference, etc.) exist in the bundle, with content appropriately split across files.

3 / 3

Total

11

/

12

Passed

Description

85%

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 highly specific, distinctive description that clearly states both capabilities and use-when triggers for MPS migration authoring/debugging. Its only weakness is a jargon-heavy trigger vocabulary that may not match a user's everyday phrasing.

Suggestions

Add a few user-facing natural-language triggers alongside the jargon (e.g. "when a language definition changes and user models need upgrading") so trigger_term_quality reaches full natural-term coverage.

DimensionReasoningScore

Specificity

Lists many concrete capabilities such as "MigrationScript class-based, PureMigrationScript declarative, MoveConcept/MoveContainmentLink/MoveReferenceLink/MoveProperty, ordering via OrderDependency, putData/getData, RefactoringLog" and Enhancement Script variants, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers what (the two languages and their migration constructs) and when via a clear "Use when authoring or debugging MPS migration scripts ... when a model needs version-gated upgrade, concept rename or removal ..." clause.

3 / 3

Trigger Term Quality

Trigger phrases like "version-gated upgrade, concept rename or removal, link or property rename, instance-level transformation" are MPS-domain natural phrasings, but the description leans heavily on technical jargon and lacks broader common-term variations, stopping short of full natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

Highly niche to the MPS migration aspect with language UUIDs and specific concept names, making it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

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.