CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-console

Run or generate MPS Console code and `jetbrains.mps.lang.smodel.query` queries in MPS intentions, behavior, actions, generators, and BaseLanguage. Covers console commands, result printers, IDE operations, scripts, scoped node/model/module queries, and inserting, reading, recalling, or running commands through MPS MCP tools.

Quality

84%

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

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

An exemplary reference-skill body: dense with non-obvious, verifiable domain facts, fully actionable tool call sequences with parameters, and genuinely strong workflow design — polling loops with terminal states, a pre-run model-checker validation step, and a deliberate safety choice between refactor and forEach for batch mutation. Its only deductions are minor repetition of the reference-validity caveat and the three referenced files being absent from the provided bundle, which leaves progressive disclosure unverified beyond the document itself.

DimensionReasoningScore

Conciseness

Efficient and information-dense: nearly every line carries non-obvious domain facts ("The reference is only valid until the next console interaction", "refactor ... pops a modal confirmation dialog", "preview is ... cut at 200 characters") and it assumes competence — no padding explaining what MPS or an IDE is. Not a 5: the reference-validity caveat is repeated across items #4, #5, and #8, and several parenthetical asides in "Ways this skill gets used" could be tightened or pushed to a reference file.

4 / 5

Actionability

Fully executable guidance throughout: exact MCP tool names with parameters and formats ("mps_mcp_get_console_history(includeResponses = true, limit = 2)", "mps_mcp_print_node(nodeReference = ..., format = \"PLAIN TEXT\")"), runnable surface-syntax examples ("#instances(Ingredient).select({~it => it.name; })"), and a decision table mapping value shapes to printed output and response nodes. The 'shape the query for what you need back' section gives copy-ready patterns for both values and node references, plus an explicit anti-pattern.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation and feedback loops: the output-reading procedure is a numbered poll loop with terminal conditions ("finished when the last entry is a kind:response", "still running ... or it printed nothing", "call again a few times, then stop waiting") and a previewComplete check before trusting or re-printing; way #8 provides pre-run checker validation; and the refactor-vs-forEach directive is an explicit confirmation checkpoint for destructive batch mutation ("when the user asks you to create and run it yourself ... prefer forEach — refactor would ... stall on the dialog"). This matches the anchor of clear sequence with explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

Good structure: a dedicated Reference Index clearly signals three one-level-deep references with accurate content summaries ("references/console-languages.md for the full console command-language reference", "references/smodel-query.md for the ... with statement", "references/mcp-insertion.md for mps_mcp_insert_console_command_from_json"), plus inline pointers in the relevant sections and a Related Skills map. Not a 5: those three referenced files are not present in the provided bundle, so navigation cannot be verified end-to-end, and the body carries more operational detail (the full printing/value-shape table and the #4–#8 MCP caveats) than a pure overview would.

4 / 5

Total

18

/

20

Passed

Description

75%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 highly specific, well-scoped description in third person that comprehensively states what the skill does with distinct, niche-appropriate triggers. Its one real weakness is the absence of an explicit 'Use when...' clause, which leaves the triggering conditions implied and caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to run or build MPS Console commands, find nodes/instances/usages in an MPS project, or insert/inspect/run console commands via MPS MCP tools."

Include the natural trigger terms users actually say for this skill's headline uses: "find usages", "instances", and "search/query nodes" alongside the existing capability list.

Consider naming the Console tool window and Model Checker contexts (e.g. "Tools ▸ Console") as additional natural entry points users mention.

DimensionReasoningScore

Specificity

Multiple specific concrete actions with comprehensive coverage: "Run or generate MPS Console code and `jetbrains.mps.lang.smodel.query` queries", plus a second sentence enumerating "console commands, result printers, IDE operations, scripts, scoped node/model/module queries, and inserting, reading, recalling, or running commands through MPS MCP tools". It matches the anchor 'lists multiple specific concrete actions; comprehensive coverage' — no vague filler and no missing capability area relative to the body.

5 / 5

Completeness

The 'what' is clear and detailed (run/generate console code and smodel queries; covers commands, printers, scoped queries, MCP insertion/recall/run), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the "in MPS intentions, behavior, actions, generators, and BaseLanguage" phrase states where the code lives, only weakly implying when to load the skill. Per the guideline, a missing Use-when clause caps completeness at 3; it is not a 4 because the when-guidance is implied rather than stated.

3 / 5

Trigger Term Quality

Good keyword coverage of terms an MPS user would naturally say: "MPS Console", "console commands", "queries", "intentions, behavior, actions, generators, BaseLanguage", "node/model/module queries", "MPS MCP tools". Not a 5: a few natural terms users say for this skill's headline uses are missing — e.g. "find usages", "instances", or "search nodes", and there are no synonym variations beyond the single pass.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: "MPS Console code", "jetbrains.mps.lang.smodel.query", and console-specific MCP operations ("inserting, reading, recalling, or running commands through MPS MCP tools") are unambiguous and would not fire for sibling skills like mps-model-manipulation or mps-node-editing. Overlap with those siblings is minimal because the description consistently frames everything around the Console and its MCP tools.

5 / 5

Total

17

/

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

Warning

Total

14

/

16

Passed

Repository

JetBrains/MPS

Path

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