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.

77

Quality

97%

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

92%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.

A well-structured instruction skill with concrete actionable guidance, a validated multi-step workflow, and exemplary one-level-deep progressive disclosure via a routing table. The only soft spot is minor conceptual padding that assumes too little of Claude.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized tables and a tight how-to, but a few sections re-explain concepts Claude already knows - the ISTQB definition of exploratory testing and the scripted-vs-exploratory comparison table - that could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance: the exact charter syntax 'Explore <area> with <tools> to discover <information>' with a worked example, numeric TBS healthy ranges, the PROOF letter definitions, and a needs-to-lens routing table pointing to templates.

5 / 5

Workflow Clarity

The 6-step 'How to use' sequence is clearly ordered with an explicit validation checkpoint and feedback loop - 'if T < 50%, stop and fix the cause... then re-run the session before aggregating' - plus timing deadlines (within 30 min, within 24h).

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references (all 9 referenced files exist), each split by concern and indexed through a routing table that maps session needs to the right reference file.

5 / 5

Total

19

/

20

Passed

Description

100%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, third-person description that names concrete SBTM actions, multiple natural trigger scenarios, an explicit 'Use when' clause, and a clear boundary against sibling skills. It answers what, when, and how-it-differs without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full SBTM cycle - 'charters (Explore X with Y to discover Z), 60-90 minute sessions, session sheets with TBS metrics, and the PROOF debrief' plus 'budgeting the available hours to debriefing what was found' - giving comprehensive, non-vague coverage.

5 / 5

Completeness

Explicitly answers both what ('Plans and runs time-boxed exploratory testing... charters, sessions, session sheets with TBS metrics, PROOF debrief') and when ('Use when deciding what to explore with the time available, and how to run and record those sessions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural scenario phrases a tester would actually say - 'tester hours are scarce before a release', 'code freeze', 'year-end payroll', 'device and environment the scripted suite never touches', 'what to explore with the time available' - across several realistic triggering situations.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche and explicitly disambiguates from siblings - 'Broader than exploratory-charter-author, which writes one charter document: this owns the whole cycle' - so it is unlikely to trigger for the wrong skill.

5 / 5

Total

20

/

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