mps-aspect-structure-concepts

Define concepts, interface concepts, enumerations, and constrained data types in an MPS language's `structure` aspect. Covers smart-reference detection, alias rules, cardinality, INamedConcept usage, bulk creation, and the full `mps_mcp_alter_structure` / `mps_mcp_query_structure` reference. Use when authoring or modifying a language's structure model.

Quality

81%

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

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 content is well-organized, concise, and actionable with named MCP tool calls and a clear workflow plus rebuild validation, scoring solidly across conciseness, actionability, and workflow clarity. The main weakness is progressive disclosure: the body points to two reference files that are not present in the bundle.

Suggestions

Add the missing referenced files (references/structure-operation-api.md and references/attributes-and-annotations.md) to the bundle, or remove the Reference Index pointers if those materials are not being shipped.

Include one small end-to-end JSON blueprint example inline (e.g. a minimal ConceptDeclaration with INamedConcept) so the most common case is copy-paste ready without opening a reference.

Add an explicit validate→fix→retry loop for mps_mcp_alter_structure batch operations, mirroring the makeStatus (success/runtime_stale/failed/skipped) handling already mentioned, to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body assumes MPS domain competence and avoids explaining basics, with dense, useful directives; minor redundancy between 'Critical Directives' and workflow steps 5-7/11 keeps it just below a 5.	4 / 5
Actionability	Names concrete tool calls and flags (e.g. 'mps_mcp_alter_structure', 'mps_mcp_alter_nodes MAKE', 'rebuild="true"') and gives specific guidance like enum-before-property ordering, but full copy-paste JSON blueprints are deferred to references rather than shown inline.	4 / 5
Workflow Clarity	An 11-step sequence is clearly laid out with a rebuild-to-make-discoverable checkpoint repeated for emphasis, but the alter/batch operations lack an explicit validate→fix→retry feedback loop of the kind the rubric reserves for a 5.	4 / 5
Progressive Disclosure	The Reference Index clearly signals two one-level-deep reference files, but those files (references/structure-operation-api.md and references/attributes-and-annotations.md) do not exist in the bundle, so the signaled navigation is broken. Not a 2 because structure and signaling are good; not a 4 because the referenced separate files are missing.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific, complete, and clearly distinct, naming concrete capabilities and an explicit 'Use when' trigger. Its only mild gap is trigger-term synonym coverage, which keeps trigger_term_quality at a strong-but-not-perfect 4.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — 'Define concepts, interface concepts, enumerations, and constrained data types' plus 'smart-reference detection, alias rules, cardinality, INamedConcept usage, bulk creation' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both 'what' (define the four element types and the enumerated capabilities) and 'when' ('Use when authoring or modifying a language's structure model') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural niche phrases users would say ('authoring or modifying a language's structure model', 'concepts', 'structure aspect') but lacks synonyms and common variations beyond the core MPS terminology. Not a 3 because the terms present are natural for the domain; not a 5 because synonym/file-extension-level coverage is absent.	4 / 5
Distinctiveness Conflict Risk	Targets a highly specific MPS-structure-aspect niche with distinct triggers ('structure aspect', 'INamedConcept', 'mps_mcp_alter_structure'), making overlap with other skills minimal.	5 / 5
	Total	19 / 20 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

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