CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

94

0.97x
Quality

94%

Does it follow best practices?

Impact

90%

0.97x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

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, highly actionable diagnostic discipline with clear sequenced phases, explicit validation checkpoints, and sensible bundle use. The only soft spot is actionability depth for some harness types and minor progressive-disclosure refinement.

Suggestions

For the harness types in Phase 1 (e.g. property/fuzz loop, bisection harness), add one short executable snippet or a script reference so they are copy-paste ready rather than described.

Consider extracting the Phase 1 technique catalog into a reference file if the skill grows, keeping SKILL.md as the concise overview.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence, explains no basic concepts, and every line earns its place (e.g. 'A 2-second deterministic loop is a debugging superpower').

5 / 5

Actionability

Concrete enumerated techniques, an executable referenced script (scripts/hitl-loop.template.sh), and specific patterns like [DEBUG-a4f2] and git bisect run; minor gaps where harness types are described rather than given as ready-to-run code.

4 / 5

Workflow Clarity

Six explicitly sequenced phases with validation gates ('Do not proceed until...'), checklists in Phase 2 and Phase 6, and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-organized sections with one clearly signaled, one-level-deep reference (scripts/hitl-loop.template.sh); appropriately self-contained overview with minor room for splitting detailed technique guidance.

4 / 5

Total

18

/

20

Passed

Description

100%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 actions, explicit trigger phrases covering what and when, and a well-scoped niche with low conflict risk. Third person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists six concrete actions (Reproduce → minimise → hypothesise → instrument → fix → regression-test) giving comprehensive coverage of the diagnosis workflow.

5 / 5

Completeness

Explicitly answers what (a disciplined diagnosis loop with named phases) and when (concrete 'Use when...' trigger phrases).

5 / 5

Trigger Term Quality

Includes natural phrases users say ('diagnose this', 'debug this', 'broken/throwing/failing', 'performance regression') with synonyms and variants.

5 / 5

Distinctiveness Conflict Risk

Clear niche (hard bugs and performance regressions) with distinct triggers, minimal overlap with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coder/agent-tty
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.