exploratory
/exploratory
Create exploratory testing charters and session ideas for a feature — where to look for bugs, what to try, tours and heuristics. Use when the user wants exploratory testing ideas, a testing tour, or "what should I test" guidance for a feature.
- Author
- MohamedRamadanSalah ↗
- Repository
- claude-qa-toolkit ↗
- Licence
- MIT
- Last repository change
- 31.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create exploratory testing charters and session ideas for a feature — where to look for bugs, what to try, tours and heuristics. Use when the user wants exploratory testing ideas, a testing tour, or "what should I test" guidance for a feature.
Triggers from the description
Original author description
Create exploratory testing charters and session ideas for a feature — where to look for bugs, what to try, tours and heuristics. Use when the user wants exploratory testing ideas, a testing tour, or "what should I test" guidance for a feature.
How it works
- Output
- Where to find good ideas
SKILL.md preview
--- name: exploratory description: Create exploratory testing charters and session ideas for a feature — where to look for bugs, what to try, tours and heuristics. Use when the user wants exploratory testing ideas, a testing tour, or "what should I test" guidance for a feature. --- # Exploratory Testing Guide Help the tester plan exploratory testing sessions for a feature they describe. ## Output Produce 3-6 **charters**, each in this format: > **Charter:** Explore <area> using <resources/approach> to discover <kind of problems> > **Time box:** 30-60 min > **Ideas to try:** 5-10 concrete, creative things to attempt ## Where to find good ideas Apply heuristics relevant to the feature (pick what fits, don't dump all): - **CRUD tour** — create, read, update, delete everything; delete things that are in use elsewhere - **Interruption tour** — cancel mid-operation, refresh during save, kill network, go back button, double-click submit - **Data tour** — extreme values, wrong formats, copy-paste with formatting, autofill - **State tour** — expired session, second tab, concurrent edits by two users - **Permission tour** — every role tries every action, including via direct URL/API - **Environment tour** — small screen, slow network (throttle), different browser/locale/timezone - **History tour** — upgrade with old data, previously-saved drafts, legacy records End with a short **"Most likely bug hiding spots"** list — your top 3 guesses for where this specific feature will break, with reasoning.
Versions
The database has no other skills named exploratory.
Database snapshot: 13.11.2026 · package version f10ad16389e8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100exploratory-testing
Run structured exploratory testing sessions using test charters, timeboxing, and heuristics. Use when user says "exploratory testing", "charter-based testing", "explore the app", "unscripted testing", "session-based testing", "find unknown bugs", or needs to test an area without… - 100exploratory-charter
Create focused exploratory testing charters (\"Explore <target> with <resources> to discover <information>\") using the SFDIPOT product elements and Whittaker's testing tours, with time-boxes and a session sheet. Use when planning exploratory testing of a feature, a release or a… - 100exploratory-testing-advanced
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. - 98exploratory-heuristics
Exploratory testing toolkit — session-based test management (charters, time boxes, session sheets, debriefs), test heuristics (SFDPOT, FEW HICCUPPS consistency oracles, CRUD, goldilocks, interruptions), tours (money, landmark, back-alley, saboteur, all-nighter), a cheat sheet of… - 100planning-exploratory-testing
Runs session-based exploratory testing: writes charters, timeboxes sessions, applies coverage heuristics and tours, captures notes as evidence, debriefs, and converts findings into bug reports and automation candidates. Use when a feature needs testing before requirements… - 90exploratory-charter
Writes 3-5 ranked exploratory-testing charters for something that already shipped in a web app, from a feature file, an archived change, a ticket or a few words. Use for "what should we explore in X", "plan exploratory sessions for this feature", "where could this break", or a…