manual-testing
Use this skill when you need to plan manual or exploratory testing with charters, heuristics, and session records; triggers include manual testing and exploratory testing.
Best use case
manual-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when you need to plan manual or exploratory testing with charters, heuristics, and session records; triggers include manual testing and exploratory testing.
Teams using manual-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/manual-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How manual-testing Compares
| Feature / Agent | manual-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when you need to plan manual or exploratory testing with charters, heuristics, and session records; triggers include manual testing and exploratory testing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Manual/Exploratory Testing **中文版：** 见对应中文技能。 ## When to Use - Need help with manual testing in a real project context. - Need an output that can be used directly for execution, review, or follow-up. ## Output Format Options Markdown by default. If you need Excel, CSV, JSON, Word, or other supported formats, append the format request at the end and check [output-formats.md](output-formats.md). ## How to Use 1. Open `prompts/manual-testing.md` and use it as the main prompt. 2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable. 3. If the input is incomplete, return a usable first version and mark missing information and assumptions. ## Reference Files - `prompts/manual-testing.md`: main prompt for this skill. - `output-formats.md`: optional output format instructions. - `references/`: supporting notes loaded only when needed. - `scripts/`: helper scripts or converters for this skill. ## Common Pitfalls - Do not use it with vague scope and no context. - Do not treat every area as equally important. - Do not skip assumptions and missing information. ## Best Practices - Start from the prompt file, then add only the context that matters. - Keep the output risk-driven and executable. - If the request is incomplete, return a usable first version and mark gaps.
Related Skills
sprint-testing-workflow
Use this skill when you need a sprint-based QA workflow from planning through review and retrospective; triggers include sprint testing workflow and sprint QA flow.
release-testing-workflow
Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and release readiness testing.
discover-testing
Use this skill when you need to quickly route a request to the best testing-type or testing-workflow skill.
daily-testing-workflow
Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
security-testing
Use this skill when you need to design security testing around OWASP risks, vulnerability scanning, and penetration scenarios; triggers include security testing and vulnerability testing.
performance-testing
Use this skill when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include performance testing and load testing.
mobile-testing
Use this skill when you need to design mobile test plans for iOS or Android covering functionality, compatibility, performance, network, and security; triggers include mobile testing and app testing.
functional-testing
Use this skill when you need to design functional test plans or cases for business flows, UI, data, and integrations; triggers include functional testing and functional test cases.
automation-testing
Use this skill when you need to design automation testing approaches using patterns like POM, data-driven testing, or BDD; triggers include automation testing and test automation strategy.
api-testing
Use this skill when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
ai-assisted-testing
Use this skill when you need AI-assisted testing workflows such as test data generation, root-cause analysis, and prioritization; triggers include AI-assisted testing and AI for QA.
accessibility-testing
Use this skill when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.