Qa Expert
CheckedThe Qa Expert skill analyzes text for questions and answers, streamlining knowledge extraction and verification processes for improved accuracy.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add daymade/claude-code-skills --skill qa-expert -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
daymade
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned daymade/claude-code-skills at 1327636852.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1327636852
- Manifest
- qa-expert/SKILL.md
- Scanned
- 9 files, 2,792 lines
About this skill
What it does
The QA Expert skill establishes structured quality assurance (QA) testing processes for software projects, drawing upon Google Testing Standards and OWASP security best practices. It enables AI agents to initialize QA infrastructure, write standardized test cases using the AAA pattern, track test execution, generate reports, and implement security testing. The skill aims to improve accuracy and efficiency in software quality verification.
When to use it
- Setting up QA infrastructure for new or existing projects.
- Writing standardized test cases adhering to the AAA (Arrange-Act-Assert) pattern.
- Executing comprehensive test plans and tracking progress.
- Implementing security testing based on OWASP Top 10 principles.
- Preparing QA documentation for team handoffs.
Key capabilities
- QA Project Initialization: Creates a complete QA infrastructure including directory structure, tracking CSVs, documentation templates, and a master prompt for autonomous execution.
- Test Case Writing: Facilitates the creation of standardized test cases following the AAA pattern, with priority assignment (P0-P4) and consideration of edge cases.
- Test Execution & Tracking: Provides guidance on manual and autonomous test execution, emphasizing the importance of a "Ground Truth Principle" to maintain accurate test specifications.
Example prompts
- “Initialize QA infrastructure for my project called ‘Project Phoenix’ in the directory
/projects/phoenix_qa.” - “Write a standardized test case following the AAA pattern for user login functionality, assigning it priority P2.”
- "Show me the template for writing a test case."
Tips & gotchas
- The "Ground Truth Principle" is critical: always refer to test case documents as the authoritative source of truth and avoid batch updates to tracking CSVs.
- For autonomous execution, utilize the master prompt provided (references/master_qa_prompt.md) for a significant speedup.
- Test cases should follow a specific format: TC-[CATEGORY]-[NUMBER] (e.g., TC-CLI-001).