CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-language-analysis

Analyze an MPS language by name — discover concepts, properties, references, children, aspects (editor/constraints/behavior), metadata, and answer type questions (is A a subtype of B, common supertype, expected type of a slot, why a node has its type) with `mps_mcp_query_types`. Use when investigating an unfamiliar language, exploring concept structure, or finding sample nodes to use as templates for JSON blueprints.

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 is dense, tool-specific, and well organized: exact tool/parameter names, a clear analysis workflow with a verification step, and sensible deferral of detail to reference files and companion skills. The dominant defect is that none of the referenced bundle files or scripts are actually present, leaving the progressive-disclosure structure unverifiable and the script instructions unusable.

Suggestions

Ship the referenced bundle files (references/search-concepts.md, references/concept-details.md, scripts/concept_shape.py) in the skill directory, or remove the pointers — as delivered, the bundle contains only SKILL.md and every reference is dangling.

Add one minimal example tool invocation payload (e.g., a `mps_mcp_query_nodes` GET_TYPE or `mps_mcp_query_types` IS_SUBTYPE call with its JSON envelope) so the most common queries are copy-paste ready.

Include a brief error-path note for the analyze-by-name workflow: what to do when the `startingPoint` filter returns nothing, multiple languages match, or a shorthand name cannot be resolved.

DimensionReasoningScore

Conciseness

The body assumes competence (no "what is MPS" padding) and every section is actionable, but the companion-loading boilerplate and the thrice-repeated "in the X skill root after loading that companion skill from the same origin" phrasing could be trimmed to a single stated rule.

4 / 5

Actionability

Concrete tool names with parameter selectors ("startingPoint: My_Language", "sampleOnly: true", "includeInherited: true"), a runnable script with example command and output, and a no-python fallback procedure. Not 5: no example tool-call payloads (e.g., a full `mps_mcp_query_types` invocation envelope) are shown.

4 / 5

Workflow Clarity

"Analyzing a Language by Name" gives a numbered 4-step sequence where step 1 ("Verify Language... This confirms existence and provides the UUID") is a real validation checkpoint, and shorthand names get explicit resolution guidance. Not 5: no error-path guidance beyond step 1 (e.g., what to do when the filter returns nothing or names collide); not penalized further since operations are read-only.

4 / 5

Progressive Disclosure

The Reference Index signals one-level-deep references with clear content descriptions ("Open references/search-concepts.md for the `mps_mcp_search_concepts` matching algorithm..."), but the bundle as shipped contains no `references/` or `scripts/` directories — every referenced path (search-concepts.md, concept-details.md, concept_shape.py) is dangling, so navigation fails as delivered.

3 / 5

Total

15

/

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: concrete third-person capability listing, explicit 'Use when...' triggers, and domain-specific vocabulary that makes mis-triggering unlikely. The only weaknesses are a few missing natural synonyms and minor boundary overlap with companion skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "discover concepts, properties, references, children, aspects (editor/constraints/behavior), metadata, and answer type questions (is A a subtype of B, common supertype, expected type of a slot, why a node has its type)" — with a named tool (`mps_mcp_query_types`), giving comprehensive coverage of the skill's niche in third person.

5 / 5

Completeness

Explicitly answers both what ("Analyze an MPS language by name — discover concepts, properties... answer type questions") and when ("Use when investigating an unfamiliar language, exploring concept structure, or finding sample nodes...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when investigating an unfamiliar language, exploring concept structure, or finding sample nodes to use as templates for JSON blueprints" provides natural trigger phrases, but a few common user synonyms ("typesystem", "inheritance", "structure model") are missing.

4 / 5

Distinctiveness Conflict Risk

"Analyze an MPS language by name" with tool-specific terms carves a clear niche, but type questions like "is A a subtype of B, common supertype" overlap with the delegated `mps-language-inheritance` companion skill, so minor overlap risk with closely related skills remains.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 7 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

JetBrains/MPS

Path

.agents/skills/mps-language-analysis/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.