CtrlK
BlogDocsLog inGet started
Tessl Logo

investigate

Investigate a specific issue report with strict, evidence-driven diagnosis.

56

Quality

64%

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 ./packages/eve-code/extension/skills/investigate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exceptionally lean, well-organized instruction-only skill with a coherent diagnostic workflow and explicit stop conditions. Its main weakness is actionability: the guidance is directional throughout, with no concrete output template, tooling hints, or worked example that would make the required artifacts (hypothesis log, evidence summary, decision tree) unambiguous.

Suggestions

Add a compact output template or example (e.g., a short filled-in example of the final report: observed evidence, diagnosed mechanism, unresolved references, prognosis) to make the 'Return compact but complete evidence' instruction concrete.

Specify how the explicit hypothesis log should be kept at each branch (e.g., one line per hypothesis with the disproof attempt and its result) so that standard is executable rather than directional.

Number the top-level workflow steps (reproduce → trace → hypothesize → conclude) so the sequence and its early-out checkpoints are explicit rather than implied by paragraph order.

DimensionReasoningScore

Conciseness

Every sentence is directive guidance ("Start at the observed effect and identify the code paths directly responsible", "Stop when required evidence is unavailable rather than filling gaps with guesses") with zero padding and no explanation of concepts Claude already knows. Lean and efficient; every token earns its place.

5 / 5

Actionability

Concrete direction exists ("Keep an explicit hypothesis at every branch and try to disprove it", "Distinguish observations, inferences, and unknowns", "Resolve every cited call frame") but there are no executable specifics — no commands, tooling, output template, or worked example showing what the hypothesis log or final report looks like. Not a 4 because the guidance stays directional rather than executable; not a 2 because several standards are concretely actionable.

3 / 5

Workflow Clarity

A clear sequence is present (establish reproducibility → trace upward from the effect → hypothesis testing → return evidence) with explicit checkpoints ("If not, pause and report that result", "Stop when required evidence is unavailable") and a checklist section. Not a 5 because the ordering is implicit across prose rather than an explicitly marked sequence, and there is no explicit validate-fix-retry feedback loop; not a 3 because checkpoints are stated rather than missing.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well-organized into focused sections (## Standards, ## Questions for every hypothesis) with no content that belongs in separate files. Per the scoring notes for simple, self-contained skills, this warrants a 5.

5 / 5

Total

17

/

20

Passed

Description

50%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 concise, third-person, and names a clear domain and approach, but it lacks any 'Use when...' trigger guidance and misses common natural keywords like "bug", "debug", or "root cause". It communicates what the skill does but not when to invoke it, leaving it to blend with general debugging skills.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user reports a bug, error, crash, regression, or unexpected behavior and asks to investigate, debug, or find the root cause.') to raise completeness and distinctiveness.

Include natural trigger synonyms such as "bug", "error", "debug", "root cause", and "regression" alongside "issue report" so the description matches phrases users actually say.

Enumerate 1-2 more concrete actions (e.g., 'reproduce the issue, trace it through call frames and processes, and return the diagnosed mechanism with evidence') to make the capability set more specific.

DimensionReasoningScore

Specificity

Names the domain ("issue report") and 1-2 concrete actions ("Investigate", "evidence-driven diagnosis"), but does not enumerate several specific actions, matching the 'names domain and 1-2 concrete actions' anchor. It is not a 2 because the named action is concrete rather than generic, and not a 4 because no broader action list is provided.

3 / 5

Completeness

It clearly answers 'what' ("Investigate a specific issue report with strict, evidence-driven diagnosis") but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like "Investigate", "issue report", and "diagnosis" are present, but common natural variations users would say — "bug", "error", "debug", "root cause" — are missing. Matches the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The phrases "specific issue report" and "evidence-driven diagnosis" give it some specificity, but "investigate" is a broad verb and the description overlaps with debugging and code-review skills without trigger phrasing to sharpen the boundary, matching the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

12

/

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
vercel/eve
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.