CtrlK
BlogDocsLog inGet started
Tessl Logo

find-cause

Wraps investigation requests with evidence-chain discipline. Use when asked to find out why something happens, research a root cause, debug an issue, or investigate unexpected behavior. Transforms vague investigation requests into reproducible-proof investigations with a 5-step protocol — disambiguate, reproduce, read source, build evidence chain, present findings. Invoke with /find-cause followed by a description of what to investigate.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

73%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, highly actionable investigation protocol with excellent sequencing and validation. The main weakness is repetition of evidence templates and restated prohibitions that inflate token cost.

Suggestions

Define the CLAIM/EVIDENCE/VERIFIED/DEPENDS-ON entry format once and reference it from Steps 2-4 instead of repeating the full template three times.

Consolidate the 'Prohibited Behaviors' list so it does not restate rules already enforced inline in Steps 2 and 4 (e.g., reproduction-skipping), keeping only net-new prohibitions.

Consider extracting the Step 1.5 safety-check template and Step 0 capability-matrix template into a references/ file to reduce SKILL.md length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient instruction-focused prose with no concept padding, but the CLAIM/EVIDENCE/VERIFIED/DEPENDS-ON template repeats across Steps 2-4 and prohibited behaviors partly restate in-step rules.

3 / 5

Actionability

Concrete commands (command -v ...), exact AskUserQuestion formats, and copy-paste-ready templates dominate; minor gaps because core investigation steps are procedural templates rather than executable code.

4 / 5

Workflow Clarity

Tightly sequenced Steps 0-5 with explicit gates and pervasive validation checkpoints (disambiguation, success criteria, safety classification, VERIFIED flags, dependency tracking) plus feedback loops for recovery.

5 / 5

Progressive Disclosure

Single self-contained file with clear section headers and XML-tagged blocks giving good internal structure, but at ~278 lines with reusable templates some content could be externalized into reference files.

4 / 5

Total

16

/

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.

A strong, specific description that clearly states capabilities, triggers, and niche with concrete action enumeration and natural trigger synonyms. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names the protocol and enumerates concrete actions ('disambiguate, reproduce, read source, build evidence chain, present findings'), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (evidence-chain 5-step protocol) and 'when' (concrete trigger phrases), plus invocation guidance.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say with synonyms — 'find out why something happens', 'research a root cause', 'debug an issue', 'investigate unexpected behavior'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (evidence-chain-driven root-cause investigation) with a distinct /find-cause trigger, minimizing overlap with other skills.

5 / 5

Total

20

/

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
Jamie-BitFlight/claude_skills
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.