CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-lang-core-xml

Use when authoring XML documents as MPS root nodes or building XML-generating generator templates with jetbrains.mps.core.xml — covers XmlFile, XmlDocument, prolog (XML declaration, DOCTYPE, processing instructions, comments), elements, attributes, CDATA, entity references, and macro attachment via the smodelAttribute role for templates that emit XML output.

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

68%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 lean, knowledge-dense body with precise directives and a clear workflow, but two structural weaknesses hold it back: the workflow lacks the error-recovery feedback loop the rubric requires for XML manipulation, and all four reference files the skill depends on for its detailed material (especially the JSON blueprints) are missing from the bundle.

Suggestions

Add an explicit feedback loop after step 6: when `mps_mcp_check_root_node_problems` reports problems, fix them via the MCP node tools and re-run the check before proceeding — this satisfies the validate→fix→retry requirement for XML manipulation workflows.

Ship the four referenced files (concept-catalog, json-blueprints, rules-and-pitfalls, language-dependencies) in the bundle, or inline a minimal working JSON blueprint for the common single-root-document case so the workflow is executable even if references are unavailable.

Consider a short inline example of one complete XmlFile JSON structure (root + element + attribute) so the concept/role directives have an immediately visible concrete referent.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: directives are terse one-liners carrying non-obvious knowledge ("XmlText / XmlSingleLineText use the property `value`. `XmlTextValue` … uses the property `text`"), with no padding or explanation of concepts Claude already knows. The companion-loading paragraph is the only candidate for trimming, but it is tight operational policy — this matches the every-token-earns-its-place anchor.

5 / 5

Actionability

The body gives concrete, executable guidance — exact concept names, child roles (`document`, `rootElement`, `smodelAttribute`), the validation tool `mps_mcp_check_root_node_problems`, and exact languages to add — which is strong for an instruction-only reference skill. However, the copy-paste JSON blueprint examples that make the workflow fully executable are deferred to `references/json-blueprints.md`, so the body stops short of fully executable payloads. Not 3 because nothing is vague or pseudocode; not 5 because the concrete example material is entirely external to the body.

4 / 5

Workflow Clarity

The 6-step common path is clearly sequenced and ends with an explicit validation step ("Validate with `mps_mcp_check_root_node_problems`"), but there is no feedback loop — no instruction on what to do when the check reports problems, or to re-validate after fixes. Per the rubric's cap, XML/document manipulation without an explicit validate→fix→retry loop cannot score above 3; it is not 2 because the sequence is complete and a concrete checkpoint is present.

3 / 5

Progressive Disclosure

The Reference Index is excellently signaled — each of the four entries has an "open when …" trigger and one-level-deep paths — but none of the referenced files (`references/concept-catalog.md`, `references/json-blueprints.md`, `references/rules-and-pitfalls.md`, `references/language-dependencies.md`) exist in the bundle; there is no references/ directory at all. The promised navigation structure is broken, leaving four dead links, which lands it at the broken/minimal-structure anchor rather than 3 (where references exist but are poorly signaled).

2 / 5

Total

14

/

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 strong, highly specific description: it states concrete capabilities, uses third person, and opens with an explicit 'Use when' clause containing accurate, niche-appropriate trigger phrases. The only weakness is minor — it could add natural synonyms/file extensions like '.xml' to broaden trigger matching.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — "authoring XML documents as MPS root nodes", "building XML-generating generator templates", "macro attachment via the smodelAttribute role" — and comprehensively enumerates the covered constructs ("XML declaration, DOCTYPE, processing instructions, comments), elements, attributes, CDATA, entity references"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both: the "Use when authoring XML documents as MPS root nodes or building XML-generating generator templates with jetbrains.mps.core.xml" clause gives concrete triggers, and "covers XmlFile, XmlDocument, prolog … CDATA, entity references, and macro attachment" clearly states what it does. Clearly matches the anchor-5 example pattern of action list followed by explicit 'Use when' triggers.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases like "authoring XML documents" and "building XML-generating generator templates" plus domain terms (XmlFile, DOCTYPE, CDATA, generator templates), but a few natural terms are missing — no file-extension trigger (".xml files") or output-file phrasing beyond "emit XML output". Not score 5 because synonym/extension coverage is not comprehensive; not 3 because the included terms are exactly what an MPS user would say for this task.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — scoped to the specific MPS language "jetbrains.mps.core.xml", MPS root nodes, and generator-template macro attachment — minimizing conflict risk with generic XML or document skills. Adjacent MPS companion skills (generator, textgen) cover different layers, so overlap is minimal; not 4 because the named language and smodelAttribute trigger leave essentially no ambiguity.

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.

Validation — 13 / 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: 4 missing

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

13

/

16

Passed

Repository

JetBrains/MPS

Path

.agents/skills/mps-lang-core-xml/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.