code-style

Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.

Quality

87%

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

100%

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

An efficient, well-organized rule set that assumes Claude's competence and provides concrete, actionable style directives with no unnecessary padding.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point rules with no padding or explanation of concepts Claude already knows; every line carries a concrete directive.	3 / 3
Actionability	Concrete, copy-paste-ready rules (e.g., '@ApiStatus.Experimental', 'Line length: 140 characters max', 'Use @JvmField') give exact executable guidance.	3 / 3
Workflow Clarity	A simple single-purpose skill under 50 lines, organized into clear Language and Formatting sections with unambiguous directives and no risky batch/destructive operations needing validation.	3 / 3
Progressive Disclosure	Well under 50 lines with no bundle files needed; content is cleanly split into well-signaled sections, and the single external path reference is one level deep and clearly signaled.	3 / 3
	Total	12 / 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.

A concise, well-scoped description with an explicit use-trigger and a clear IntelliJ niche. It would benefit from naming more concrete style actions and broader trigger-term coverage.

Suggestions

List specific concrete actions (e.g., 'enforce Kotlin idioms, naming, and formatting rules') to raise specificity.

Add common trigger variations users might say, such as 'formatting', 'linting', or 'naming conventions', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Code style rules for IntelliJ codebase') and an action ('writing or reviewing code'), but does not list multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	Clearly answers what it does ('Code style rules for IntelliJ codebase') and when to use it via an explicit 'Use when writing or reviewing code for style compliance' trigger.	3 / 3
Trigger Term Quality	Includes natural terms a user would say ('code style', 'writing or reviewing code', 'style compliance') but misses common variations such as 'formatting', 'linting', or 'naming conventions'.	2 / 3
Distinctiveness Conflict Risk	Scoping to 'IntelliJ codebase' and 'IntelliJ-specific rules' gives it a clear niche with distinct triggers, unlikely to fire for unrelated style 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/code-style/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.