qa

Simulate real user interactions to manually test web, API, and bot interfaces.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/EllevatedAI/MeMyselfAndI --skill qa-ellevatedai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/EllevatedAI/MeMyselfAndI/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/EllevatedAI/MeMyselfAndI --skill qa-ellevatedai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams validate product behavior by simulating real user QA, focusing on observed symptoms rather than code-level issues and ensuring issues are caught from a user perspective.

Core Features & Use Cases

  • Activates via the /qa command to start a manual test session.
  • Guides testers to observe and describe user-facing symptoms, not root causes.
  • Documents test scenarios, captures evidence, and communicates findings to the team.
  • Useful for onboarding new testers, verifying new features, and reproducing reported bugs across web, API, and chat bots.

Quick Start

Invoke QA with /qa {what to test} to start a manual test session in the running product.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform manual QA testing to reproduce a reported bug?▼

Manual QA testing reproduces bugs by simulating real user interactions to observe and record user-facing symptoms. Start a session using the /qa command, specifying the target feature to test across web, API, or bot interfaces.

What is exploratory testing for verifying user experience without reading source code?▼

Exploratory testing validates user experience by observing product behavior and capturing evidence of symptoms rather than inspecting source code. It focuses on real user interactions to catch issues from a user perspective.

Can I use manual test scenarios to verify new features across web, API, and chat bots?▼

Yes, manual test scenarios verify new features across web, API, and chat bot interfaces. The testing process documents scenarios, captures evidence, and communicates findings to the team without requiring code-level inspection.

How do I start a manual test session for onboarding new testers?▼

Start a manual test session by invoking the /qa command followed by what to test. This activates the tester role, guiding new testers to observe and describe user-facing symptoms while documenting evidence in the running product.

Does manual QA testing focus on finding root causes or documenting user-facing symptoms?▼

Manual QA testing focuses strictly on documenting user-facing symptoms and capturing evidence rather than finding root causes. It simulates real user interactions to observe and communicate product behavior issues to the team.