CtrlK
BlogDocsLog inGet started
Tessl Logo

java-debug

Safety rules, workflows, and tool reference for debugging applications via IntelliJ debugger: breakpoints, debug sessions, stepping, evaluating expressions, inspecting runtime state. TRIGGER when: user wants to debug, investigate a bug, set breakpoints, inspect runtime behavior, step through code, or understand why code behaves unexpectedly at runtime. Trigger phrases (EN): "debug", "breakpoint", "step through", "step into", "step over", "why does this crash", "why is this null", "launch in debug mode", "trace execution", "run with debugger", "evaluate expression". Trigger phrases (RU): "отладить", "дебаг", "брейкпоинт", "почему падает", "пошагово пройти", "зайти в метод", "посмотреть значение переменной", "запустить в режиме отладки", "почему null", "стектрейс". Also trigger when user wants to understand runtime behavior or investigate incorrect behavior.

77

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is a tight, highly actionable MCP debugger reference with clear sequenced workflows and explicit verification checkpoints — strong on conciseness, actionability, and workflow clarity. Its only weakness is progressive disclosure: everything sits in one ~145-line file with no split-out reference material.

Suggestions

Move the Tool Reference tables into a bundled references/ file (e.g. references/tool-reference.md) and link to it from a short overview in SKILL.md, so the main file stays a lean entry point.

Optionally extract the per-category tool tables (Session, Breakpoints, Execution Control, Inspection) into one-level-deep, clearly signaled reference sections for easier navigation.

DimensionReasoningScore

Conciseness

The body is lean and operationally focused — tool/parameter tables and sequenced workflows — without explaining general concepts Claude already knows (no "what is a breakpoint" or "how a JVM works"); prose such as the suspended-process trap is tool-specific operational hazard, not padding.

3 / 3

Actionability

Gives concrete, copy-paste-ready guidance: exact tool names with typed parameters and defaults (e.g. "add_breakpoint: filePath, line (1-based), condition"), and concrete commands like "--max-time 5 with curl" or "run_in_background: true".

3 / 3

Workflow Clarity

Two numbered workflows with explicit validation checkpoints ("get_current_position — confirm the breakpoint was hit", "After each step, call get_current_position") plus a dedicated Error Recovery table providing fix-and-retry feedback loops.

3 / 3

Progressive Disclosure

Well organized into clear sections but it is a single monolithic file with the full tool reference inline and no bundle files or external references to defer detail to, mirroring the anchor where reference-like content that could be separate lives inline.

2 / 3

Total

11

/

12

Passed

Description

100%

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 specific, bilingual, and explicitly covers both what the skill does and when to invoke it, all in third person. It is among the strongest reference examples in the rubric. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "breakpoints, debug sessions, stepping, evaluating expressions, inspecting runtime state" — matching the anchor that asks for several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Safety rules, workflows, and tool reference for debugging applications via IntelliJ debugger") and when ("TRIGGER when: user wants to debug, investigate a bug..."), with explicit trigger guidance rather than implied usage.

3 / 3

Trigger Term Quality

Provides broad coverage of natural phrases users would say in both EN ("debug", "breakpoint", "why does this crash", "step through") and RU ("отладить", "почему падает"), well beyond the "some relevant keywords" level.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — "debugging applications via IntelliJ debugger" via the IntelliJ Debug MCP — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Amplicode/spring-skills
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.