CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 tight, well-structured reference that gives concrete tool-level guidance without teaching Claude what it already knows. It is an instruction/reference skill whose guidance is fully actionable.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding — it never explains what MPS is or basic inheritance concepts, and every line delivers actionable guidance that earns its tokens.

3 / 3

Actionability

Concrete tool calls and specific operations throughout (mps_mcp_get_project_structure with includeDependencies, GET_ALL_SUPERCONCEPTS, GET_SUB_CONCEPTS, GET_ASSIGNABLE_CONCEPTS, IS_SUBCONCEPT_OF), naming exact response fields to inspect.

3 / 3

Workflow Clarity

The Module-Level section is explicitly sequenced (Tool → Workflow → Hierarchy tracing) and Critical Directives prioritize the correct calls; as a read-only investigation skill it needs no destructive-operation validation checkpoints, so the clear sequence is sufficient.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed, yet well-organized into clear sections (Critical Directives, Module-Level, Concept-Level up/down, Strategic Analysis, Best Practice, Related Skills), satisfying the simple-skill scoring note.

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 concise, specific, and clearly delineates both capability and trigger conditions in third person. It is a strong example with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "extended languages, superconcepts, implemented interfaces, sub-/assignable concepts, and cross-language specialization" — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers what ("Investigate inheritance between MPS languages and between concepts ...") and when ("Use when tracing language hierarchies, finding extension points, or checking concept assignability"), with an explicit "Use when" clause.

3 / 3

Trigger Term Quality

Natural phrasing a user would say is present — "tracing language hierarchies, finding extension points, or checking concept assignability" — giving good coverage of natural trigger terms for MPS users.

3 / 3

Distinctiveness Conflict Risk

The MPS-specific niche (language/concept inheritance, cross-language specialization) and its triggers are distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.