mps-language-modularity

Use when designing how multiple MPS languages relate or compose — choosing between language referencing, extension, reuse, and embedding, or deciding where a cross-language dependency should live and how generated code interacts. Covers the 2×2 modularity taxonomy adapted to MPS, a decision procedure, per-kind recipes (references + search scopes; subconcepting + overloaded operations; abstract hooks + adapter languages + separated/interwoven generation; guest + composition languages + type bridges), the annotations escape hatch, and per-kind validation. This is the design tier above the aspect-implementation skills: it picks the strategy, then routes into the relevant mps-aspect-* skills (structure, constraints, typesystem, generator, generation-plan, intentions) and mps-tests. Reach for it before authoring aspects, or whenever one language must see, extend, embed, or adapt another.

Quality

92%

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-organized, concise design-tier skill with a clear decision procedure and excellent progressive disclosure via verified reference files. The only gap is actionability being inherently conceptual rather than executable, which the skill itself acknowledges and routes to aspect skills.

Suggestions

Consider adding one short, concrete MPS-MCP-tool invocation example (e.g., the actual tool calls to declare a used language or set a search scope) to lift actionability from conceptual routing toward executable guidance.

The 'Reference index' could note a recommended reading order or mark which reference is the best entry point for each of the four kinds, reducing navigation friction.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense — dense tables and a tight decision procedure — and assumes Claude's competence without padding or explaining basics MPS users already know.	3 / 3
Actionability	The decision procedure and routing tables are concrete guidance, but the body is design-tier conceptual direction rather than executable code; the explicit 'illustrative pseudo-syntax... implement through MPS MCP tools' note justifies this, keeping it above a 1.	2 / 3
Workflow Clarity	A clearly sequenced three-step decision procedure with explicit branch answers, plus validation guidance ('Run the model checker over the example suite after every structural or generator change') and a per-kind checklist reference.	3 / 3
Progressive Disclosure	A concise overview SKILL.md with a 'Reference index' signaling six one-level-deep reference files — all verified present (referencing, extension, reuse, embedding, design-principles, validation) — plus a Related skills section for navigation.	3 / 3
	Total	11 / 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.

A strong, specific description with explicit 'Use when'/'Reach for it' triggers, concrete capabilities, and a well-delineated niche that routes to downstream aspect skills. No notable weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'choosing between language referencing, extension, reuse, and embedding', 'deciding where a cross-language dependency should live and how generated code interacts', plus 'per-kind recipes' and 'per-kind validation' — rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (picks the modularity strategy and routes into aspect skills) and 'when' via 'Use when...' and 'Reach for it before authoring aspects' trigger clauses.	3 / 3
Trigger Term Quality	Natural MPS-user phrasings are present — 'designing how multiple MPS languages relate or compose', 'before authoring aspects', 'whenever one language must see, extend, embed, or adapt another' — covering the likely trigger surface well.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — the design tier above aspect-implementation skills — with explicit routing, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 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: 4 suspicious	Warning

	Total	14 / 16 Passed

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