CtrlK
BlogDocsLog inGet started
Tessl Logo

investigate

Use when the user asks to diagnose a bug, find the root cause of a failing behavior, or run a controlled hypothesis-by-hypothesis investigation with experiments and evidence. Produces a diagnostic report with a recommended fix (but does not apply the fix). Do NOT trigger on "fix this bug" when the cause is obvious, or on simple error-message lookups.

74

Quality

92%

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

92%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 well-structured, lean instruction-only skill with a clear sequenced workflow, explicit validation checkpoints, and a verification checklist. The only improvement room is adding a concrete Hypothesis Board example to lift actionability.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept explanations Claude already knows; every section (Overview, Context, Rules, Instructions, Verification) earns its place and assumes Claude's competence.

5 / 5

Actionability

Specific, actionable guidance ('Propose 3-7 candidate root causes with initial probabilities summing to ~100%', 'Recommend a concrete fix (file, line, proposed change)') but lacks a concrete Hypothesis Board template or worked example that would make it copy-paste ready.

4 / 5

Workflow Clarity

Clear four-step sequence (Initialize → Hypotheses → Experiment Loop → Final Report) with explicit validation (baseline restore, termination condition), a revert feedback loop, and a closing verification checklist.

5 / 5

Progressive Disclosure

Under 50 lines, single self-contained file with well-organized sections and no need for external references, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

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.

A strong, specific description that clearly states both capability and trigger conditions while adding negative-trigger guidance to avoid misfiring. The only gap is minor synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'diagnose a bug', 'find the root cause of a failing behavior', 'run a controlled hypothesis-by-hypothesis investigation with experiments and evidence', and 'Produces a diagnostic report with a recommended fix' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' ('Produces a diagnostic report with a recommended fix (but does not apply the fix)') and 'when' ('Use when the user asks to diagnose a bug...') with concrete trigger phrases and anti-trigger guidance.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ('diagnose a bug', 'root cause', 'failing behavior', 'investigation') plus helpful negative triggers, but common synonyms such as 'debug' or 'troubleshoot' are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (autonomous root-cause investigation) and actively reduces conflict risk with explicit anti-triggers ('Do NOT trigger on fix this bug when the cause is obvious, or on simple error-message lookups').

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
korchasa/flowai-plugins
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.