CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-language-inheritance

Investigate inheritance between MPS languages and between concepts — extended languages, superconcepts, implemented interfaces, sub-/assignable concepts, and cross-language specialization. Use when tracing language hierarchies, finding extension points, or checking concept assignability.

Quality

82%

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

71%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 delivers specific, actionable MPS tool guidance with a clear two-layer (module vs concept) structure and well-signaled companion references. Its main weaknesses are redundancy (the Best Practice and companion-loading sections) and the absence of a worked example or explicit verification checkpoints in the analysis workflows.

Suggestions

Remove or fold the 'Best Practice' section into 'Strategic Analysis', since it repeats the extendedLanguages-then-concept-details workflow already described there.

Tighten the companion-loading paragraph to the essential rule (load named siblings from the same catalog) and trim the conditional MCP/filesystem policy detail.

Add a short worked example of the cross-language check, e.g. comparing languageReference between a concept and its superConcept and what a mismatch implies, to make the most subtle guidance concrete.

DimensionReasoningScore

Conciseness

The body is mostly lean and tool-focused, but the "Best Practice" section restates guidance already covered in "Critical Directives" and "Strategic Analysis", and the companion-skill loading paragraph is padded with conditional policy detail. Fits anchor 3 (some unnecessary explanation, could be tightened) rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Guidance is concrete and executable: named tools with parameters ("mps_mcp_get_project_structure (with includeDependencies: true)", "GET_ALL_SUPERCONCEPTS", "IS_SUBCONCEPT_OF") and specific response fields (extendedLanguages, superConcept, superInterfaces, languageReference). Anchor 4 rather than 5 because no example query payloads or a worked cross-language comparison are shown, leaving minor gaps.

4 / 5

Workflow Clarity

Module-level and concept-level workflows are clearly sequenced (check extendedLanguages, recurse for parents; upward via GET_ALL_SUPERCONCEPTS, downward via GET_SUB_CONCEPTS) with verification embedded through IS_SUBCONCEPT_OF. Matches anchor 4 (clear sequence, most checkpoints) rather than 5 since there are no explicit validation/feedback checkpoints, though the read-only operations make the destructive-operation cap inapplicable.

4 / 5

Progressive Disclosure

This is a single-purpose reference skill with no bundle files; content is appropriately compact with well-organized sections and clearly signaled one-level-deep companion references in "Related Skills". Per the simple-skill guideline this matches anchor 5; navigation is easy and nothing that belongs in a separate file is inlined.

5 / 5

Total

16

/

20

Passed

Description

87%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 names a specific niche, enumerates concrete mechanisms at both module and concept level, and includes an explicit 'Use when' clause with natural trigger phrases. Trigger synonyms could be slightly broadened, but conflict risk and completeness are excellent.

DimensionReasoningScore

Specificity

Concrete actions are listed ("tracing language hierarchies, finding extension points, or checking concept assignability") alongside enumerated mechanisms (extended languages, superconcepts, implemented interfaces, sub-/assignable concepts). Not 5 because it is one umbrella action ("Investigate") with sub-topics rather than multiple distinct fully concrete actions; not 3 because coverage extends well past 1-2 actions.

4 / 5

Completeness

Explicitly answers "what" (investigate language- and concept-level inheritance via extended languages, superconcepts, interfaces, sub-/assignable concepts, cross-language specialization) and "when" with a concrete "Use when tracing language hierarchies, finding extension points, or checking concept assignability" clause, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural MPS vocabulary is present ("inheritance", "superconcepts", "extension points", "concept assignability", "cross-language specialization") which users of this domain would actually say. A few natural phrasings are missing (e.g. "which language extends which", "concept hierarchy"), placing it at anchor 4 rather than 5; well above the generic-keyword anchors of 2-3.

4 / 5

Distinctiveness Conflict Risk

The MPS language/concept inheritance niche is distinct with clear triggers (inheritance, superconcepts, extension points, assignability), so it is unlikely to fire for unrelated skills; only minimal overlap with a general MPS language-analysis companion, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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-language-inheritance/SKILL.md

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.