nacl-tl-qa

Automate end-to-end QA testing of UC tasks with MCP Playwright.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-tl-qa
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-qa
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end QA testing of UC tasks requires acting as a real user to validate behavior across frontend and backend, capture evidence, and ensure acceptance criteria are met.

Core Features & Use Cases

  • Real-user oriented end-to-end testing using MCP Playwright to navigate pages, fill forms, click controls, and verify outcomes.
  • Acceptance criteria-driven testing: reads uc task acceptance.md and produces a QA report with evidence and status updates.
  • Evidence generation and tracking: automatically takes screenshots at key steps and updates qa artifacts like qa-report.md and tracking files.
  • Use Case coverage: supports verifying UI flows, data handling, and integration points across the full software lifecycle.

Quick Start

Invoke the QA flow by running /nacl-tl-qa UC### to perform end-to-end QA testing for the specified UC with MCP Playwright.

Frequently Asked Questions about nacl-tl-qa

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

FAQPage Schema
How do I automate end-to-end QA testing for UC tasks?

End-to-end QA testing for UC tasks is automated by acting as a real user with MCP Playwright. The skill reads acceptance criteria from task directories, navigates frontend and backend flows, and outputs a qa-report.md with status updates.

Can I generate evidence and screenshots automatically during Playwright e2e testing?

Yes, e2e testing with MCP Playwright automatically captures evidence by taking screenshots at key workflow steps. It updates tracking files and qa-report.md to ensure acceptance criteria verification is fully documented.

Does acceptance criteria-driven testing work with existing UC task directories?

Acceptance criteria-driven testing reads uc task acceptance.md files directly from your existing directories. It validates UI flows, data handling, and integration points to verify if the specified acceptance criteria are met.

What do I need to run automated QA testing for UC functionality across frontend and backend?

Automated QA testing for UC functionality requires MCP Playwright tools to simulate real user interactions. It reads acceptance.md from UC task directories and produces a qa-report.md with tracking file updates.

How do I verify acceptance criteria and update QA artifacts for UC tasks?

To verify acceptance criteria and update QA artifacts, invoke the QA flow by running the command targeting a specific UC. MCP Playwright executes real user actions, validates outcomes, and updates qa-report.md and tracking files automatically.