CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a tight, highly actionable diagnosis playbook with a clear sequenced workflow, explicit validation gates, and genuine domain-specific knowledge rather than filler. No bundle files are needed or present, and structure is clean.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding of concepts Claude already knows; every element (EmDash culprits list, confidence/fix-approach taxonomies) is non-obvious domain knowledge that earns its tokens.

5 / 5

Actionability

Gives concrete executable guidance — 'read each frame in order from the deepest application frame', 'grep for the function then trace its inputs', named APIs (sql.ref(), validateIdentifier()), and a specific output format with a real path example — covering common cases fully.

5 / 5

Workflow Clarity

A clearly sequenced 9-step procedure with explicit validation/recovery checkpoints (search more if you cannot pin below file level; confidence gates when fix runs) and honesty-both-ways guidance; read-only so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Environment, Do not, Procedure, Output) with no nested or buried references; as a self-contained single-purpose skill there is no content that belongs in a separate file.

5 / 5

Total

20

/

20

Passed

Description

67%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 specific, action-oriented, and distinct, but lacks an explicit 'Use when...' trigger clause and uses task-internal vocabulary over natural user phrasing. Adding a trigger clause and common synonyms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming when to invoke this skill, e.g. 'Use when a bug has been reproduced and you need to locate its root cause before fixing.'

Include natural user-facing trigger terms like 'diagnose', 'find the bug', 'root cause', or 'where is this error coming from' alongside the task-internal vocabulary.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Trace from a reproduced symptom to the source code', 'Pin the specific file and approximate line', 'rate confidence', 'always propose a concrete fix' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

The 'what' is strong and concrete, but there is no explicit 'Use when...' trigger clause, only weakly implied 'when' via 'from a reproduced symptom'; per rubric guidance the missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Has relevant task terms ('symptom', 'source code', 'fix', 'confidence') but these are task-internal rather than natural user trigger phrases; common synonyms a user would say ('diagnose', 'find the bug', 'root cause') are missing.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — root-causing a reproduced symptom — distinct from sibling fix/verify/reproduce skills, with minimal overlap risk.

5 / 5

Total

16

/

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