mps-aspect-accessories

Wire MPS module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language/dependency versions. Use when adding/removing module dependencies, importing languages or devkits into a model, declaring runtime solutions, or shipping accessory content visible to consumers without explicit import.

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%

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

A well-structured reference skill: lean, competent body with concrete MCP tool calls, a clear verified workflow, and excellent one-level-deep progressive disclosure with all referenced files present. The main weakness is verbosity in the Reference Index, which previews content that belongs in the reference files.

Suggestions

Tighten each Reference Index bullet to a single short clause stating only what the file covers; move the sub-topic enumerations (e.g., the six runtime-solutions sub-topics, the eight module-level-deps declarations) into the reference files themselves.

Trim the runtime-solutions and module-level-deps index entries in particular, since they currently duplicate content the reader will get when opening those references.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no concept primers or fluff), but the Reference Index previews detailed per-file content — e.g., the runtime-solutions bullet enumerates six sub-topics (Java-facet settings, <runtime>-block wiring, jar-as-stubs, the no-MCP-tool caveat, the Kaja example) — that could be tightened and left to the references.	2 / 3
Actionability	It names concrete MCP tools with parameters (mps_mcp_model_used_language with kind = language or devkit, mps_mcp_create_module type="solution", mps_mcp_get_project_structure startingPoint=<module>) and gives a concrete dependency-vs-used-language decision rule, which is specific, actionable guidance for a reference skill.	3 / 3
Workflow Clarity	The Common Workflow is a clear four-step sequence (Inspect → Diagnose → Apply → Rebuild) with an explicit rebuild verification checkpoint ("Rebuild the module so MPS re-reads the descriptor") and an explicit error-recovery step ("Diagnose the symptom against the pitfalls table").	3 / 3
Progressive Disclosure	The body is an overview with a well-signaled one-level-deep Reference Index; all nine referenced local files (accessory-models, extends-vs-uses, model-level-imports, module-creation, module-info-fields, module-level-deps, module-rename, pitfalls, runtime-solutions) exist and are clearly described, giving easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

92%

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: information-dense, third-person, with an explicit "Use when..." trigger clause and concrete MPS capabilities. The only real weakness is overlap risk with sibling MPS skills on the used/extended-language triggers.

Suggestions

Add a disambiguating qualifier to the used/extended-language items (e.g., "wiring — not inheritance semantics — of used/extended languages") so they don't overlap with mps-language-inheritance.

Include a one-line contrast in the description (e.g., "For inheritance semantics see mps-language-inheritance; for generator deps see mps-aspect-generator") to reduce conflict risk on shared triggers.

Dimension	Reasoning	Score
Specificity	"Wire MPS module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language/dependency versions" plus "adding/removing module dependencies, importing languages or devkits... declaring runtime solutions, or shipping accessory content" lists multiple specific concrete capabilities and actions, matching the anchor for listing several concrete actions rather than a single vague one.	3 / 3
Completeness	It explicitly states what ("Wire MPS module and model dependencies...") and when via an explicit "Use when adding/removing module dependencies, importing languages or devkits into a model, declaring runtime solutions, or shipping accessory content..." clause, satisfying both the what and the when with explicit triggers.	3 / 3
Trigger Term Quality	Terms like "module dependencies", "importing languages or devkits", "runtime solutions", and "accessory content" are the natural vocabulary an MPS user would say when requesting this work, giving good coverage of relevant trigger terms.	3 / 3
Distinctiveness Conflict Risk	It carves a clear MPS niche with distinctive accessory/runtime triggers, but "used languages... extended languages" and "importing languages or devkits into a model" overlap with the sibling skills named in the body (mps-language-inheritance, mps-aspect-generator), so it could still fire for a closely related skill.	2 / 3
	Total	11 / 12 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-aspect-accessories/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.