Skip to content
TrustedSkillsbeta
Back to all skills

Exploratory Testing Advanced

Checked
proffesor-for-testing·vlatest·testing·MIT

Automatically generates diverse test cases and explores edge conditions beyond predefined scenarios to uncover hidden defects.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

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

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned proffesor-for-testing/agentic-qe at 124d8c735e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
124d8c735e
Manifest
assets/skills/exploratory-testing-advanced/SKILL.md
Scanned
4 files, 502 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform advanced exploratory testing of software. It guides the agent through a structured process involving charter creation (defining mission and scope), heuristic application (SFDIPOT and FEW HICCUPPS), systematic exploration using test tours, real-time documentation of findings, and debriefing. The goal is to uncover hidden defects and quality risks beyond predefined scenarios.

When to use it

  • Investigating new or changed software features.
  • Finding bugs that automated tests might miss.
  • Learning about unfamiliar systems.
  • Discovering potential quality risks before formal test planning.

Key capabilities

  • Charter Creation: Defines the scope, mission and time-box for testing sessions.
  • Heuristic Application: Uses SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time) to guide what to test and FEW HICCUPPS (Familiar, Explainable, World, History, Image, Comparable, Claims, Users, Product, Purpose, Standards) to identify potential problems.
  • Test Tours: Employs 12 different exploration strategies for systematic testing.
  • Real-time Documentation: Records findings with notes and screenshots.
  • Debriefing: Summarizes learnings and plans next steps.

Example prompts

  • "Create a charter to explore the user authentication flow, focusing on security risks."
  • "Apply the SFDIPOT heuristics to investigate the data validation process in this form."
  • "Use the 'Business District' test tour to explore the main navigation of this application."

Tips & gotchas

  • Exploratory testing with this skill requires structured thinking, not random clicking. Follow the charter and heuristic guidance for best results.
  • Focus on documenting discoveries rather than creating pre-planned test cases.
  • The session structure (Charter - Explore - Note - Debrief) is designed to be followed for optimal effectiveness.