trace

Generates competing hypotheses and evaluates evidence to explain observed outcomes.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill trace-xz1220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/trace
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill trace-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you explain why a specific observed result happened by structuring competing hypotheses and collecting supporting and contradicting evidence instead of looping on generic debugging or implementation.

Core Features & Use Cases

  • Competing Explanations: Generates multiple intentional hypotheses to explain the same observation, including explicit evidence for and against each.
  • Evidence-graded Reasoning: Prioritizes stronger evidence types (controlled reproduction, direct artifacts, multi-source corroboration) and downgrades weaker/indirect claims.
  • Discriminating Next Step: Produces a single highest-value probe that can most quickly collapse uncertainty, plus a clear critical unknown that blocks the leading explanation.

Quick Start

Ask an AI to run the trace workflow by providing the observation you want to explain and requesting competing hypotheses with an evidence-backed ranking and the most discriminating next probe.

Frequently Asked Questions about trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform root cause analysis for a confusing performance regression?

Root cause analysis for a performance regression involves generating competing hypotheses and collecting supporting and contradicting evidence for each. This approach grades evidence by strength to explain why the observed outcome occurred.

What is the best way to structure an investigation for ambiguous architectural postmortems?

Structuring an investigation for ambiguous architectural postmortems requires preserving observations, hypotheses, and evidence gaps. This method applies falsification and re-ranking to competing explanations to find evidence-backed conclusions.

How do I stop looping on generic debugging and find the real cause of an observed behavior?

To stop generic debugging loops, generate multiple intentional hypotheses explaining the same observation. Prioritize stronger evidence like controlled reproduction and direct artifacts over weaker indirect claims.

Can I use hypothesis-driven investigation for experimental configuration trace-back?

Yes, hypothesis-driven investigation applies to experimental configuration trace-back. It processes evidence-dense scenarios by evaluating competing explanations and identifying a discriminating probe to collapse uncertainty.

What should I do next when my investigation hits a critical unknown and evidence gaps remain?

When evidence gaps remain, identify a single highest-value discriminating probe. This probe quickly collapses uncertainty and resolves the critical unknown blocking your leading explanation.

Does evidence-graded reasoning work for analyzing resource behavior anomalies?

Evidence-graded reasoning works for resource behavior analysis by downgrading weaker indirect claims. It prioritizes multi-source corroboration and controlled reproduction to validate hypotheses explaining the anomaly.