CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-structured reference skill: critical directives, a decision rule, a tool quick reference, and a routed reference index keep it actionable and token-efficient. The main improvement opportunity is an explicit validation step in the workflow (e.g. re-inspect the module to confirm the dependency resolved) and slightly tighter directive phrasing.

Suggestions

Add an explicit validation step to the Common Workflow, e.g. "5. Verify: re-run mps_mcp_get_project_structure(startingPoint=<module>) and confirm the new dependency/used language appears".

Split the multi-clause language-OWN-version directive into a short rule plus a pointer to references/module-info-fields.md, trimming the in-body explanation of fromVersion computation.

Include one concrete mps_mcp_module_dependency or mps_mcp_model_used_language call (tool name + key arguments) in the MCP Tools Quick Reference so the most common action is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and expert-level with no padding or teaching of known concepts, but a few directives (notably the language-OWN-version bullet) pack many clauses into single sentences that could be trimmed or split.

4 / 5

Actionability

Gives concrete tool names with parameters ("mps_mcp_get_project_structure(startingPoint=<module>)", "mps_mcp_create_module(type='solution')") and a decision rule for dependency vs. used language; minor gaps remain since actual wiring call examples are deferred to references.

4 / 5

Workflow Clarity

The Inspect → Diagnose → Apply → Rebuild workflow is clearly sequenced with a pitfalls-diagnosis feedback step and a rebuild checkpoint, but there is no explicit post-change validation that the wiring resolved the symptom.

4 / 5

Progressive Disclosure

The body is a lean overview with a "Start here — most common case" routing guide, one-level-deep reference entries each with a clear purpose statement, and a Related Skills section — easy to navigate with details properly external.

5 / 5

Total

17

/

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 description: it states a comprehensive, domain-specific capability list and pairs it with an explicit multi-trigger "Use when" clause. Trigger coverage and separation from adjacent sibling skills could be marginally improved with synonyms and clearer boundary terms.

DimensionReasoningScore

Specificity

Enumerates the full capability surface concretely: "Wire MPS module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language/dependency versions" — comprehensive concrete actions with no notable gaps.

5 / 5

Completeness

Explicitly answers both "what" (the wiring enumeration) and "when" via a concrete "Use when adding/removing... importing... declaring... shipping..." clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "adding/removing module dependencies", "importing languages or devkits into a model", and "declaring runtime solutions" match what an MPS user would say, but synonyms and file extensions (.mpl) are missing.

4 / 5

Distinctiveness Conflict Risk

The wiring/dependency niche is clearly distinct with specific triggers, but overlap risk remains with closely related companion skills (e.g. mps-language-inheritance also covering extendedLanguages).

4 / 5

Total

18

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 16 missing

Warning

Total

13

/

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.