CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-language-analysis

Analyze an MPS language by name — discover concepts, properties, references, children, aspects (editor/constraints/behavior), and metadata. Use when investigating an unfamiliar language, exploring concept structure, or finding sample nodes to use as templates for JSON blueprints.

67

Quality

81%

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

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 a well-structured, actionable, read-only analysis workflow with concrete MCP tool calls and a clear sequence. Its main defect is that the referenced files in the Reference Index are not actually bundled, leaving broken navigation pointers.

Suggestions

Add the missing references/search-concepts.md and references/concept-details.md files to the bundle (or remove the Reference Index section) so the signaled references resolve.

Tighten the intro line and Critical Directives/Related Skills sections to remove redundancy with the frontmatter description.

Add a brief error-recovery note (e.g. what to do if the language is not found or a concept reference is unresolved) to round out the workflow's verification checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's familiarity with MPS terms, but the intro line and the Critical Directives / Related Skills sections have minor redundancy that could be trimmed.

4 / 5

Actionability

Names specific MCP tools (mps_mcp_get_project_structure, mps_mcp_get_concept_details, mps_mcp_query_nodes with FIND_INSTANCES, mps_mcp_query_structure with LIST_CONCEPT_ASPECTS) with concrete parameter guidance (startingPoint, languageRefs, sampleOnly, includeInherited), giving mostly executable direction with minor gaps in full call signatures.

4 / 5

Workflow Clarity

A clear numbered sequence (Verify -> Retrieve -> Extract -> Drill Down) with an existence-confirmation checkpoint in step 1, though it lacks an explicit error-recovery feedback loop; the read-only nature means the destructive-cap does not apply.

4 / 5

Progressive Disclosure

The body is well sectioned and signals two one-level-deep references (references/search-concepts.md, references/concept-details.md) with descriptions, but those files and the references/ directory do not exist in the bundle, so the references are dangling dead ends.

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 strong: third-person, concrete, and explicit about both capability and triggers. Its only weakness is somewhat specialized trigger vocabulary that omits common synonyms and extensions.

DimensionReasoningScore

Specificity

Lists multiple specific concrete outputs ("concepts, properties, references, children, aspects (editor/constraints/behavior), and metadata"), giving comprehensive coverage of what the analysis returns.

5 / 5

Completeness

Explicitly answers both what ("Analyze an MPS language by name — discover...") and when ("Use when investigating an unfamiliar language, exploring concept structure, or finding sample nodes...") with concrete triggers.

5 / 5

Trigger Term Quality

Good natural trigger phrases ("investigating an unfamiliar language", "exploring concept structure", "finding sample nodes... templates for JSON blueprints"), but the vocabulary is specialized and lacks synonym/file-extension variants.

4 / 5

Distinctiveness Conflict Risk

Clear niche ("MPS language", "JSON blueprints", "concept structure") with distinct, specialized triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation14 / 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: 2 missing

Warning

Total

14

/

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.