debugging-strategies

Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.

Quality

50%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/debugging-strategies/SKILL.md

The canonical home for this skill is debugging-strategies in rmyndharis/antigravity-skills

Quality

Content

63%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 well-organized and concise with a clear trigger/anti-trigger structure and a sequenced workflow, but its instructions lack concrete executable specifics and its single reference points to a missing file. Actionability and the broken reference are the main weaknesses.

Suggestions

Add concrete, executable specifics to the instructions, e.g. named tools (strace, lldb, perf), example commands, or a minimal repro-capture snippet.

Create the referenced 'resources/implementation-playbook.md' so the progressive-disclosure link resolves, or remove the reference if no detail is needed.

Remove the verbatim repetition of the frontmatter description in the opening body line to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no padding or explanation of basic concepts; the only minor inefficiency is the opening line repeating the frontmatter description verbatim.	4 / 5
Actionability	Instructions give concrete directives ('Reproduce the issue and capture logs', 'Narrow scope with binary search and targeted instrumentation') but no specific tools, commands, or examples, leaving the steps at a high level rather than executable.	3 / 5
Workflow Clarity	The five instructions form a clear sequence (reproduce -> hypothesize -> narrow -> document -> verify) with an explicit 'verify the fix' checkpoint; it stops short of 5 only because error-recovery feedback loops are not detailed.	4 / 5
Progressive Disclosure	The body is well structured with clearly signaled one-level-deep references to 'resources/implementation-playbook.md', but that referenced file does not exist in the bundle, so navigation is signaled yet broken.	3 / 5
	Total	14 / 20 Passed

Description

37%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 is grammatically clean and names a clear domain, but it is vague on concrete actions and omits any 'Use when' trigger guidance, leaving it indistinct from general problem-solving. Specificity and trigger-term coverage are the main weaknesses.

Suggestions

Add concrete actions to the description, e.g. 'Reproduce issues, capture logs and traces, form hypotheses, and narrow scope with binary search.'

Append a 'Use when...' clause with natural trigger phrases users would say, e.g. 'Use when tracking down elusive bugs, debugging production incidents, or analyzing crash dumps and stack traces.'

Replace generic adjectives ('powerful tools', 'proven strategies') with specific nouns or named techniques to reduce overlap with general coding skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('debugging') but relies on generic adjectival actions like 'proven strategies, powerful tools, methodical approaches' rather than concrete actions such as reproduce, capture logs, or binary search; it is below the 3 anchor which requires named concrete actions.	2 / 5
Completeness	It clearly states what the skill does ('Transform debugging... into systematic problem-solving') but includes no 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Only 'debugging' is a natural keyword users would say; the body's richer triggers (crash dumps, stack traces, performance) are absent from the description itself, leaving mostly generic language like 'problem-solving'.	2 / 5
Distinctiveness Conflict Risk	'Debugging' is a recognizable niche, but the abstract framing ('frustrating guesswork into systematic problem-solving') is broad enough to overlap with general problem-solving or coding skills, so it is only somewhat specific.	3 / 5
	Total	10 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/debugging-strategies/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.