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

93%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.

The body is lean and highly actionable, giving exact file paths, complete XML examples, and a mandatory post-change validation step. The only gap is the absence of an explicit failure-recovery loop around the consistency test.

Suggestions

Add a brief recovery instruction after the consistency-test step, e.g. 'If the test fails, review the XML against the examples above, fix the offending configuration, and re-run the test.'

Dimension	Reasoning	Score
Conciseness	Lean bullet guidance with no explanation of concepts Claude already knows; the two XML blocks earn their place as concrete reference patterns rather than padding.	5 / 5
Actionability	Provides copy-paste-ready XML examples (replaceConfiguration, searchConfiguration, inspection_tool scopes), the exact inspection file path, and an exact test command, covering the common SSR cases.	5 / 5
Workflow Clarity	A clear single-purpose flow with an explicit validation checkpoint ('You must run InspectionProfileConsistencyTest after changing xml files'), but the recovery loop on test failure is not spelled out.	4 / 5
Progressive Disclosure	Self-contained, short, well-organized bullet structure with no nested references; the simple-skill exception applies since no external files are warranted at this size.	5 / 5
	Total	19 / 20 Passed

Description

70%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.

The description is clear, concise, and properly structured with both a 'what' and an explicit 'Use when' trigger clause. It is specific to the IntelliJ SSR niche, though the action list and trigger synonyms could be richer.

Suggestions

Expand the action list to cover replace configurations and not just inspections/search patterns, e.g. 'creating or modifying SSR inspections, search patterns, and replace templates'.

Add user-natural synonyms to the trigger clause such as 'structural find-and-replace', 'inspection templates', or '.idea inspection XML'.

Dimension	Reasoning	Score
Specificity	Names the domain plus two concrete actions ('creating or modifying SSR inspections or search patterns'), but coverage is thin with no mention of replace configurations or other SSR capabilities.	3 / 5
Completeness	Clearly states what the skill does ('Guide for using Structural Search and Replace in IntelliJ') and when to use it ('Use when creating or modifying SSR inspections or search patterns'), with the 'when' explicit but not maximally concrete.	4 / 5
Trigger Term Quality	Good keyword coverage including 'Structural Search and Replace', 'SSR inspections', 'search patterns', and 'IntelliJ', though common synonyms users might say are missing.	4 / 5
Distinctiveness Conflict Risk	The IntelliJ SSR niche is mostly distinct from generic code skills, with only minor overlap risk against general refactoring or IDE-inspection skills.	4 / 5
	Total	15 / 20 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: c74b207

Reviewed: 3 days 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.