Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evolution-foundation/dev-trace
Evidence-driven causal tracing with competing hypotheses.
Passed 17 of 20 test cases with the skill, and 5 of 20 without it.
and 13 more in the full report
14 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What two explicit elements must be produced in the final PROBE step of a multi-hypothesis trace into data sync drift?
| Checked | Without skill | With skill |
|---|---|---|
| The probe step must identify the critical unknown | Missed | Passed |
| The probe step must specify a discriminating experiment | Missed | Passed |
The instructions your model reads when the skill loads.
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Causal investigation with multi-hypothesis discipline. Generate at least 2 explanations, collect evidence FOR and AGAINST, rank by strength, end with a discriminating probe.
@hawk-debugger@hawk-debugger@scout-explorerDelegate to @trail-tracer:
Saved to workspace/development/debug/[C]trace-{topic}-{date}.md using the dev-trace-report.md template.
@trail-tracer (the executor)@hawk-debugger (when trace converges to a clear bug)@apex-architect (when trace reveals architectural issues)test cases passed, vs 5 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.