CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ssr

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/ssr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, highly actionable skill that gives copy-paste-ready XML templates, exact file locations, and a required verification test with no wasted tokens. Its main weaknesses are an implied rather than sequenced workflow, a missing error-recovery loop around the validation test, and a small inconsistency in how the scope configuration's UUID references the replace configuration.

Suggestions

Sequence the steps as an explicit numbered workflow (read idea_default.xml with terminal tools, add the configuration under <inspection_tool class="SSBasedInspection">, configure the inspection scope, run InspectionProfileConsistencyTest) instead of leaving the order implied.

Add a feedback loop for the validation step: instruct to fix any XML issues the InspectionProfileConsistencyTest reports and re-run it until it passes before proceeding.

Resolve the UUID linkage: either add a uuid attribute to the replaceConfiguration example or explain where the class value in the inspection_tool scope configuration comes from, and include the exact command used to run InspectionProfileConsistencyTest.

DimensionReasoningScore

Conciseness

The body is lean with zero explanations of known concepts ('You must use terminal search...', the two XML templates, the test instruction all carry operational value). Minor trimmables exist: the note 'This node should be located under <inspection_tool class="SSBasedInspection" tag' is duplicated after both examples and 'Here is an example of a...' phrasing is padded, keeping it below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete, executable guidance throughout: the exact path '.idea/inspectionProfiles/idea_default.xml', two complete copy-paste XML templates, and a named verification test. Minor gaps keep it from 5: no command for running InspectionProfileConsistencyTest, and the scope section says 'class is UUID of the created replace configuration' while the replaceConfiguration example has no uuid attribute, leaving the linkage unclear.

4 / 5

Workflow Clarity

All workflow components are present (read the profile file, add configurations under the SSBasedInspection tag, configure scope, run InspectionProfileConsistencyTest) but never sequenced into an ordered process. Validation is stated ('You must run InspectionProfileConsistencyTest after changing xml files') but there is no fix-and-retry feedback loop, and the rubric caps XML-manipulation skills without feedback loops at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the ~55-line single-file layout is the right choice for this scope, with bullet-level organization that is easy to navigate. It falls short of 5 because there are no section headers and the duplicated node-placement note could be consolidated into one place.

4 / 5

Total

15

/

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.

A concise third-person description with an explicit 'Use when' trigger that includes both the full feature name and its SSR acronym, giving it good discoverability and a distinct niche. Its main limitation is the vague 'what' portion ('Guide for using'), which does not state the concrete capabilities the skill provides.

DimensionReasoningScore

Specificity

Names the domain ('Structural Search and Replace in IntelliJ') and two concrete actions ('creating or modifying SSR inspections or search patterns'), matching the 1-2-concrete-actions anchor. It is not 4 because other specific capabilities (configuring scopes, editing the profile XML, running validation) are not mentioned, and not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Both parts are present: an explicit trigger clause 'Use when creating or modifying SSR inspections or search patterns' and a what-statement 'Guide for using Structural Search and Replace in IntelliJ'. It is not 5 because the 'what' is generic ('Guide for using') and never states concretely what the skill enables, such as writing the XML configurations or setting inspection scopes.

4 / 5

Trigger Term Quality

Good natural keyword coverage: both the full feature name 'Structural Search and Replace' and the abbreviation 'SSR' appear alongside 'inspections' and 'search patterns', which IntelliJ users would naturally say. A few natural terms are missing (e.g., 'SSR templates', 'replace patterns'), so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

'Structural Search and Replace in IntelliJ' and 'SSR inspections' define a clear niche with minimal conflict risk against unrelated skills. It is not 5 because 'search patterns' is a generic phrase that could also fire for ordinary code-search or regex requests from other skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

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.