CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-quotations

Use when writing or debugging MPS quotations and anti-quotations — "node literals" that create SNode trees inline in behavior, typesystem, intentions, generator, and other model code. Covers heavy quotations (`Quotation`, `<...>`), light quotations (`NodeBuilder`, constructor-style for bootstrapping), and the four anti-quotation varieties: child (`%(...)%`), list (`*(...)*`), reference (`^(...)^`), property (`$(...)$`). Reach for this skill whenever the task involves splicing runtime values into quoted node trees or choosing between heavy and light quotations.

Quality

93%

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

86%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 reference skill: critical MPS-specific gotchas are surfaced inline, the workflow is concrete and validated, and detailed material is cleanly deferred to clearly-signaled reference files. The main improvement opportunities are trimming the companion-loading and Related Skills meta-content and closing the validate→fix→re-validate loop.

Suggestions

Trim the 'Loading companion skills' paragraph to the one sentence that applies to the current host (the rest is generic loader-resolution policy), and shorten Related Skills entries to name-only with a few-word hook.

Extend the workflow's final step into an explicit feedback loop: after fixing reported problems (e.g. adding a missing used language), re-run `mps_mcp_check_root_node_problems` and only proceed when it reports no problems.

DimensionReasoningScore

Conciseness

The body is dense with MPS-specific facts Claude would not know ("Quotations do not call behavior constructors", the ListAntiquotation placeholder constraint, the 2019.2 `initValue` migration), but the "Loading companion skills" paragraph (~120 words of loader-resolution meta-process) and the seven annotated Related Skills entries could each be trimmed without losing task-relevant information. Not 5: those sections are over-explanation relative to the quotation task itself; not 3: the padding is minor and most tokens earn their place.

4 / 5

Actionability

Guidance is fully executable for an IDE-manipulation domain: exact editor actions ("type `<` in an expression position to insert a `Quotation`", type `%`/`*`/`^`/`$` in the appropriate cell), copy-paste-ready MCP tool names (`mps_mcp_insert_root_node_from_json`, `mps_mcp_check_root_node_problems`), the exact used-language FQN and UUID, and a decision table covering the common cases. Not 4: there are no gaps in the concrete guidance; per the rubric's instruction-skill note, absence of code blocks is not penalized when the instructions are this specific.

5 / 5

Workflow Clarity

The Common-Path Workflow is a clear 5-step sequence with an explicit validation checkpoint ("Validate with `mps_mcp_check_root_node_problems`; rebuild the host language if needed") and the Critical Directives explain the most common failure mode (missing used-languages) with its fix. Not 5: there is no explicit re-validate-after-fixing loop (the "rebuild if needed" remedy lacks a "then re-check before proceeding" step); not 3: validation is explicit and present, with a named recovery action.

4 / 5

Progressive Disclosure

The Reference Index is the model pattern: eleven one-level-deep references, each signaled with "Open `references/X.md` when..." plus a content summary, covering every sub-topic; the body keeps only the overview, critical directives, and workflow inline. Not 4: navigation is unambiguous, references are one level deep, and content is appropriately split. (No bundle files were present in the reviewed directory, so this scores the body's structure per the rubric guideline.)

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: explicit dual "Use when" triggers, a clear statement of what the skill covers, comprehensive enumeration of all quotation and anti-quotation forms with their syntax, and third-person voice throughout. Dense with information rather than padded, with natural trigger terms for the MPS domain.

DimensionReasoningScore

Specificity

Multiple concrete actions are listed — "writing or debugging MPS quotations and anti-quotations", "splicing runtime values into quoted node trees", "choosing between heavy and light quotations" — and coverage is comprehensive across the domain (heavy `Quotation` `<...>`, light `NodeBuilder`, and all four anti-quotation varieties with their syntax). Not 4: there are no coverage gaps; every sub-form of the topic is named, matching the comprehensive anchor.

5 / 5

Completeness

Both questions are answered explicitly: the "what" ("node literals that create SNode trees inline in behavior, typesystem, intentions, generator, and other model code") and the "when" ("Use when writing or debugging..." plus "Reach for this skill whenever the task involves splicing runtime values..."). Not 4: the "when" is not merely present but concrete and doubly stated with trigger phrases.

5 / 5

Trigger Term Quality

Natural domain terms an MPS user would actually say are comprehensively covered, including a synonym ("node literals"), concrete syntax forms (`%(...)%`, `*(...)*`, `^(...)^`, `$(...)$`), and specific concept names (`Quotation`, `NodeBuilder`, `SNode`). Not 4: no commonly-used variation of the trigger vocabulary is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (MPS quotation/anti-quotation authoring) with distinct, domain-specific triggers, and would not fire for generic model-manipulation or aspect-specific tasks. Not 4: the trigger vocabulary (quotations, antiquotations, node literals, splicing into quoted trees) has minimal overlap even with closely related MPS skills.

5 / 5

Total

20

/

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: 17 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

JetBrains/MPS

Path

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