菜单
Use whenever the user runs, configures, or debugs Explorbot from the command line — choosing freesail/explore/test/plan/research, asking what a flag does, asking where an artifact lives, or troubleshooting a failed run. Guide-only — you present the commands/paths and the user runs them.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a QA Sprint Progress Summary Report from Testomat.io TMS data. Use when the user wants to produce a structured end-of-sprint report covering test design coverage, execution results, defect trends, and quality signals. The skill reads data via Testomat.io MCP tools, maps it to the report sections, and outputs an `.html` file by default (or `.md` if explicitly requested).
Detect redundant tests, duplicated test logic, semantic overlaps, and parameterization opportunities across the entire test suite. Present recommendations and request user approval before refactoring.
Map test cases — manual (markdown) and automated e2e (Playwright, Cypress, WebdriverIO, CodeceptJS, Puppeteer, Appium) — to source code files and produce a `coverage.tests.yml` mapping consumed by `@testomatio/reporter --filter "coverage:..."`. Use this skill when the user wants to run only the tests affected by a code change, generate a coverage file (manual, e2e, or both), build a traceability matrix between tests and source code, or set up change-aware regression.
Orchestrate the complete test case lifecycle from requirements to uploading to TMS (Test Management System). Generate test cases, improve existing ones, analyze test coverage, add test reporter, upload to TMS, write new autotests, fix/heal autotests. Use this skill when you need to manage the entire testing workflow including generation, improvement, coverage, and sync with Testomat.io or do one of these tasks. This is the tactical/execution layer triggered by concrete task verbs — for strategic intent ("where do I start", "improve our QA process", "review our quality", "QA maturity review") use the `qa-lead-strategy-advisor` skill instead.
This skill converts manual test cases into production-ready automated test scripts. It analyzes the existing automation framework, interprets manual test steps, and generates maintainable tests following automation best practices. Use this skill whenever the user wants to automate manual test cases, expand test coverage, or create end-to-end automated flows from existing test documentation.
Diagnose and fix failing automated tests. Analyzes failures, inspects DOM, identifies root causes, and applies targeted fixes using framework tools and MCP/CLI debug modes. Use when tests fail, are flaky, or behave inconsistently (e.g., pass locally but fail in CI).
| name | explorbot-fundamentals |
| description | Use whenever the user runs, configures, or debugs Explorbot from the command line — choosing freesail/explore/test/plan/research, asking what a flag does, asking where an artifact lives, or troubleshooting a failed run. Guide-only — you present the commands/paths and the user runs them. |
| license | MIT |
| metadata | {"author":"Testomat.io","version":"0.1.0"} |
Explorbot is an autonomous AI web-testing CLI. It drives its own browser (CodeceptJS → Playwright) and works in cycles of research → plan → test.
The installed CLI and the installed package's docs/ tree are the source of truth — do not paraphrase them from memory. Discover commands and read docs at the moment of use.
Docs ship inside the npm package. After npm i explorbot, they're at:
<project root>/node_modules/explorbot/docs/
That's the only place to read them from in a typical user project. Do not look in the skill's own folder, do not look in a project-level docs/ (that belongs to the user's app), do not fetch from the web. If node_modules/explorbot/docs/ doesn't exist, Explorbot isn't installed → route the user to explorbot-setup.
(For an Explorbot contributor working in the explorbot repo itself, docs are at <repo root>/docs/. Detect this by checking for package.json with "name": "explorbot" at the project root. Everyone else: node_modules/explorbot/docs/.)
Always run the CLI's own help before answering a "how do I…" or "what flag…" question:
npx explorbot --help # list every command
npx explorbot <command> --help # flags and options for one command
These outputs match the installed version. Any hardcoded list (in skills, blog posts, or your own memory) can be stale.
Pick the file that matches the topic when the question comes up — do not pre-load summaries. All paths below are relative to node_modules/explorbot/docs/ (or the repo's docs/ for contributors).
| Topic the user is asking about | Open |
|---|---|
| Is this app even suitable for explorbot? | prerequisites.md |
| Full list of CLI + TUI commands and flags | commands.md |
Config file shape, dirs:, rules wiring | configuration.md |
| AI providers (OpenRouter / OpenAI / Anthropic / Groq / Cerebras / Azure) | providers.md |
| Knowledge files (URL patterns, frontmatter, interpolation) | knowledge.md |
| Planner, planning styles, plan markdown format | planner.md, test-plans.md |
| Researcher (page analysis) | researcher.md |
| Page interaction model (locators, ARIA, iframes) | page-interaction.md |
| Re-running generated tests with healing | rerun.md |
| Generated test code (Playwright / CodeceptJS) | automated-tests.md |
| Hooks | hooks.md |
| Reporting (HTML/MD/Testomat.io) | reporting.md |
| Tracing / Langfuse / observability | observability.md |
| Library / programmatic use | scripting.md, npm-package.md |
| API testing | api-testing.md |
| Doc collector | doc-collector.md |
If the topic isn't in this table, ls node_modules/explorbot/docs/ and pick the matching file by name.
An agent can run only the non-interactive CLI (explorbot explore, explorbot test, explorbot plan, explorbot research, explorbot navigate, etc.). These run headless and exit.
explorbot start launches an interactive terminal UI (TUI). An agent cannot operate a TUI — never try to launch or drive it. If the user wants interactive mode, tell them to run explorbot start [path] themselves.
node_modules/explorbot/ exists. If not → route to explorbot-setup.npx explorbot … --help) or a concept/config/feature (→ open the matching file in node_modules/explorbot/docs/).node_modules/explorbot/docs/knowledge.md, npx explorbot explore --help).node_modules/explorbot/ is missing.output/explorbot.log + Langfuse traces.node_modules/explorbot/docs/configuration.md first.--help doesn't show it, it doesn't exist.node_modules/explorbot/docs/prerequisites.md says it's for CRUD-heavy apps.