CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agency/plugins/nori/skills/systematic-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 excels at workflow design: a strictly gated four-phase process with explicit verification steps, feedback loops, and escalation rules. However, it is noticeably verbose — it re-teaches basic debugging knowledge and repeats its core message across three redundant sections — and its external references point to paths that do not exist in the bundle.

Suggestions

Trim the sections that restate the same 'don't skip Phase 1' message ('When to Use', 'Red Flags', 'Common Rationalizations', and 'Real-World Impact' with its unverifiable statistics) into a single compact section, and cut guidance Claude already knows such as reading stack traces or checking git diff.

Resolve the dangling references: either add the referenced files (e.g., a root-cause-tracing reference) to the bundle as clearly signaled one-level-deep links, or remove the 'skills/root-cause-tracing' and '.agency/plugins/nori/skills/test-driven-development' pointers.

Move the long multi-layer bash instrumentation example and the rationalizations table into a references/ file linked from Phase 1, keeping SKILL.md as a lean overview of the four phases.

DimensionReasoningScore

Conciseness

The ~310-line body repeatedly explains knowledge Claude already has ('Read Error Messages Carefully — Don't skip past errors or warnings', 'Check Recent Changes — Git diff, recent commits') and restates the same 'don't skip the process' message across 'When to Use', 'Red Flags', and 'Common Rationalizations', plus filler like 'Violating the letter of this process is violating the spirit of debugging.' This matches the 2 anchor (noticeably verbose, several padded sections); not a 1 because there is no library-primer padding and the phase structure itself is useful.

2 / 5

Actionability

Concrete, executable guidance dominates: a runnable bash instrumentation example ('env | grep IDENTITY', 'security list-keychains', 'codesign --sign "$IDENTITY" --verbose=4'), explicit decision rules ('If < 3: Return to Phase 1... If ≥ 3: STOP and question the architecture'), and a per-phase checklist. Minor gaps (the 'For EACH component boundary' block is pseudo-structured) hold it at the 4 anchor rather than 5.

4 / 5

Workflow Clarity

The four phases are strictly sequenced ('You MUST complete each phase before proceeding to the next') with explicit validation checkpoints ('Verify Fix — Test passes now? No other tests broken?'), error-recovery feedback loops ('If fix doesn't work: STOP, count, return to Phase 1'), an escalation rule at 3+ failed fixes, and a quick-reference table of success criteria — a clear match for the 5 anchor. This is a debugging process, not a destructive/batch operation, so the workflow cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, yet the body references 'skills/root-cause-tracing' and '.agency/plugins/nori/skills/test-driven-development' as bare, unlinked paths outside the bundle — references present but not clearly signaled. Content that could live in separate files (the multi-layer bash example, the rationalizations table, the signals section) is inlined in a ~310-line body, matching the 3 anchor.

3 / 5

Total

14

/

20

Passed

Description

83%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 strong: it pairs an explicit 'Use when' clause with concrete trigger terms and a clearly enumerated four-phase capability list in third-person voice. Its only weaknesses are a few missing natural synonyms (e.g., 'error', 'debug', 'crash') and coverage that names the phases without detailing them.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation)' — naming the domain and four specific activities. It falls short of the 5 anchor because it does not comprehensively cover what each phase involves, but is well above the 1-2 action coverage of the 3 anchor.

4 / 5

Completeness

Explicitly answers both questions: 'Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes' gives concrete trigger phrases for when, and the four-phase framework with named phases states clearly what it does. This matches the 5 anchor; the 4 anchor's weaker or implicit 'when' does not apply.

5 / 5

Trigger Term Quality

'bug, test failure, or unexpected behavior' provides good natural keyword coverage a user would actually say. Below the 5 anchor because common synonyms like 'error', 'debug', 'crash', or 'exception' are missing; above the 3 anchor since only a few natural variations are absent.

4 / 5

Distinctiveness Conflict Risk

A distinct debugging-methodology niche with specific triggers ('bug, test failure, unexpected behavior') that are unlikely to fire for unrelated skills. Minor overlap risk with test-fixing or error-handling skills keeps it at the 4 anchor rather than 5.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/FluidFramework

Path

.agency/plugins/nori/skills/systematic-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.