CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagnose

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 tightly written process skill with exemplary sequencing, gates, and checklists, and unusually concrete technique guidance for an instruction-only skill. Its only deductions are light motivational padding and a single-file structure with one external reference whose target file is absent from the bundle.

Suggestions

Trim the motivational editorial lines (e.g., "Be aggressive. Be creative. Refuse to give up.", "debugging superpower") and compress the provenance footnote to a one-line attribution.

Ship the referenced `.agents/skills/diagnose/hitl-loop.template.sh` in the bundle (or move the 10-item loop-construction catalog into a reference file) so the one external reference resolves and the main file stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with high-signal, imperative guidance and explains nothing Claude already knows, but a few motivational/editorial lines ("Be aggressive. Be creative. Refuse to give up.", "A 2-second deterministic loop is a debugging superpower.", "the bug is 90% fixed") and the long closing provenance paragraph could be trimmed. Efficient with minor over-explanation — the score-4 anchor, clearly above the 'could be tightened' level of 3.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: ten concrete feedback-loop constructions with named tools (Playwright/Puppeteer, curl, bisection harness, differential loop), a concrete hypothesis format template, a specific log-tagging convention (`[DEBUG-a4f2]`), named instrumentation techniques (performance.now(), profiler, query plan), and a template file path for the human-in-the-loop case. Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this specific; it does not fall to score 4's 'minor gaps'.

5 / 5

Workflow Clarity

Six clearly sequenced phases with explicit validation gates ("Do not proceed to Phase 2 until you have a loop you believe in", "Do not proceed until you reproduce the bug"), checklists in Phases 2 and 6, and a watched-fail→fix→watched-pass→re-run loop in Phase 5 — matching the score-5 anchor's explicit validation steps, error-recovery feedback loops, and checklists.

5 / 5

Progressive Disclosure

Good structure: a phase-per-section overview with clearly signaled one-level references (`.agents/skills/diagnose/hitl-loop.template.sh` for the last-resort loop, a LICENSE note). However, no bundle files exist alongside this SKILL.md — the referenced template path is not present in the reviewed bundle — and at ~117 lines some content (e.g., the ten loop constructions or the post-mortem hand-off detail) could live in reference files, which is the minor organization gap of the score-4 anchor rather than the clean split of score 5.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete pipeline actions, explicit dual triggers in natural user language, third-person voice, and a well-carved niche. The only weakness is a handful of missing common trigger synonyms (error, crash, not working).

Suggestions

Add a few high-frequency trigger synonyms such as "errors", "crashes", or "not working" to the Use-when clause to reach comprehensive keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("hard bugs and performance regressions") and lists six concrete, specific actions in the pipeline ("Reproduce → minimise → hypothesise → instrument → fix → regression-test"), which comprehensively covers the diagnosis workflow. It does not merely gesture at the domain like the score-4 anchor's 'minor gaps' case — the full loop is enumerated.

5 / 5

Completeness

Explicitly answers both questions: what ("Disciplined diagnosis loop for hard bugs and performance regressions" plus the six-step loop) and when ("Use when user says 'diagnose this' / 'debug this', reports a bug, says something is broken/throwing/failing, or describes a performance regression") with concrete trigger phrases — the exact pattern of the score-5 anchor.

5 / 5

Trigger Term Quality

Strong natural phrasing — "diagnose this", "debug this", "something is broken/throwing/failing", "performance regression" — matching what users actually say. A few very common trigger terms are missing ("error", "crash", "not working", "it's slow"), which keeps it short of the comprehensive-synonyms bar of the score-5 anchor; it sits above score 3 because the quoted phrases are natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

A clear niche (disciplined, multi-phase diagnosis of hard bugs) with distinct, direct triggers; the quoted phrases route bug reports and regressions here unambiguously with minimal overlap risk against neighboring skills like code review or general implementation. Fits the score-5 'clear niche with distinct triggers' anchor better than the score-4 'minor overlap risk' anchor.

5 / 5

Total

19

/

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

agranado2k/ai-report-platform

Path

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