Skip to content
Skills Library
Programming · Testing

explore

/explore

Charter-driven exploratory testing of a running feature or endpoint. Dispatches the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing, CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an incremental report. Use when the user says "explore this endpoint", "poke at this feature", or wants hands-off exploratory testing of a live target.

Licence
MIT
Last repository change
14.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Charter-driven exploratory testing of a running feature or endpoint. Dispatches the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing, CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an incremental report. Use when the user says "explore this endpoint", "poke at this feature", or wants hands-off exploratory testing of a live target.

Triggers from the description

Chaos Specialistexplore this endpointpoke at this feature

Arguments

/explore --charter '<goal>' [target] [--probe-budget <n>] [--invariants '<expr,...>'] [--no-adversarial] [--force]
Original author description

Charter-driven exploratory testing of a running feature or endpoint. Dispatches the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing, CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an incremental report. Use when the user says "explore this endpoint", "poke at this feature", or wants hands-off exploratory testing of a live target.

How it works

  1. Worker constraints
  2. Parse Arguments
  3. Steps
Original SKILL.md headings · 39 lines, 286 words
SKILL.md preview
---
name: explore
description: >-
  Charter-driven exploratory testing of a running feature or endpoint. Dispatches
  the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics
  (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing,
  CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an
  incremental report. Use when the user says "explore this endpoint", "poke at
  this feature", or wants hands-off exploratory testing of a live target.
argument-hint: "--charter '<goal>' [target] [--probe-budget <n>] [--invariants '<expr,...>'] [--no-adversarial] [--force]"
user-invocable: true
allowed-tools: Read, Grep, Glob, Bash, Write, Skill, Agent
---

# Explore

Role: worker. This command is a thin entry point: it parses arguments, runs the
charter-quality + reachability pre-flight, then runs the
[`exploratory-testing`](../exploratory-testing/SKILL.md) skill as the
probe loop. It does not probe directly — the skill owns the protocol.

## Worker constraints

1. Probe a **running** target; do not fix anything. Critical defects go to `/triage`.
2. Stop at or before the probe budget; always leave a usable (possibly partial) report.
3. **Be concise.** Stream one line per probe to chat; detail lives in the report.

## Parse Arguments

Arguments: $ARGUMENTS

- `--charter '<goal>'` — **required**. `Explore [target] with [approach] to discover [concern]`.
- `target` — URL/endpoint/command under test (may be implied by the charter).
- `--probe-budget <n>` — default `15`.
- `--invariants '<expr,...>'` — per-probe invariants; a violation is Critical-immediate.
- `--no-adversarial` — skip adversarial expansion (on by default).
- `--force` — proceed past a charter-quality warning.

If `--charter` is absent, do not probe and do not write a report — emit exactly:

```
What should I investigate? Provide a charter: --charter '<goal>'
```

## Steps

1. **Charter quality** — evaluate the charter against the field-guide anti-patterns. On a match, emit a one-line warning and prompt to refine or re-run with `--force`; do not probe until acceptable or forced.
2. **Reachability** — baseline-request the target. If unreachable, report the URL + error and stop (no report).
3. **Run the skill** — invoke `exploratory-testing` with the parsed charter, budget, invariants, and flags. It runs the probe loop, adversarial expansion, defect classification, auto-triage, and writes `.dev-team-reports/explore-<YYYYMMDDThhmmss>.md` incrementally — ending with a "Next Exploration" section of 2–3 follow-up charters.

Surface the report path and any triaged defects in chat. On `/stop`, the skill finalizes a partial report.

Versions

RepositoryScoreLicence
This page · bdfinst/agentic-dev-team100MIT
yonatangross/orchestkit100MIT
yonatangross/orchestkit100MIT
rapiddweller/archkeel100MIT
zimoliao/scholaraio100MIT
artk0de/tearags-mcp100MIT
artk0de/tearags-mcp100MIT
artk0de/tearags-mcp100MIT
artk0de/tearags-mcp100MIT

Database snapshot: 13.11.2026 · package version 3b06a44b1fe0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100exploratory-testing
    Charter-driven exploratory testing — probe a running feature/endpoint with structured heuristics, evaluate charter quality, run adversarial expansion, classify defects, and auto-triage critical findings into an incremental report. Use when the user runs /explore, says "explore…
  • 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…
  • 100gvm-explore-test
    Use when running a timeboxed exploratory testing charter against built code, before doc-write. Triggered by /gvm-explore-test command or requests to run an exploratory tour, log defects in GWT form, or produce an explore-NNN session report. Writes a charter, drives…
  • 100explore-session
    WAY 18 — exploratory testing session, no requirements needed. Use when the user says "explore it", "exploratory test", "explore the app", "bug hunt", "exploratory session" — charter → live browser exploration → test-writer turns the flows and anomalies into playwright-bdd tests…
  • 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…
  • 85wicked-garden-qe-exploratory-tester
    Session-based, unscripted exploratory testing — the agent acts like a human tester. Charter-driven session, note-taking, bug hunting across UI and API. Use when: exploratory testing, unscripted session, charter-based bug hunting, heuristic-driven testing, fresh-eyes pass.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.