CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/sfdpot-exploratory-heuristic

Pure-reference catalog of James Bach's SFDPOT heuristic - 'San Francisco Depot' - a 'you are here' framework that catalogues what a tester can vary in a system to find bugs. Six dimensions: Structure, Function, Data, Platform, Operations, Time. Use as a what-to-vary checklist during an exploratory session, complementing HICCUPPS-F (which catalogues what to compare against).

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 reference skill: concise overview, concrete step-by-step usage with a worked example, clear feedback loops, and proper progressive disclosure to a verified one-level-deep reference file. Anti-patterns and limitations add practical guardrails without padding.

DimensionReasoningScore

Conciseness

The body is lean and purposeful: it explains the niche SFDPOT heuristic (justified, not common Claude knowledge) without padding basic concepts, and every section (dimensions table, worked example, anti-patterns, limitations) earns its place.

3 / 3

Actionability

Five concrete 'How to use' steps, per-dimension 'Sample variables', and a fully worked checkout charter that doubles as a copy-paste template give specific, actionable guidance despite the absence of code (appropriate for an instruction-only heuristic skill).

3 / 3

Workflow Clarity

The 'How to use' section is a clearly sequenced 5-step process with explicit feedback loops - 're-walk when stuck' and 'Interpret with an oracle... reach for HICCUPPS-F' - serving as validation/interpretation checkpoints.

3 / 3

Progressive Disclosure

The overview body signals a one-level-deep reference (references/six-dimensions-catalog.md, verified to exist) for the full variable catalog, splitting deep content out while keeping the skill body a navigable overview.

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, concrete description that names its niche, enumerates its six dimensions, gives explicit when-to-use guidance, and explicitly differentiates itself from the related HICCUPPS-F skill. It avoids vague fluff and over-claims.

DimensionReasoningScore

Specificity

Names the concrete capability ('catalogues what a tester can vary in a system to find bugs') and lists all six dimensions (Structure, Function, Data, Platform, Operations, Time), which is specific and comprehensive rather than vague.

3 / 3

Completeness

Answers both what (a variation catalog across six dimensions) and when, with explicit trigger guidance 'Use as a what-to-vary checklist during an exploratory session' equivalent to a 'Use when' clause, so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Covers natural terms a tester would say - 'SFDPOT', 'San Francisco Depot', 'exploratory session', 'what to vary', 'find bugs', 'HICCUPPS-F' - matching the breadth of the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Carves a clear, non-conflicting niche ('complementing HICCUPPS-F which catalogues what to compare against') that distinguishes it from sibling heuristics.

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