registry

Guidelines for using the IntelliJ Registry API. Use when working with registry keys or feature flags.

Quality

95%

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.

A tight, highly actionable reference with executable examples across declaration, access, early-startup, command-line override, and testing, plus well-signaled one-level-deep pointers to deeper docs. It assumes competence and avoids fluff.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the "Why" block and deprecation note convey non-obvious gotchas with every token earning its place. Not a 2 because there is no unnecessary padding to trim.	3 / 3
Actionability	It provides fully executable XML registryKey declarations, Kotlin RegistryManager/Registry.is snippets, a command-line override flag, and a @RegistryKey test annotation — all copy-paste ready with specific keys. Not a 2 because the examples are complete rather than pseudocode.	3 / 3
Workflow Clarity	This is a single-purpose reference skill with clearly organized sections; no destructive or batch operation requires a validation checkpoint, so under the simple-skills note it qualifies for full clarity. Not a 2 because the sequences present (e.g., the numbered default-value lookup) are unambiguous.	3 / 3
Progressive Disclosure	The Documentation section links to two clearly signaled, one-level-deep .md references and a cross-skill writing-tests link, with the core quick-reference content kept inline; no nested references exist. Not a 2 because references are well signaled and appropriately split.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 trigger clause and a clearly scoped niche. Its only weakness is that "guidelines for using" is generic phrasing rather than a list of concrete capabilities.

Suggestions

Replace "Guidelines for using" with concrete actions, e.g. "Declare, override, and read IntelliJ registry keys and feature flags."

Consider naming the primary contexts users mention, such as early-startup defaults or test-time registry overrides, to strengthen trigger coverage.

Dimension	Reasoning	Score
Specificity	"Guidelines for using the IntelliJ Registry API" names the domain but uses the vague phrase "guidelines for using" rather than listing concrete actions, matching the anchor that names a domain and some actions but is not comprehensive; not a 1 because it is not abstract, and not a 3 because no multiple specific concrete actions are enumerated.	2 / 3
Completeness	It states what ("Guidelines for using the IntelliJ Registry API") and an explicit when ("Use when working with registry keys or feature flags"), answering both; not a 2 because the when clause is explicit rather than implied.	3 / 3
Trigger Term Quality	"registry keys" and "feature flags" alongside "IntelliJ Registry API" are natural terms a user would say when they need this skill, giving good coverage; not a 2 because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	The IntelliJ Registry API is a clear niche with distinct triggers unlikely to fire for the wrong skill; not a 2 because it is not merely "works with files"-level generic.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/registry/SKILL.md
Commit: 52c9d63

Reviewed: about 4 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.