CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debugging

Debugging techniques and tools for IntelliJ development. Use when debugging IDE issues or investigating failures.

Quality

72%

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

Quality

Content

75%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.

The body is lean, IntelliJ-specific, and immediately actionable, with copy-paste grep commands, a worked category-abbreviation example, and a clear 4-step debugging workflow that includes a verification checkpoint. Minor issues keep it just below top marks: slightly redundant grep examples, directional rather than executable end-to-end steps, and one buried reference.

DimensionReasoningScore

Conciseness

The body is lean and restricted to genuinely non-obvious IntelliJ specifics ("#<abbreviated.package.path>.<ClassName>", "FINE = debug level (from LOG.debug { })"), but the three grep variants are partially redundant — "# All logs from a class" subsumes the FINE and INFO variants, so a token or two could be trimmed. Not 5 because of that minor redundancy; not 3 because there is no padding or explanation of general concepts Claude already knows.

4 / 5

Actionability

Provides copy-paste-ready commands ("grep \"FINE - #c.i.o.w.i.s.IdeStatusBarImpl\" idea.log") and a concrete tool pointer ("get the log location via `mps_mcp_list_open_projects`"), but the End-to-End Behavior steps are directional ("Trace the full execution chain") without executable commands, and the Documentation links are bare references. Not 5 because of these minor gaps; not 3 because the core log-search guidance is fully executable with a worked category example.

4 / 5

Workflow Clarity

The End-to-End Behavior section gives a clear 4-step sequence with a verification checkpoint ("Verify the fix at the entry point the user actually invokes") and a fallback ("Add debugging output... if still unsure"), though an explicit validate-and-retry feedback loop is absent. Not 5 because there is no error-recovery loop; not 3 because checkpoints are present and the sequence is coherent — and no destructive/batch operations are involved that would cap the score.

4 / 5

Progressive Disclosure

Well-organized sections (Documentation, Searching idea.log, End-to-End Behavior) with one-level-deep references, but the ide-log.md pointer is buried mid-sentence ("or see `.agents/skills/mps-mcp-workflow/references/ide-log.md`") and the docs links ("../../../../docs/IntelliJ-Platform/...") resolve outside the bundle. Not 5 because of these minor signaling gaps; not 3 because structure is good and references are mostly clearly labeled with one-line descriptions.

4 / 5

Total

16

/

20

Passed

Description

57%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 names a specific domain and includes an explicit "Use when" trigger clause, but the capability statement ("techniques and tools") is generic and trigger coverage misses natural synonyms like errors, exceptions, freezes, and stack traces. There is moderate conflict risk with general debugging skills.

Suggestions

Replace "Debugging techniques and tools" with the concrete capabilities from the body, e.g., "Search idea.log using IntelliJ category abbreviations, analyze exceptions and freezes, trace execution chains across IDE layers."

Broaden the trigger terms to natural synonyms users would say: "errors, exceptions, stack traces, freezes, crashes, idea.log" — the body covers these but the description never mentions them.

Tighten the when-clause to the IntelliJ/MPS scope, e.g., "Use when debugging IntelliJ Platform or MPS IDE issues, searching idea.log, or investigating freezes and exceptions."

DimensionReasoningScore

Specificity

"Debugging techniques and tools for IntelliJ development" names the domain but the capability statement is generic — "techniques and tools" names no concrete action (log searching, exception analysis, freeze investigation are all in the body but absent here). Not 3 because no 1-2 concrete actions are listed; not 1 because, unlike "Helps with documents", a specific domain (IntelliJ development) is named.

2 / 5

Completeness

Has both an explicit trigger clause ("Use when debugging IDE issues or investigating failures") and a "what" ("Debugging techniques and tools for IntelliJ development"), but the "what" is generic and the "when" could be more specific. Not 5 because the what lacks concrete actions and the trigger phrases are not comprehensive; not 3 because an explicit "Use when..." clause is present, so the cap does not apply.

4 / 5

Trigger Term Quality

Includes natural phrases "debugging", "IDE issues", and "investigating failures", but misses common variations users would actually say: "errors", "exceptions", "stack traces", "freezes", "crashes", or "idea.log" — all of which the body covers. Not 4 because keyword coverage has several missing natural synonyms; not 2 because more than one relevant, natural keyword is present.

3 / 5

Distinctiveness Conflict Risk

The "IntelliJ development" qualifier establishes a clear niche, but the generic triggers "debugging" and "investigating failures" overlap with any general-purpose debugging skill. Not 5 because "investigating failures" is broad enough to collide with other skills; not 3 because the IntelliJ scoping makes it mostly distinct.

4 / 5

Total

13

/

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/debugging/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.