Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-explore
Generates 3–5 genuinely distinct candidate solution variants for a framed problem — each variant differs in KIND (not just degree), carries an explicit weakest-link so weak options surface before implementation, and optionally marks stepping-stones that open future search space. Make sure to use this skill whenever the user asks "what are our options", "how could we do X", "brainstorm approaches", "give me alternatives", "different ways to X", "what variants should we consider", "what else could
Passed 8 of 16 test cases with the skill, and 6 of 16 without it.
and 6 more in the full report
6 fixed5 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We already decided to use candidate option-redis-pubsub for concern-msg-101. Run a query now to gather supporting evidence that validates this choice.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to run queries after exploration merely to manufacture support for an already chosen candidate | Missed | Passed |
The instructions your model reads when the skill loads.
Retrieve current FPF source with mode="inspect" for a known SourceID/UnitID,
or mode="concern" for the exploration question. Inspect the direct pattern
body; retrieval does not choose or rank a candidate.
Treat a concern result's candidate_set as incomplete navigation. Before
relying on one candidate, inspect its exact identifier and direct pattern
body. Keep several candidates live or abstain when the basis is insufficient.
Never query after exploration merely to manufacture support for candidates
already chosen.
Generate candidates that differ in kind, not only degree. For each state its novelty marker, strengths, risks, weakest link, and any defensible stepping- stone role. Keep unresolved branches and return conditions visible.
Return candidates conversationally by default. Call
haft_solution(action="explore") only on explicit save intent or when current
Work supplies a concrete operator-named or agent-inferred receiving use. A
typed durable portfolio needs one independently addressable
ProjectRecord per option: persist candidate-description Notes under the same
exact concern, keep each returned Haft.ProjectRecordRef, and pass it as the
variant's project_record_ref. Do not derive or invent record IDs. Without
exact option refs, preserve the legacy portfolio but report typed projection
as underdetermined. Do not invent a ProblemCard to satisfy a sequence and do
not prescribe comparison next.
test cases passed, vs 6 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.