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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent, lean reference skill: concrete MCP tool calls with parameters, a sequenced workflow with an explicit verification step, and clean section organization. It assumes Claude's competence and provides copy-paste-ready guidance throughout.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean — every line is an actionable instruction or concrete spec (exact tool names, parameter names, ref formats) with no padding explaining what MPS, DSLs, or JSON are, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Names exact MCP tools with their parameters (e.g. `mps_mcp_get_project_structure` with `includeModels: false`, `mps_mcp_get_concept_details` with `l:<uuid>:<languageName>`), exact ref formats, directory globs, and output paths — fully executable, copy-paste-ready guidance.	3 / 3
Workflow Clarity	An 8-step sequenced workflow includes an explicit Verify checkpoint (step 8: confirm reference files exist, blueprint JSON parses, no `.DS_Store`, node refs still resolve) plus a validation step in Quick start, satisfying the 'clear sequence with explicit validation steps' anchor for a model-editing task.	3 / 3
Progressive Disclosure	Content is cleanly split into well-signaled sections (When to Use, Prerequisites, Workflow, Layout, Requirements, Reference Files) with no monolithic wall and no deeply nested references; per the simple-skill scoring note a well-organized skill scores 3 even without external bundle files.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 distinct, but it lacks an explicit 'Use when...' trigger clause and the natural user-facing trigger terms are absent from the description itself (they appear only in the body). Adding a concrete trigger clause would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when ...' clause with natural triggers (e.g. 'Use when bootstrapping or generating a DSL skill, documenting a DSL, or when an existing generated DSL skill under `.agents/skills/*-dsl/` is outdated').

Add colloquial variations users would actually say ('generate DSL skill', 'document this DSL', 'bootstrap DSL skill') into the description, not just the body.

Keep the precise output path and `-dsl` suffix detail — it is what makes the description distinct.

Dimension	Reasoning	Score
Specificity	States concrete actions ('Create or refresh project-local DSL skills under `.agents/skills/<dsl-name>-dsl/`') and names the precise output path and scope, matching the 'lists multiple specific concrete actions' anchor rather than the domain-only level 2.	3 / 3
Completeness	Clearly answers 'what' but 'when' is only implied via the 'after discovering...' precondition; there is no explicit 'Use when...' clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Names a relevant domain ('DSL skills', 'MPS languages') but the natural trigger phrases a user would say (e.g. 'generate DSL skill', 'document this DSL') live in the body, not the description, so common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The MPS/DSL-specific output path and mandatory `-dsl` suffix carve out a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	14 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-dsl-memory/SKILL.md
Commit: 52c9d63

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.