How do I install the QA Validation skill?

Run npx skillmds@latest add majiayu000/qa-validation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is QA Validation safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Validation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is QA Validation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published QA Validation?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA Validation by majiayu000 — Agent Skill

Name: QA Validation
Rating: 4.2 (5 reviews)
Author: majiayu000

QA Validation

Validate implementation against test cases and acceptance criteria. Use when checking if code works correctly, validating against user-provided test cases, or verifying acceptance criteria are met. Gets test cases from user input or previous workflow stages.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

QA Validation Skill

Validate implementation against test cases and acceptance criteria to ensure code works correctly.

When to Use

This skill activates when:

User provides test cases to validate against
Checking if implementation meets acceptance criteria
Verifying all scenarios work correctly
After unit tests are generated to validate coverage
User mentions "validate", "verify", "check", "QA"

Validation Categories

Functional Tests

Core functionality works as expected
Input/output contracts are honored
Business logic is correct
API responses match expected format

Error Handling

Errors are caught and handled gracefully
Error messages are informative
Recovery mechanisms work
Edge cases don't crash the application

Edge Cases

Boundary conditions are handled
Empty/null inputs don't crash
Large inputs are processed correctly
Concurrent operations work safely

Acceptance Criteria

User requirements are satisfied
Feature behaves as specified
Integration points work correctly
Performance is acceptable

Validation Process

Gather Test Cases:
- From user-provided test cases in the request
- From previous workflow stages (unit_test output)
- From acceptance criteria in task description
For Each Test Case, Validate:
- Functional requirements are met
- Error handling works correctly
- Edge cases are handled
- Performance is acceptable
Report Results:
- Pass/fail status for each test case
- Issues found with specific details
- Recommendations for fixes
- Overall pass rate

Output Format

## Validation Results

**Status**: PASSED / FAILED
**Pass Rate**: X%

### Scenarios Validated
1. [Scenario Name] - PASSED/FAILED
   - Details...

### Issues Found
1. [Issue Description]
   - Location: [file:line]
   - Severity: Critical/Warning/Info
   - Recommendation: [fix suggestion]

### Recommendations
1. [Actionable recommendation]

Best Practices

Be thorough in validation
Document all findings clearly
Prioritize critical issues
Suggest actionable fixes
Consider user experience
Test both positive and negative scenarios

---name: qa-validationdescription: Validate implementation against test cases and acceptance criteria. Use when checking if code works correctly, validating against user-provided test cases, or verifying acceptance criteria are met. Gets test cases from user input or previous workflow stages.--- # QA Validation Skill Validate implementation against test cases and acceptance criteria to ensure code works correctly. ## When to Use This skill activates when: - User provides test cases to validate against - Checking if implementation meets acceptance criteria - Verifying all scenarios work correctly - After unit tests are generated to validate coverage - User mentions "validate", "verify", "check", "QA" ## Validation Categories ### Functional Tests - Core functionality works as expected - Input/output contracts are honored - Business logic is correct - API responses match expected format ### Error Handling - Errors are caught and handled gracefully - Error messages are informative - Recovery mechanisms work - Edge cases don't crash the application ### Edge Cases - Boundary conditions are handled - Empty/null inputs don't crash - Large inputs are processed correctly - Concurrent operations work safely ### Acceptance Criteria - User requirements are satisfied - Feature behaves as specified - Integration points work correctly - Performance is acceptable ## Validation Process 1. **Gather Test Cases**: - From user-provided test cases in the request - From previous workflow stages (unit_test output) - From acceptance criteria in task description 2. **For Each Test Case, Validate**: - Functional requirements are met - Error handling works correctly - Edge cases are handled - Performance is acceptable 3. **Report Results**: - Pass/fail status for each test case - Issues found with specific details - Recommendations for fixes - Overall pass rate ## Output Format ``` ## Validation Results **Status**: PASSED / FAILED **Pass Rate**: X% ### Scenarios Validated 1. [Scenario Name] - PASSED/FAILED - Details... ### Issues Found 1. [Issue Description] - Location: [file:line] - Severity: Critical/Warning/Info - Recommendation: [fix suggestion] ### Recommendations 1. [Actionable recommendation] ``` ## Best Practices - Be thorough in validation - Document all findings clearly - Prioritize critical issues - Suggest actionable fixes - Consider user experience - Test both positive and negative scenarios

Frequently asked questions