Trace
Skill Verified ActiveEvidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
To provide an evidence-driven tracing lane that orchestrates competing tracer hypotheses, aiding in the explanation of 'why' observed results occurred.
Features
- Orchestrates competing tracer hypotheses
- Gathers evidence in parallel
- Ranks hypotheses and proposes next probes
- Supports runtime bugs, performance, and architecture analysis
Use Cases
- Tracing runtime bugs and regressions
- Explaining performance, latency, or resource behavior
- Conducting architecture, premortem, or postmortem analysis
- Tracing scientific or experimental results
Non-Goals
- Collapsing into a generic fix-it coding loop
- Providing a generic debugger summary
- Dumping raw worker output
- Claiming fake certainty when evidence is incomplete
Installation
First, add the marketplace
/plugin marketplace add Yeachan-Heo/oh-my-claudecode/plugin install oh-my-claudecode@omcQuality Score
VerifiedTrust Signals
Similar Extensions
LangSmith Observability
99LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
Create Command
100Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
Project Development
100This skill should be used when the user asks to "start an LLM project", "design batch pipeline", "evaluate task-model fit", "structure agent project", or mentions pipeline architecture, agent-assisted development, cost estimation, or choosing between LLM and traditional approaches.
Write A Skill
100Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Extract
100Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.