CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/hiccupps-f-heuristic

Pure-reference catalog of Michael Bolton's HICCUPPS-F oracle heuristic - the reference points a tester consults to decide 'is this a bug?': History, Image, Comparable products, Claims, Users' desires, Product (internal consistency), Purpose, Standards/statutes, plus Familiar problems. Use mid-session to test an observation against each oracle. For what to VARY use sfdpot-exploratory-heuristic, for what to MODEL use fcc-cuts-vids-heuristic, for quality criteria use crusspic-stmpl-heuristic.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured single-purpose reference skill: concise oracle definitions, a concrete worked example, an anti-patterns table, and clear sections throughout. It assumes Claude's intelligence and provides actionable guidance without padding.

DimensionReasoningScore

Conciseness

Lean reference catalog: each oracle gets a one-line definition and a tight source list, with no padding explaining what a bug or an oracle is — assumes Claude's competence and every section earns its place.

3 / 3

Actionability

For an instruction-only reference skill it gives concrete, copy-paste-ready guidance: the per-oracle questions to ask and a fully worked cart-total example walking H through F to a filing decision.

3 / 3

Workflow Clarity

The apply-it process is clearly sequenced in the worked example (H→I→C→C→U→P→P→S→F then conclude), with the anti-patterns table serving as error-recovery guidance; no destructive/batch step needs an explicit validation checkpoint.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the body is organized into clear, navigable sections (Overview, When to use, The nine oracles, Worked example, Anti-patterns, Limitations, References) with no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states a concrete capability, gives an explicit mid-session trigger, enumerates the nine oracles, and actively disambiguates from three sibling heuristics. No vagueness or over-claims.

DimensionReasoningScore

Specificity

Names the heuristic and enumerates all nine concrete oracle types (History, Image, Comparable products, ...) plus the action 'test an observation against each oracle' — multiple specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers both what (a pure-reference catalog of the HICCUPPS-F oracles) and when with an explicit trigger clause ('Use mid-session to test an observation against each oracle').

3 / 3

Trigger Term Quality

Includes natural tester phrasing like 'is this a bug?', 'mid-session', and 'observation' alongside the oracle names, giving good coverage of terms a user would naturally say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Explicitly routes sibling intents away ('For what to VARY use sfdpot-exploratory-heuristic, for what to MODEL use fcc-cuts-vids-heuristic, for quality criteria use crusspic-stmpl-heuristic'), carving a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents