CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-aspect-dataflow

Use when defining or debugging MPS dataflow builders for a concept — control/data flow declarations that drive reachability analysis and variable-use checking. Covers DataFlowBuilderDeclaration, BuilderBlock, emit instructions (code for, jump, ifjump, label, read, write, ret, mayBeUnreachable), positions (AfterPosition, BeforePosition, LabelPosition), the jetbrains.mps.lang.dataFlow language, the NodeParameter implicit, BL+smodel usage inside builder bodies, and IBuilderMode for advanced analyses such as nullable/non-null tracking.

78

Quality

100%

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

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 exemplar reference skill: concise but dense, immediately actionable with named tools and exact identifiers, a clearly sequenced workflow with validation, and clean progressive disclosure to six well-signaled one-level references. Content appropriately split between the overview and bundle files.

DimensionReasoningScore

Conciseness

Lean and dense with expertise: every section earns its tokens (mental model, critical directives, numbered workflow, reference index) and assumes Claude's competence, avoiding generic explanations of what MPS or dataflow is.

3 / 3

Actionability

Concrete and actionable throughout: named MCP tools (mps_mcp_create_model, mps_mcp_check_root_node_problems), exact aspect-ID spelling ('dataFlow', case-sensitive), and a numbered workflow with specific emit-statement types and positions.

3 / 3

Workflow Clarity

Clear six-step sequence with an explicit validation checkpoint (step 6: 'Validate with mps_mcp_check_root_node_problems') and a debugging feedback path (inspect a known-good builder with mps_mcp_print_node deep:true) for error recovery.

3 / 3

Progressive Disclosure

Well-structured overview that points to six one-level-deep references, each with a clear 'open when...' trigger and verified bundle files that match the referenced paths (concept-catalog.md, json-patterns.md, rules-and-pitfalls.md, etc.).

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, comprehensive, and well-targeted: it states both what the skill does and when to use it, with concrete MPS-specific terminology and natural trigger phrasing. It is slightly dense but earns its tokens through specificity rather than fluff.

DimensionReasoningScore

Specificity

Lists many concrete actions and artifacts: 'defining or debugging MPS dataflow builders', 'reachability analysis and variable-use checks', plus a long enumerated set of concrete emit instructions, positions, and concepts.

3 / 3

Completeness

Explicitly answers both what (control/data flow declarations, specific constructs and instructions) and when ('Use when defining or debugging MPS dataflow builders for a concept').

3 / 3

Trigger Term Quality

Includes natural trigger phrasing ('Use when defining or debugging MPS dataflow builders for a concept') and surfaces user-recognizable terms like 'dataflow builders', 'reachability analysis', 'variable-use checking', and 'nullable/non-null tracking'.

3 / 3

Distinctiveness Conflict Risk

Highly specific MPS dataflow niche with named language and constructs, clearly distinct from sibling skills like typesystem or behavior aspects; unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation14 / 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

Total

14

/

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.