CtrlK
BlogDocsLog inGet started
Tessl Logo

mps-ide-plugin

Use when authoring or modifying MPS IDE plugins — code that integrates with the MPS / IntelliJ host IDE shell. Covers ActionDeclaration, ActionGroupDeclaration, ToolDeclaration/TabbedToolDeclaration (dockable tool windows), KeymapChangesDeclaration (shortcuts), PreferencesComponentDeclaration (settings pages), EditorTab+Order (concept editor tabs), InterfaceGroup (bootstrap wrappers around external groups), NonDumbAwareActions, IdeaConfigurationXml, ApplicationPluginDeclaration/ProjectPluginDeclaration/StandalonePluginDescriptor (lifecycle hooks). Uses jetbrains.mps.lang.plugin and jetbrains.mps.lang.plugin.standalone. Trigger terms: action group, tool window, menu item, MainMenu, EditorPopup, NodeActions, ModelActions, ModuleActions, ProjectViewPopupMenu, MPS plugin solution, ActionInstance, ModificationStatement, DataKey, MPSCommonDataKeys, MPSDataKeys, dumb-aware, project.tool<...>, project.preferenceComponent<...>, application plugin<...>, project plugin<...>.

74

Quality

92%

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.

An exemplary reference skill body: dense, actionable, well-structured, with a validated multi-step workflow and clean one-level-deep progressive disclosure to verified bundle files.

DimensionReasoningScore

Conciseness

Lean and information-dense with no padding: it never explains basics Claude knows (what MPS is, what a tool window is) and every line earns its place with specific tool names, concept FQNs, or directives.

3 / 3

Actionability

Provides concrete, executable guidance — specific MCP tool calls (mps_mcp_insert_root_node_from_json, mps_mcp_search_root_node_by_name, mps_mcp_check_root_node_problems), real example nodes/models, and exact field lists — actionable without being mere description.

3 / 3

Workflow Clarity

The 8-step Common-Path Workflow is clearly sequenced with an explicit validation checkpoint (step 8: mps_mcp_check_root_node_problems) and a rebuild + Reload All feedback loop, complemented by the common-failures reference for error recovery.

3 / 3

Progressive Disclosure

The body is an overview that points to 13 real, one-level-deep reference files, each clearly signaled in the Reference Index with "Open references/X when …" plus a summary of contents, with detail appropriately pushed into the bundle.

3 / 3

Total

12

/

12

Passed

Description

85%

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 highly specific, well-scoped description that clearly states both what it does and when to use it for a narrow expert domain. Its one weakness is a trigger-term list padded with internal identifiers over natural user phrasing.

Suggestions

Trim internal identifiers (MPSCommonDataKeys, MPSDataKeys, ModificationStatement, DataKey, project.tool<…>) from the trigger-terms list and keep the natural user-facing phrases (action group, tool window, menu item, settings page, shortcut, editor tab).

Add a few more common natural variations such as "add a menu item", "tool window", "keyboard shortcut", and "settings page" to broaden natural-keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete concepts mapped to their function — "ActionDeclaration, ActionGroupDeclaration, ToolDeclaration/TabbedToolDeclaration (dockable tool windows), KeymapChangesDeclaration (shortcuts), PreferencesComponentDeclaration (settings pages)" — a comprehensive, concrete enumeration.

3 / 3

Completeness

Opens with an explicit "Use when authoring or modifying MPS IDE plugins" trigger and pairs it with a comprehensive "what" via the Covers… list plus a dedicated Trigger terms clause.

3 / 3

Trigger Term Quality

Natural terms like "action group, tool window, menu item" are present, but the trigger list is dominated by internal identifiers (MPSCommonDataKeys, ModificationStatement, DataKey, project.tool<…>) a user would not naturally say, so common-variation coverage is partial.

2 / 3

Distinctiveness Conflict Risk

Targets a narrow MPS IDE-shell niche with distinct concept identifiers (ActionDeclaration, InterfaceGroup, StandalonePluginDescriptor) that are unlikely to fire for any other skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.