CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mps-dsl-memory

Create or refresh project-local DSL skills under `.agents/skills/<dsl-name>-dsl/` for one or more MPS languages after discovering concepts, sandbox examples, JSON blueprints, references, or gotchas.

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.

The body is a dense, highly actionable eight-step workflow with concrete MCP tool names, ref formats, a copy-paste shell command, and explicit dry-run validation with fix-and-retry feedback loops. The main weaknesses are the over-packed run-on paragraph in step 8 and the absence of any reference-file split for the skill itself, leaving detail inline that would fit better in a reference file.

Suggestions

Move the dry-run/temp-directory mechanics of workflow step 8 (server temp-dir restriction, inline content limit, copy-then-pass workaround, hollow-descriptor diagnosis) into a one-level-deep reference file such as references/dry-run.md, keeping a short 'dry-run every blueprint, fix the shipped file and retry' instruction in the main step.

Break the remaining step 8 text into sub-bullets or a short checklist so verification, failure handling, and cross-references are scannable instead of a single paragraph.

Move the generated-skill 'Reference Files' descriptions alongside the 'Generated Skill Layout' tree so the file listing and per-file contents are in one place.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no explanations of what MPS or DSLs are, and every tool name and gotcha is project-specific knowledge Claude would not have. Not 5: workflow step 8 is an over-packed run-on paragraph that mixes verification, temp-directory mechanics, inline-content limits, a shell snippet, failure policy, and a cross-reference, and could be tightened or split.

4 / 5

Actionability

Quotes concrete tool calls ('Call `mps_mcp_get_project_structure` with `includeModels: false`', 'mps_mcp_insert_root_node_from_json with `dryRun: true`'), exact ref formats ('l:<uuid>:<languageName>'), a copy-paste shell snippet ('d="${TMPDIR:-/tmp}/<dsl-name>-blueprints"; mkdir -p "$d"; cp ...'), a layout tree, and the blueprint JSON shape ('properties:[{name,value}]'), not a map'). Not 4: the guidance is fully executable with placeholders only where a generator skill cannot avoid them.

5 / 5

Workflow Clarity

The 8-step workflow (discover → scope → examples → concepts → sample → generate → cross-link → verify) is clearly sequenced with an explicit verification step that includes dry-run validation and a fix-and-retry feedback loop ('When a dry run fails, fix the shipped file, not only the inline text or the temp copy, and dry-run again from the fixed file'). Not 4: checkpoints are explicit, not merely present.

5 / 5

Progressive Disclosure

Clear section headers (When to Use, Prerequisites, Workflow, Generated Skill Layout, Requirements, Reference Files) make the body easy to navigate, and the generated-skill reference layout is well specified. Not 5: the skill itself ships no reference files, and step 8's dry-run/temp-directory mechanics are inlined in the main workflow where a one-level-deep reference file would fit better; not 3 because structure and signaling are otherwise good.

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.

The description is specific and distinctive, naming concrete actions, artifacts, and an exact output path within a well-defined MPS niche. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness at 3 and leaves natural invocation phrases out of the description itself.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks to bootstrap, generate, or refresh a DSL skill for an MPS language, or after exploring a DSL whose structure should be persisted for future sessions.'

Surface the natural trigger phrases already listed in the body ('bootstrap DSL skill', 'generate DSL skill', 'document this DSL') into the description itself so users' phrasing matches the skill's description.

Mention the outcome benefit ('persist your findings for future sessions') in the description so users searching for 'remember this DSL' style goals find the skill.

DimensionReasoningScore

Specificity

Quotes 'Create or refresh project-local DSL skills under `.agents/skills/<dsl-name>-dsl/`' and 'discovering concepts, sandbox examples, JSON blueprints, references, or gotchas' — multiple concrete actions plus concrete artifacts and an exact output location, comprehensively covering the skill's purpose. Not 4: there are no minor gaps in what the skill does.

5 / 5

Completeness

The 'what' is clear (create/refresh project-local DSL skills for MPS languages), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'after discovering...' describes inputs rather than when to invoke the skill, capping completeness at 3 per the judging guidelines. Not 4: the 'when' is not merely implicit-unspecific, it is absent.

3 / 5

Trigger Term Quality

'MPS languages', 'DSL skills', 'JSON blueprints', and 'gotchas' are terms the target audience naturally says, giving good keyword coverage. Not 5: natural invocation phrases like 'bootstrap', 'generate', or 'document this DSL' appear only in the body's When to Use section, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

Quotes 'project-local DSL skills under `.agents/skills/<dsl-name>-dsl/` for one or more MPS languages' — a clear niche with distinct vocabulary (MPS, DSL, blueprints, sandbox) and minimal conflict risk with any other skill. Not 4: no meaningful overlap risk even with closely related skills.

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

Warning

Total

14

/

16

Passed

Repository

JetBrains/MPS

Path

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