CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnose

Trace from a reproduced symptom to the source code that causes it. Identify the specific file and approximate line, then rate confidence honestly.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.flue/skills/diagnose/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable diagnostic procedure with clear sequencing and good organization; its only weakness is moderate verbosity in the qualifying prose of a few steps. Trimming the long parentheticals and the embedded issue example would improve token efficiency.

Suggestions

Tighten the extended parentheticals in steps 6 and 7; move the 'fix stage runs/defers' rules into the fix-approach descriptions rather than repeating them as caveats.

Shorten or extract the issue #1178 worked example so the main procedure stays scannable while retaining the concrete illustration.

Consider moving the 'obvious culprits' checklist toward a bundled reference if more patterns accrue, keeping the main body lean.

DimensionReasoningScore

Conciseness

It assumes Claude's competence and explains no basic concepts, but several qualifying passages (the extended step-6 and step-7 parentheticals, the long issue-#1178 example) could be tightened to earn every token.

2 / 3

Actionability

Provides concrete per-symptom sub-procedures, a specific 'obvious culprits' checklist with real patterns (missing locale filter, missing await, module-scope t()), and a worked output example, all directly actionable for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 9-step numbered sequence anchored on prior-stage output, with explicit gates ('If you cannot get below file-level... search more') and a defined output schema; read-only scope means destructive-validation loops are not applicable.

3 / 3

Progressive Disclosure

A single self-contained, well-sectioned SKILL.md (Hard prohibitions, Procedure, Output) with no external references needed, which the rubric allows to score 3 for compact, clearly organized skills.

3 / 3

Total

11

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific and occupies a clear niche, but it lacks an explicit 'Use when...' trigger clause and broader natural trigger terms, which caps its completeness and trigger-term quality. Adding a brief usage-trigger clause would raise both.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use after reproducing a bug to locate the source code that causes it.'

Broaden trigger terms to include natural user phrasings like 'diagnose a bug', 'find the root cause', or 'locate the failing code'.

Keep the third-person voice (it already does) and avoid softening phrases like 'rate confidence honestly' toward something more directive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Trace from a reproduced symptom', 'Identify the specific file and approximate line', 'rate confidence'), matching the anchor for enumerating several specific actions rather than just naming a domain.

3 / 3

Completeness

It clearly states what the skill does, but lacks any explicit 'Use when...' trigger clause; the 'when' is only implied by 'from a reproduced symptom', which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Uses relevant but process-internal terms ('reproduced symptom', 'source code', 'rate confidence') while missing common natural phrasings a user would say like 'diagnose a bug' or 'find the root cause', so it only partially covers natural trigger vocabulary.

2 / 3

Distinctiveness Conflict Risk

The scope is a narrow post-reproduce diagnosis stage ('trace a reproduced symptom to source code'), a clear niche unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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
emdash-cms/emdash
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.