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

80%

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

72%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.

A well-organized, token-efficient overview that points to a clear reference structure and names the right MCP tools. Its main weaknesses are a missing validation/retry loop in the destructive hand-edit workflow and the absence of the referenced bundle files that the index promises.

Suggestions

Add an explicit feedback loop to Common Workflow for the destructive .mpl hand-edit path: after 'Rebuild', state 'if MPS reports descriptor errors, re-check references/pitfalls.md, fix the targeted block, and rebuild again'.

Create the referenced bundle files (references/module-level-deps.md, model-level-imports.md, accessory-models.md, runtime-solutions.md, extends-vs-uses.md, pitfalls.md, module-creation.md, module-rename.md, module-info-fields.md) so the Reference Index resolves.

Include one concrete fully-parameterized mps_mcp_module_dependency call example with sample scope values to lift actionability from high-level hints to copy-paste-ready guidance.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it assumes Claude's knowledge of MPS and offers no padded concept explanations; every directive, tool name, and reference earns its place.	5 / 5
Actionability	Names concrete MCP tools with parameters (e.g. 'mps_mcp_model_used_language (kind = language or devkit)', 'mps_mcp_create_module(type="solution", …)') and a layer-dispatch rule, but stops short of a full copy-paste call example with values.	4 / 5
Workflow Clarity	The Common Workflow (Inspect → Diagnose → Apply → Rebuild) is sequenced, but for destructive .mpl hand-editing it lacks an explicit validate→fix→retry feedback loop; 'Rebuild' acts as a weak checkpoint with no error-recovery path stated.	3 / 5
Progressive Disclosure	The Reference Index clearly signals one-level-deep references, but the referenced files (references/module-level-deps.md, model-level-imports.md, accessory-models.md, etc.) do not exist in the bundle, so the disclosed structure is non-navigable.	3 / 5
	Total	15 / 20 Passed

Description

88%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, third-person description that concretely enumerates capabilities and provides an explicit 'Use when…' trigger clause covering the main invocation scenarios. It is specific and well-scoped to the MPS wiring layer with only minor overlap risk against related MPS skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete wiring actions — 'module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language/dependency versions' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (Wire MPS module and model dependencies…) and 'when' ('Use when adding/removing module dependencies, importing languages or devkits into a model, declaring runtime solutions, or shipping accessory content…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong domain-natural terms ('module dependencies', 'used languages', 'devkits', 'runtime solutions', 'accessory models') that MPS users would actually say, though coverage leans on technical jargon over common synonyms.	4 / 5
Distinctiveness Conflict Risk	Clear niche (MPS wiring/accessory layer) with distinct triggers, but minor overlap risk with sibling skills like mps-language-inheritance and mps-aspect-generator that cover adjacent dependency territory.	4 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 13 / 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
referenced_paths_exist	Referenced path issues: 11 missing	Warning

	Total	13 / 16 Passed

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