CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-mcp-workflow

Complete JetBrains MPS workflow guide for DSL projects — models, languages, generators, node JSON blueprints, validation, MPS MCP tool usage, and the index of companion skills. Use whenever working in an MPS project, when AGENTS.md says to load the MPS workflow skill, or when you need to pick the right MPS aspect-specific skill.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/mps-mcp-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable with strong, validated multi-step workflows and concrete MPS-MCP tool guidance, but it carries some over-explanation of basics and, critically, references seven reference files that are not present in the bundle, breaking progressive disclosure.

Suggestions

Ship the missing references/*.md files (finding-things, node-editing-rules, reference-formats, bulk-creation, analysis-tools, editor-workflow, mcp-tools-index) or inline the essential parts so the signaled navigation resolves.

Trim the Key Concepts section's explanations of AST/projectional-editor fundamentals that Claude already knows, keeping only MPS-specific terminology definitions.

Condense the multi-project and install/refresh notes, which are dense and could move to a single companion reference to reduce body token cost.

DimensionReasoningScore

Conciseness

Most content is operationally dense and earns its place (specific tool names, ordering chains), but the Key Concepts section explains AST/projectional-editor basics Claude largely knows and some multi-project/installation notes are padded; it could be tightened, matching the "mostly efficient with some unnecessary explanation" anchor.

3 / 5

Actionability

Concrete, specific guidance dominates — named tools like mps_mcp_update_root_node_from_json, mps_mcp_check_root_node_problems, and explicit alter_structure MAKE sequences — with only minor gaps where detail is deferred to reference files, sitting just below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The Structure-to-Aspect Prerequisite Chain is a numbered 4-step sequence with an explicit Verify-Descriptors checkpoint and recovery notes, and the Initialize-a-Session workflow plus "Validate frequently" directive provide clear feedback loops for these destructive/batch model edits, matching the top anchor.

5 / 5

Progressive Disclosure

The body is well-structured with clearly signaled one-level-deep references ("Open references/finding-things.md for..."), but the referenced bundle files do not exist in this package — the ./references/ directory is absent — so the navigation promise is broken and the disclosure structure does not actually deliver, pulling it down to the mid anchor.

3 / 5

Total

15

/

20

Passed

Description

87%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, well-scoped description that clearly states what the skill covers and when to load it, with concrete MPS-specific trigger phrases and low conflict risk. It is only slightly below ceiling on specificity and trigger-term breadth.

DimensionReasoningScore

Specificity

The description enumerates concrete domains — "models, languages, generators, node JSON blueprints, validation, MPS MCP tool usage, and the index of companion skills" — but frames them as topics a guide covers rather than discrete actions, leaving minor gaps versus the comprehensive-actions anchor at 5.

4 / 5

Completeness

It explicitly answers both what (the listed coverage areas) and when ("Use whenever working in an MPS project, when AGENTS.md says to load the MPS workflow skill, or when you need to pick the right MPS aspect-specific skill") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases a user would say appear ("MPS project", "DSL projects", "AGENTS.md", "MPS workflow skill", "MPS aspect-specific skill"), with good keyword coverage; a few common synonyms/extensions are missing, so it sits just below the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is tightly scoped to JetBrains MPS DSL work with MPS-MCP-specific triggers, making conflict with other skills minimal and matching the clear-niche anchor.

5 / 5

Total

18

/

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.

Validation14 / 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: 7 missing

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.