Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-reason
Umbrella for FPF-style structured reasoning in a haft project. Carries the full reasoning palette in one place: framing, exploration, comparison, verification, notes, plus slideument patterns (NQD, Goldilocks, BLP, Scaling-Law Lens). Make sure to use this skill whenever the operator wants structured thinking but the workflow isn't pre-named — phrases like "давай подумаем", "помоги разобраться", "let's think this through", "structured approach", "apply FPF here", "FPF reasoning", "haft this" — or
Passed 14 of 18 test cases with the skill, and 9 of 18 without it.
and 5 more in the full report
8 fixed9 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need general flow orientation for our order checkout processing system, but we do not have a specific code symbol anchor yet. What tool action should be used to explore this code area?
| Checked | Without skill | With skill |
|---|---|---|
| Selects the explore action mode for general code-area orientation. | Missed | Passed |
The instructions your model reads when the skill loads.
Contract truth: source-native FPF Query and typed-memory resolve, neighborhood, and recall are V9 CONTRACT capabilities. Source, schema, skill, or local-test presence is not installed-runtime proof and does not establish Pi host parity. A readiness claim requires current EXACT-CANDIDATE EVIDENCE from P14 tied to one exact candidate; RC or release status additionally requires release authority. Pi support is an experimental compatibility carrier; stable host parity is not proven. Do not infer CURRENT PRODUCT status from contract inclusion or evidence alone.
For purely mechanical, status-only, or exact project-lookup work where no FPF
pattern choice is material, caller abstention is the result: skip FPF Query and
do the bounded work directly. Do not fabricate
QueryResult(kind="abstained"); no query ran. Query when pattern applicability
is material or uncertain.
Name the current object, question, relations, constraints, evidence, and
smallest useful result. Query haft_query(action="fpf", mode="concern", query="<object + question + terms>"); compare README practical-use cards, use
the source ToC as the identifier/keyword index, recover exact source units with
mode="lookup" or non-broadening mode="inspect", and inspect the selected
pattern's full body. Retrieval returns source candidates. Returned source
material is not applicability, selection, recommendation, evidence,
precedence, or authority.
For a non-English concern, keep the operator's wording in query and add
precise English or FPF terms in known_context. Those terms are required: the
bundled source is English, a measured 6 of 6 Russian concerns returned zero
candidates without them, and the same concerns with English known_context
resolved to the exact card at rank 1. Do not translate query itself.
In ordinary working use, identify the selected direct pattern by PatternID,
title, and stable source reference. Do not routinely reproduce source spans,
repository-local paths, line ranges, hashes, revisions, or other provenance.
Request trace or audit provenance only when the current use requires it.
Keep exact identifier namespaces separate:
test cases passed, vs 9 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.