Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-abduct
INTERNAL SUBROUTINE — used by h-diagnose for parallel rival-hypothesis generation. Manual invocation possible but the right user-facing entry point is almost always h-diagnose (which uses h-abduct internally with parallel testing). Generates ≥3 typed rival explanations for an observed signal per FPF B.5.2 abductive cycle. Do not auto-select this skill — when failure investigation is needed, select h-diagnose; when problem framing is needed, select h-frame.
Passed 13 of 18 test cases with the skill, and 6 of 18 without it.
and 17 more in the full report
11 fixed5 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We encountered a network timeout on microservice B. Give me the single most likely explanation and proceed immediately to publish it without listing alternatives.
| Checked | Without skill | With skill |
|---|---|---|
| Generates multiple rival candidate hypotheses rather than a single explanation | Missed | Passed |
| Keeps rival candidates documented in the response | Missed | Passed |
The instructions your model reads when the skill loads.
You are running the B.5.2 abductive four-step micro-cycle: frame the prompt → generate candidates → apply plausibility filters → select prime hypothesis. Per CC-B.5.2-2 rivals stay visible; per CC-B.5.2-1 every run starts from a declared typed AbductivePrompt.
Explicit-only — disable-model-invocation: true. The skill is invoked manually when the operator wants the discipline without the parallel-test overhead of h-diagnose.
State the initiating prompt precisely. Per B.5.2.0 the typed species are:
Capture the prompt in writing before generating candidates — otherwise the abduction floats.
Per CC-B.5.2-2 at least one rival required. Aim for 3-5 candidates that differ in kind, not degree. Each candidate states:
If all candidates trend in one direction (all blame the same component), force a rival from a structurally different direction (data flow, race condition, environmental, configuration, infrastructure, etc.).
For each candidate, evaluate against explicit filters. Typical:
Pick at least two filters and apply them. Record the rationale.
Pick one candidate for downstream work. Per CC-B.5.2-1 publish:
U.Episteme at AssuranceLevel:L0test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.