ssr

Guide for using Structural Search and Replace in IntelliJ. Use when creating or modifying SSR inspections or search patterns.

Quality

81%

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

87%

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

The content is lean, concrete, and copy-paste-ready with real XML and explicit commands. Its main weakness is workflow clarity: steps are an implicit bulleted set with one validation checkpoint but no error-recovery feedback loop.

Suggestions

Convert the bullets into a short numbered workflow (read .idea via terminal → edit the XML → configure scope → run InspectionProfileConsistencyTest) so the sequence is explicit.

Add a feedback loop after the test step, e.g. "If InspectionProfileConsistencyTest fails, fix the XML and re-run until it passes before committing."

Dimension	Reasoning	Score
Conciseness	The body is lean bullet guidance plus complete XML examples, with no padding explaining what SSR or XML is; it assumes Claude's competence and every token serves the task. Not 2 because there is no unnecessary explanation to trim.	3 / 3
Actionability	It gives concrete commands ("ls, cat and grep to read directory .idea", "run InspectionProfileConsistencyTest") and complete, copy-paste-ready replaceConfiguration/searchConfiguration XML. Not 2 because the examples are executable and complete rather than pseudocode.	3 / 3
Workflow Clarity	It lists the steps (read .idea, edit XML, configure scope, run the test) and includes a validation checkpoint ("must run InspectionProfileConsistencyTest"), but the sequence is implicit via bullets and there is no error-recovery feedback loop for XML manipulation. Not 3 because of the missing fix-and-retry loop; not 1 because a validation step and the operations are present.	2 / 3
Progressive Disclosure	It is a single self-contained file with no nested references, organized into logical bullets — matching the simple-skill carve-out for skills with no external references. Not 2 because the content is appropriately flat and discoverable rather than a monolithic wall or multi-level indirection.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 cleanly covers both capability and an explicit usage trigger, and carves out a distinctive IntelliJ SSR niche. It is slightly held back by terse, somewhat generic action framing and limited keyword variation.

Suggestions

Replace the generic "Guide for using" framing with concrete actions, e.g. "Create, modify, and scope IntelliJ Structural Search and Replace (SSR) inspections."

Add a few natural trigger variations (e.g. "IntelliJ inspection", "structural find and replace", "SSR pattern") so users phrase the need in more ways.

Dimension	Reasoning	Score
Specificity	"Guide for using Structural Search and Replace" and "creating or modifying SSR inspections or search patterns" name the domain and some concrete actions, but the list is not comprehensive. Not 3 because it leans on a generic "guide for using" framing rather than enumerating multiple specific actions; not 1 because it does name real actions.	2 / 3
Completeness	It states both what it does ("Guide for using Structural Search and Replace in IntelliJ") and an explicit when clause ("Use when creating or modifying SSR inspections or search patterns"). Not 2 because the trigger is explicit rather than implied.	3 / 3
Trigger Term Quality	It includes the full term "Structural Search and Replace", the acronym "SSR", "IntelliJ", and "search patterns" — relevant keywords a user might say, but coverage is somewhat narrow and technical. Not 3 because common variations (e.g. "IntelliJ inspection", "find/replace structurally") are absent; not 1 because the core natural terms are present rather than pure jargon.	2 / 3
Distinctiveness Conflict Risk	"Structural Search and Replace in IntelliJ" is a clear, narrow niche with distinct triggers unlikely to fire for unrelated skills. Not 2 because the IntelliJ + SSR scope is specific enough to avoid overlap with general code-search skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JetBrains/MPS
Path: .agents/skills/ssr/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.