CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-aspect-actions

Use when defining or editing MPS node factories (the "actions" aspect) — `NodeFactories` roots, per-concept `NodeFactory` setup functions that initialize a freshly created node and optionally copy data from a replaced `sampleNode`, plus the actions aspect's `CopyPasteHandlers` and `PasteWrappers` roots. Reach for this skill when a substitution, side transform, completion replacement, or `add new initialized(...)` should preserve fields from the node it is replacing, or when defaults set in a constructor are not enough.

71

Quality

89%

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

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 high-quality reference body: specific, well-organized, and action-oriented with real tooling. The main gaps are an implicit (rather than explicit) validation feedback loop and code patterns that lean on placeholders, plus the referenced `references/*.md` bundle files are not actually present alongside the skill.

Suggestions

Make the validation feedback loop explicit in the workflow: after `mps_mcp_check_root_node_problems`, add 'If problems are reported, fix them and re-check before rebuilding.'

The body cites six `references/*.md` files (e.g. `references/node-factories-and-triggers.md`, `references/setup-function-bodies.md`) but no `references/` directory ships with the skill — add the bundle so the signaled navigation actually resolves.

Replace a few of the `<Concept>`/`<prop>` placeholders in the setup-body pattern with one fully concrete worked example so the common case is copy-paste ready.

DimensionReasoningScore

Conciseness

Dense and lean throughout — every line carries specifics (tool names, FQNs, exact rules) with no padding explaining what MPS or a node factory is; tokens consistently earn their place.

5 / 5

Actionability

Concrete, executable guidance with named MCP tools (`mps_mcp_insert_root_node_from_json`, `mps_mcp_update_node`, `mps_mcp_check_root_node_problems`) and a real code pattern, but body snippets use placeholders (`<Concept>`, `<prop>`) and defer some detail to reference files, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 5-step Common-Path Workflow with an explicit validation step (`mps_mcp_check_root_node_problems` + rebuild), but the validate→fix→re-validate feedback loop is implied rather than spelled out.

4 / 5

Progressive Disclosure

Well-structured overview with clearly signaled one-level-deep references and a Reference Index that tells the reader exactly when to open each `references/*.md` file; navigation is easy to follow as written.

5 / 5

Total

18

/

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, specific description that clearly states both capability and trigger conditions for a well-scoped MPS niche. It is slightly jargon-heavy in its trigger terms, which keeps trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — defining/editing `NodeFactories` roots, per-concept `NodeFactory` setup functions that initialize nodes and copy data from `sampleNode`, plus `CopyPasteHandlers` and `PasteWrappers` roots — giving comprehensive coverage of the aspect's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (node factories, setup functions, copy/paste handlers) and 'when' via two trigger clauses ('Use when defining or editing...', 'Reach for this skill when a substitution, side transform...').

5 / 5

Trigger Term Quality

Good coverage of natural domain triggers ('substitution', 'side transform', 'completion replacement', 'add new initialized(...)'), but the phrasing leans heavily on MPS jargon and omits some common synonyms a user might say, stopping short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear, narrow niche (the MPS 'actions' aspect) with distinctive triggers and no realistic overlap with unrelated skills.

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: 10 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.