mps-model-manipulation

Use when writing or editing MPS BaseLanguage code that lives inside a model — behavior methods, typesystem rules, checking rules, generator queries, constraints, intentions, scope/canBe callbacks, dataflow builders — and combines the `smodel`, `collections`, and `closures` language extensions. Covers querying nodes (`.descendants<C>`, `.ancestor<C>`, `.children`, `.parent`, `containingRoot`), filtering sequences (`.where`, `.select`, `.translate`, `.ofConcept<C>`), building closures (`{ it => ... }`, `yield`, recursion), creating and mutating nodes (`new node<C>()`, `add new(C)`, `set new(C)`, `replace with new(C)`, `.detach`, `.copy`), property and link access (`SPropertyAccess`, `SLinkAccess`, `SLinkListAccess`), reference operations (`.reference/C : role/`, `.target`), null-safe node equality (`:eq:` / `:ne:`), smodel/Java type casts (`node:C`, `node as C`, `/`, `downcast`), foreach choice, the `command` / `read action` lock wrappers, and JSON blueprints for every shape the Java parser cannot produce.

Quality

100%

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

100%

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 lean, expert-oriented overview that pairs concrete directives and a validated workflow with a well-signaled one-level-deep reference catalog. It avoids pedagogy, assumes competence, and routes detail to the right files.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with no explanation of concepts Claude already knows; every line carries concept names, error signatures, or tool names, and it assumes competence throughout.	3 / 3
Actionability	Gives concrete, actionable guidance — exact MCP tool calls (`mps_mcp_parse_java_and_insert`, `mps_mcp_check_root_node_problems`), precise decision rules (`SLinkAccess` for 0..1/1 vs `SLinkListAccess` for 0..n/1..n), and specific error signatures to watch for — which meets the actionable bar for an instruction skill even though executable blueprints live in references.	3 / 3
Workflow Clarity	A clear 6-step numbered sequence with an explicit validation checkpoint (step 5, `mps_mcp_check_root_node_problems`) and an error-recovery branch (step 6, adding used languages/dependencies on import failures), plus a pitfalls checklist in Critical Directives.	3 / 3
Progressive Disclosure	A well-organized overview pointing to 18 one-level-deep reference files (all verified to exist), with a dedicated Reference Index annotating each file's purpose for easy navigation; content is appropriately split between the overview and references.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 a dense, concrete catalog of capabilities with an explicit 'Use when' trigger and clear niche boundaries. It is comprehensive rather than padded, and its jargon is precisely the natural vocabulary of its intended MPS users.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — querying nodes (`.descendants<C>`, `.ancestor<C>`), filtering (`.where`, `.select`, `.translate`), closure building, node mutation (`new node<C>()`, `add new(C)`), property/link access, reference ops, casts, and lock wrappers — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both: 'Use when writing or editing MPS BaseLanguage code…' (when) and 'Covers querying nodes… creating and mutating nodes…' (what), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Covers the natural domain terms an MPS user would actually say ('MPS BaseLanguage', 'behavior methods', 'typesystem rules', 'checking rules', 'generator queries', `smodel`/`collections`/`closures`); this jargon is the colloquial language of the niche, with broad coverage and no common variation omitted.	3 / 3
Distinctiveness Conflict Risk	A narrow, clearly bounded MPS BaseLanguage + smodel/collections/closures niche with distinct triggers, explicitly disambiguated from sibling skills (mps-baselanguage, mps-console), making wrong-skill activation unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-model-manipulation/SKILL.md
Commit: 52c9d63

Reviewed: about 5 hours 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.