Agent skill

Exploratory Testing Advanced

by proffesor-for-testing in proffesor-for-testing/agentic-qe

Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours.

MITAuto-check passedTesting & QA

Install Exploratory Testing Advanced

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill exploratory-testing-advanced -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe exploratory-testing-advanced --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/exploratory-testing-advanced .claude/skills/exploratory-testing-advanced && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
exploratory-testing-advanced
GitHub stars
494
Token cost
~1.9k tokens
SKILL.md length
536 words
Files
2 (incl. references)
Skills in repo
95
Repo updated
First seen
Licence
MIT

At a glance

Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours.

  • Works in 5 steps: CREATE charter with mission, scope, and… → APPLY heuristics: SFDIPOT (quality… → EXPLORE systematically using test tours… → …
  • Planning exploration sessions
  • SKILL.md covers Quick Reference Card, Session Note Template, Agent-Assisted Exploration and Agent Coordination Hints, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Exploratory Testing Advanced is an agent skill from proffesor-for-testing/agentic-qe. Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Use when planning exploration sessions, investigating bugs, or discovering unknown quality risks.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/heuristic-cheatsheet.md`).

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Planning exploration sessions
  • Investigating bugs
  • Discovering unknown quality risks

Example prompts

  • “/exploratory-testing-advanced”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. CREATE charter with mission, scope, and time-box (45-90 min)
  2. APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)
  3. EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)
  4. DOCUMENT findings in real-time with notes, screenshots, evidence
  5. DEBRIEF: What learned? What's next? Share via agent memory

What it can do on your machine

Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Exploratory Testing Advanced loads about 1.9k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 536 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 536 words, ~1,870 tokens.

Download SKILL.mdSave it as .claude/skills/exploratory-testing-advanced/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
exploratory-testing-advanced
description
Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Use when planning exploration sessions, investigating bugs, or discovering unknown quality risks.
category
testing-methodologies
priority
high
tokenEstimate
1000
agents
qe-flaky-test-hunter, qe-visual-tester, qe-quality-analyzer
implementation_status
optimized
optimization_version
1
last_optimized
2025-12-02
quick_reference_card
true
tags
exploratory, sbtm, rst, heuristics, test-tours, session-based
trust_tier
0

Advanced Exploratory Testing

<default_to_action> When exploring software or investigating quality risks:

  1. CREATE charter with mission, scope, and time-box (45-90 min)
  2. APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)
  3. EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)
  4. DOCUMENT findings in real-time with notes, screenshots, evidence
  5. DEBRIEF: What learned? What's next? Share via agent memory

Quick Heuristic Selection:

  • What to test → SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time)
  • Recognize problems → FEW HICCUPPS (Familiar, Explainable, World, History, Image, Comparable, Claims, Users, Product, Purpose, Standards)
  • Navigate app → Test Tours (12 types for different exploration strategies)

Critical Success Factors:

  • Exploration is skilled, structured thinking - not random clicking
  • Document discoveries, not pre-planned test cases
  • Pair testing reveals more than solo exploration </default_to_action>

Quick Reference Card

When to Use
  • Investigating new or changed features
  • Finding bugs automation misses
  • Learning unfamiliar systems
  • Risk discovery before test planning
Session Structure (SBTM)
PhaseDurationActivity
Charter5 minDefine mission, scope, focus
Explore45-75 minSystematic investigation
NoteContinuousDocument findings real-time
Debrief10-15 minSummarize, prioritize, share
SFDIPOT Heuristic (What to Test)
LetterFocusExample Questions
StructureIs it properly composed?Code structure, UI layout, data schema
FunctionDoes it do what it should?Core features work correctly
DataHandles data correctly?CRUD, validation, persistence
InterfacesInteracts well?APIs, UI, integrations
PlatformWorks in environment?Browsers, OS, devices
OperationsCan be used/managed?Install, config, monitor
TimeHandles timing?Concurrency, timeouts, scheduling
FEW HICCUPPS Oracle (Recognize Problems)
Consistency WithCheck
Familiar problemsDoes this look like a known bug pattern?
ExplainableCan behavior be explained rationally?
WorldMatches real-world expectations?
HistoryConsistent with prior versions?
ImageMatches brand/product image?
ComparableSimilar to competing products?
ClaimsMatches specs/docs/marketing?
UsersMeets user expectations?
PurposeFulfills intended purpose?
StatementsMatches what devs said?
Show full SKILL.md (237 more words)Show less
Test Tours (12 Types)
TourStrategy
Business DistrictCritical business flows
HistoricalWhere bugs clustered before
Bad NeighborhoodKnown problem areas
MoneyRevenue-impacting features
LandmarkNavigate by key features
IntellectualComplex, thinking-intensive features
FedExFollow data through system
Garbage CollectorCleanup and edge cases
MuseumHelp docs and examples
Rained-OutWhat happens when things fail?
Couch PotatoMinimal effort paths
Obsessive-CompulsiveRepetitive actions

Session Note Template

markdown
**Charter:** Explore [area] to discover [what] focusing on [heuristic]
**Time-box:** 60 min | **Tester:** [name] | **Date:** [date]

## Session Notes
- [timestamp] Observation/finding
- [timestamp] Bug: [description] - [severity]
- [timestamp] Question: [unclear behavior]

## Findings Summary
- Bugs: X (Critical: Y, Major: Z)
- Questions: X
- Ideas: X

## Coverage
- Areas explored: [list]
- Heuristics used: [SFDIPOT areas]
- % Time on: Bug investigation 30%, Exploration 50%, Setup 20%

## Next Steps
- [ ] Deep dive on [area]
- [ ] Follow up on question about [topic]

Agent-Assisted Exploration

typescript
// Collaborative exploration session
await Task("Exploratory Session", {
  charter: 'Explore checkout flow for payment edge cases',
  duration: '60min',
  heuristics: ['SFDIPOT', 'FEW_HICCUPPS'],
  tour: 'money',
  collaboration: 'human-navigator-agent-driver'
}, "qe-flaky-test-hunter");

// Agent generates test variations while human observes
await Task("Edge Case Generation", {
  area: 'payment-form',
  variations: ['boundary-values', 'invalid-inputs', 'concurrent-submits']
}, "qe-test-generator");

// Visual exploration
await Task("Visual Exploration", {
  tour: 'landmark',
  focus: 'responsive-breakpoints',
  compare: 'baseline-screenshots'
}, "qe-visual-tester");

Agent Coordination Hints

Memory Namespace
aqe/exploratory/
├── sessions/*           - Session notes and findings
├── charters/*           - Reusable charter templates
├── bug-clusters/*       - Historical bug patterns
└── heuristic-results/*  - What heuristics revealed
Fleet Coordination
typescript
const exploratoryFleet = await FleetManager.coordinate({
  strategy: 'exploratory-testing',
  agents: [
    'qe-flaky-test-hunter',   // Pattern recognition
    'qe-visual-tester',       // Visual anomalies
    'qe-quality-analyzer'     // Risk assessment
  ],
  topology: 'mesh'
});

Pairing Patterns

PatternHuman RoleAgent Role
Driver-NavigatorNavigate strategyExecute variations
Strong-StyleDictate actionsRecord findings
Ping-PongObserve one areaExplore another


Remember

Exploratory testing = simultaneous learning, test design, and test execution.

Not random clicking. Structured, skilled investigation guided by heuristics and oracles. Document discoveries in real-time. Pair testing amplifies findings.

With Agents: Agents generate variations, recognize patterns, and maintain session notes while humans apply judgment and intuition. Combine agent thoroughness with human insight.

Gotchas

  • Agent treats exploratory testing as scripted test execution — remind it: exploration means learning + adapting in real-time
  • Session notes from agents lack the "why I tried this" reasoning — explicitly ask for decision rationale
  • 90-minute sessions cause context overflow — cap at 45 minutes with explicit debrief
  • Agent defaults to happy-path exploration — explicitly assign "Bad Neighborhood" or "Saboteur" tours for negative testing
  • SFDIPOT heuristics are misapplied when agent doesn't understand the domain — provide domain context upfront

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in assets/skills/exploratory-testing-advanced of proffesor-for-testing/agentic-qe.

  • SKILL.md
  • references/heuristic-cheatsheet.md

Open the folder on GitHubat commit 829d030

Compare with similar skills

Exploratory Testing Advanced next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Exploratory Testing Advanced compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Exploratory Testing Advanced this skillproffesor-for-testing/agentic-qe494—~1.9kAutomated safety check: PassMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Minimal Run And Auditlllllllama/RigorPilot-Skills4972 repos~691Automated safety check: PassMIT
Moav E2EMotherofallVPNs/MoaV448—~1.9kAutomated safety check: NotesMIT
Anchor Reprolynxlangya/techne1051 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Minimal Run And Audit

    lllllllama/RigorPilot-Skills

    Rigor Run skill for README-first deep learning repo reproduction.

    497 GitHub starsUsed in 2 repos~691 tokens
    Testing & QAAuto-check passed
  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • Anchor Repro

    lynxlangya/techne

    Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.

    105 GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed
  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1k GitHub stars~2.2k tokensUpdated 29 days ago
    Testing & QAAuto-check passed

More from proffesor-for-testing/agentic-qe

All 95 skills in this repo
  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    494 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed
  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    494 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed
  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    494 GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed
  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    494 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    494 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check: notes
  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Exploratory Testing Advanced

What does Exploratory Testing Advanced do?

Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Exploratory Testing Advanced is an agent skill from proffesor-for-testing/agentic-qe. Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours.

When should I use Exploratory Testing Advanced?

Exploratory Testing Advanced fits situations like: planning exploration sessions; investigating bugs; discovering unknown quality risks.

How do I install Exploratory Testing Advanced in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill exploratory-testing-advanced -a claude-code`. Or copy the skill folder (assets/skills/exploratory-testing-advanced in proffesor-for-testing/agentic-qe) into .claude/skills/exploratory-testing-advanced in your project. Claude Code loads it when a task matches its description.

How do I install Exploratory Testing Advanced in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill exploratory-testing-advanced -a codex`. Or copy the skill folder (assets/skills/exploratory-testing-advanced in proffesor-for-testing/agentic-qe) into .agents/skills/exploratory-testing-advanced in your project. Codex loads it when a task matches its description.

Can I use Exploratory Testing Advanced in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill exploratory-testing-advanced -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exploratory-testing-advanced, .gemini/skills/exploratory-testing-advanced, .github/skills/exploratory-testing-advanced and .opencode/skills/exploratory-testing-advanced in your project.

What does Exploratory Testing Advanced need to run?

SKILL.md names no scripts, command-line tools or credentials: Exploratory Testing Advanced is instructions for the agent only.

Does Exploratory Testing Advanced access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Exploratory Testing Advanced safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Exploratory Testing Advanced use?

Exploratory Testing Advanced is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Exploratory Testing Advanced use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 506 tokens, read only when the agent opens those files.

What are the alternatives to Exploratory Testing Advanced?

Skills that share tags, products or a category with Exploratory Testing Advanced: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Exploratory Testing Advanced?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on October 4, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.