CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/exploratory-testing

Session-based exploratory testing per the Bachs' SBTM: authoring charters (Explore X with Y to discover Z), running time-boxed sessions (60-90 min), logging session sheets with TBS metrics, and closing with the PROOF session debrief (Past, Results, Outlook, Obstacles, Feelings). Bundles the classic exploration heuristics as references: Whittaker's seven test tours (Feature, Money, Landmark, Intellectual, Bad-data, Configuration, Garbage collector's), Kelly's FCC CUTS VIDS recon tours, Bach's SFDPOT what-to-vary catalog, Bolton's HICCUPPS-F oracle heuristic, and Bach's CRUSSPIC STMPL quality criteria - plus a ready-to-fill charter-card template and a session-sheet review checklist. Use when planning, chartering, running, debriefing, or reviewing an exploratory testing session, or when picking a test tour, heuristic, or oracle mid-session. For scripted manual test cases, use manual-test-script-author instead.

86

1.01x
Quality

91%

Does it follow best practices?

Impact

86%

1.01x

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%Weight 40%Scale 1-5

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

Well-structured content with actionable, specific guidance and clear progressive disclosure into real reference files. Minor conciseness and code-example gains are the only room for improvement.

Suggestions

Tighten the scripted-vs-exploratory comparison table or fold it into prose to reduce token load where the distinction is already made in text.

Consider adding a minimal fill-in-the-blank session-sheet snippet inline so the core artifact is copy-paste ready before users open the reference.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's testing knowledge without padding; the ISTQB quote and comparison table are load-bearing rather than filler. Slightly trimmed table rows could tighten it further, so it sits just below the lean anchor.

4 / 5

Actionability

Concrete charter formula, exact time-boxes (60-90 min, ~2h cap), and precise TBS healthy ranges (T 60-80%, B 10-20%, S 10-15%) with a need-to-lens-to-reference routing table. As an instruction-only skill it lacks executable code, which is appropriate, leaving it just below the copy-paste-ready anchor.

4 / 5

Workflow Clarity

The 6-step 'How to use' sequence has an explicit validation checkpoint (step 4: 'if T < 50%, stop and fix the cause... then re-run the session before aggregating') and feedback loop, reinforced by the anti-patterns table.

5 / 5

Progressive Disclosure

Overview body points to nine one-level-deep references via a clear routing table and inline links; every referenced file exists in the bundle, making navigation easy and well-signaled.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, specific description that clearly states capabilities, trigger conditions, and skill boundaries. Trigger-term coverage is very good though not exhaustive of every colloquial phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('authoring charters (Explore X with Y to discover Z)', 'running time-boxed sessions (60-90 min)', 'logging session sheets with TBS metrics', 'closing with the PROOF session debrief') plus the bundled heuristic catalogs, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (SBTM workflow plus bundled reference heuristics) and 'when' ('Use when planning, chartering, running, debriefing, or reviewing...'), with concrete trigger phrases and an explicit boundary clause.

5 / 5

Trigger Term Quality

Strong natural triggers ('planning, chartering, running, debriefing, or reviewing an exploratory testing session', 'picking a test tour, heuristic, or oracle mid-session') with good synonym coverage; a few colloquial variants are missing, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear SBTM/exploratory-testing niche with distinct triggers and an explicit disambiguation against the scripted sibling ('For scripted manual test cases, use manual-test-script-author instead'), minimizing conflict risk.

5 / 5

Total

19

/

20

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