mps-node-editing

Add, update, or delete MPS nodes using JSON blueprints — covers the unified blueprint format, staged construction for large subtrees, validation, and reference repair. Use whenever creating, editing, or restructuring nodes in any MPS model (structure, editor, behavior, generator, application code, etc.).

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 and presents a well-validated workflow for mutating MPS nodes. Its main weakness is progressive disclosure: three reference files are advertised in the Reference Index but are absent from the bundle, breaking the navigation it promises.

Suggestions

Add the missing reference files to ./references/ (json-format.md, staged-construction.md, troubleshooting.md) so the Reference Index links resolve, or remove the references and inline the essential material.

Trim the duplicated file-path semantics — the "JSON Input — File-Path Semantics" section restates the inline note already present in the `childJson` row; consolidate to one location.

Verify each path named in the Reference Index against the actual bundle before shipping so disclosed references are never dangling.

Dimension	Reasoning	Score
Conciseness	Mostly lean and high-signal (dense tool matrix, terse directives) with minor trimmable redundancy — the "JSON Input — File-Path Semantics" section restates the inline file-path note already given for `childJson`.	4 / 5
Actionability	Provides concrete, executable guidance: exact tool names, the operation×kind matrix with required parameters, `dryRun: true` first-pass, and specific calls like `mps_mcp_apply_intention` and `autoApplyQuickFixes=true` covering the common cases.	5 / 5
Workflow Clarity	The 6-step Common Workflow has explicit validation checkpoints (dryRun + `warnings` check, `mps_mcp_check_root_node_problems`, quickFix repair) forming a validate→fix→retry loop for destructive/batch node operations, satisfying the destructive-op validation requirement.	5 / 5
Progressive Disclosure	The body is well-structured with a clearly signaled one-level-deep Reference Index, but the referenced files (references/json-format.md, references/staged-construction.md, references/troubleshooting.md) do not exist in the bundle — the disclosed deeper material is missing, which is more than a minor organization gap.	3 / 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, specific description that clearly states both the capability and the use trigger, well-distinguished within the MPS domain. It could be marginally improved by adding more natural-sounding trigger synonyms alongside the technical phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Add, update, or delete MPS nodes using JSON blueprints", "validation, and reference repair", "staged construction for large subtrees") with comprehensive coverage of the editing surface, matching the anchor for listing multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("Add, update, or delete MPS nodes using JSON blueprints — covers ... validation, and reference repair") and when ("Use whenever creating, editing, or restructuring nodes in any MPS model") with a concrete trigger phrase and model-type enumeration, in third person.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ("creating, editing, or restructuring nodes in any MPS model") but leans on technical jargon ("JSON blueprints", "unified blueprint format") and omits common synonyms a user might say ("add a node", "fix references"), so good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to MPS nodes via JSON blueprints with an enumerated model-aspect list, giving a clear distinct trigger with minimal conflict risk even against sibling MPS skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-node-editing/SKILL.md
Commit: c74b207

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.