CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-aspect-intentions

Use when defining or editing MPS intentions (the Alt+Enter context-action aspect) — adding `IntentionDeclaration` roots, parameterized or surround-with variants, description/isApplicable/execute blocks, child-filter functions, factory-initialized AST splicing, or debugging why an intention is not offered. Lives in the language's `intentions` model and uses `jetbrains.mps.lang.intentions`.

70

Quality

87%

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

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

A well-structured, token-efficient overview that points cleanly to per-topic reference files with explicit navigation guidance. The main weakness is that the referenced bundle files are absent from the reviewed directory, leaving the disclosure paths unverified.

Suggestions

Ship the referenced files under references/ (blocks-and-parameters.md, execute-idioms.md, factory-initialized.md, parameterized-intentions.md, surround-and-child-filter.md, json-blueprints.md, common-failures.md) so the signaled navigation actually resolves.

Add an explicit 'if check_root_node_problems reports errors, fix and re-run validation before rebuilding' retry step to make the validation feedback loop concrete.

Inline one minimal IntentionDeclaration JSON blueprint in the workflow so the core path is executable without opening a reference file.

DimensionReasoningScore

Conciseness

Lean and dense throughout: a single useful intro sentence, then compact directives, a numbered workflow, a parameter table, and a reference index — no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Names concrete MCP tools with parameters (`mps_mcp_insert_root_node_from_json`, `mps_mcp_apply_intention(nodeReference=..., intentionId=...)`, `mps_mcp_check_root_node_problems`) and exact syntax (`n as C`, `:eq:`), but the full copy-paste JSON blueprints live in referenced files rather than inline.

4 / 5

Workflow Clarity

A clear 6-step Common-Path Workflow with an explicit validation checkpoint ('Validate (mps_mcp_check_root_node_problems), rebuild the language, exercise via Alt+Enter'), though an explicit fix-and-revalidate retry loop is implied rather than spelled out.

4 / 5

Progressive Disclosure

Excellent one-level-deep structure with a Reference Index that signals when to open each file and what it contains, but the referenced references/*.md files are not present in the bundle, so navigation cannot be verified as resolving.

4 / 5

Total

17

/

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.

A highly specific, well-triggered description that clearly scopes the MPS intentions aspect and distinguishes it from neighboring skills. The only minor gap is keyword synonym coverage for natural trigger terms.

Suggestions

Add a couple of natural synonyms users might say (e.g. 'quick fix', 'Alt+Enter refactoring', 'intention popup') alongside the technical terms to broaden trigger matching.

Consider mentioning 'preview' explicitly since the body calls it out as a canonical intention category.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding IntentionDeclaration roots', 'parameterized or surround-with variants', 'description/isApplicable/execute blocks', 'child-filter functions', 'factory-initialized AST splicing', 'debugging why an intention is not offered' — giving comprehensive coverage of the capability surface.

5 / 5

Completeness

Explicitly answers both what (defining/editing intentions and the listed authoring tasks) and when ('Use when defining or editing MPS intentions ... or debugging why an intention is not offered') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers for the domain ('MPS intentions', 'Alt+Enter context-action', 'surround-with', 'debugging why an intention is not offered') but leans on technical jargon and omits common synonyms like 'quick fix' or 'refactoring popup'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — the MPS intentions aspect in `jetbrains.mps.lang.intentions` — distinct from sibling aspects like actions, constraints, or editor menus, with minimal overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

13

/

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.