SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Investigate ambiguous failures using evidence-ranked hypotheses before editing code.
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
Original instructions from the publisher’s SKILL.md
# Investigate first Gather evidence before changing product code. - Separate observed symptom from inferred cause. - Trace inputs, state transitions, ownership boundaries, and failure output. - Rank hypotheses by evidence and cheap falsification value. - Do not edit until one credible mechanism explains evidence. - Stop exploration when evidence is sufficient to name cause or exact blocker. Report cause and proof. Make no fix unless task authorizes implementation.
Files included alongside SKILL.md in the publisher’s repository.