CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

registry

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

Quality

80%

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/registry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, lean reference skill: every pattern has executable Kotlin/XML snippets, the critical early-startup pitfall is explained with rationale and a lookup procedure, and navigation to deeper docs is clearly signaled. Only minor trims (duplicated intro line, redundant deprecation sentence) would tighten it further.

DimensionReasoningScore

Conciseness

The body is lean and code-forward, and the IDE-specific behavior (LoadingState/COMPONENTS_LOADED pitfalls) is knowledge Claude would not already have. Minor trimmable redundancy remains: the line under the H1 restates the title/description, and 'Always prefer the RegistryManager when possible' repeats the preceding deprecation sentence.

4 / 5

Actionability

Every section ships copy-paste-ready code: the <registryKey> XML with an overrides variant, RegistryManager.getInstanceAsync().get() for suspending vs getInstance().get() for blocking code, the safe Registry.is(key, default) overload, the -Dmy.registry.key=value CLI override, and the @RegistryKey test annotation — covering the common cases completely.

5 / 5

Workflow Clarity

This is a single-purpose reference skill where each pattern is unambiguous and context-labeled ('In suspending code', 'In blocking code', early startup). The early-startup section adds a MUST rule, a two-step procedure for finding the default value, and an explicit 'Why', and no destructive or batch operations are involved so no validation checkpoint is required.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is appropriately compact with clear section headers; the two external doc links ('Defining Registry Keys', 'Cloud Registry') and the cross-skill writing-tests link are clearly labeled and one level deep. It stops short of a 5 because there is no overview/quick-start layer and the doc links point outside the skill bundle.

4 / 5

Total

18

/

20

Passed

Description

65%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 has an explicit and well-formed 'Use when...' trigger clause with natural keywords, but the 'what' side is generic — it labels the domain without stating any concrete actions the skill covers. Adding 2-3 specific capabilities (define registry keys, read values safely, override in tests) would materially improve it.

Suggestions

Replace the generic 'Guidelines for using the IntelliJ Registry API' with 2-3 concrete actions, e.g. 'Define, read, and override IntelliJ registry keys and feature flags, including safe access during early IDE startup.'

Broaden trigger coverage with natural variations users would say: 'IntelliJ', 'plugin.xml', 'registry.properties', 'RegistryManager', or 'platform settings/feature toggles'.

State the concrete failure mode the skill prevents (e.g. 'avoids Registry.is() exceptions before COMPONENTS_LOADED') to sharpen distinctiveness against generic feature-flag skills.

DimensionReasoningScore

Specificity

"Guidelines for using the IntelliJ Registry API" names the domain but the action is generic ("using"); no concrete capabilities such as defining keys, reading values, or handling early startup are explicitly stated, matching the anchor for naming the domain with minimal/generic actions.

2 / 5

Completeness

Both parts are explicit: what ("Guidelines for using the IntelliJ Registry API") and when ("Use when working with registry keys or feature flags"). The 'what' is high-level rather than a concrete capability list, so it falls short of the clearly-concrete anchor 5.

4 / 5

Trigger Term Quality

"registry keys" and "feature flags" are natural phrases users would say, giving good keyword coverage, but common variations like "IntelliJ", "plugin.xml", or "registry.properties" are missing — one level below comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"IntelliJ Registry API" carves a clear niche with distinct triggers, but the generic "feature flags" wording creates minor overlap risk with broader feature-flag or config skills, matching the 'mostly distinct' anchor rather than minimal-conflict.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

JetBrains/MPS

Path

.agents/skills/registry/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.