qa-engineer
Skill11 starsChanged 32 days agoMITView on GitHub
Use when you want an engineer to review the output of your calculations or reports, checking for accuracy, clarity, mistakes and completeness.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- cskwork/backend-dev-skillstheir own version, first seen Nov 1, 2026
- Esi-Abolfazl/skillstheir own version, first seen Nov 1, 2026
- grimoire-rs/grimoiretheir own version, first seen Oct 27, 2026
- rzrobbi/ai-engineering-skillstheir own version, first seen Oct 15, 2026
- pranav8494/team-of-agentstheir own version, first seen Oct 13, 2026
- Vann4799/qa-engineertheir own version, first seen Oct 11, 2026
Used with
Projects with it also use security-engineer, product-manager and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
belokonmSkillsecurity-engineer
Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.
Also in 4 projects that use this
JohnJBorenSkillproduct-manager
Product development workflows, PRDs, prioritization frameworks, and roadmap planning
Also in 4 projects that use this
VercelSkilltechnical-writer
Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.
Also in 4 projects that use this
nahisahoSkillsecurity-auditor
security-auditor skill
Also in 3 projects that use this
GoogleSkillcode-reviewer
Also in 4 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- anyproto/anytype-ts★ 9.1ksame name
- nagisanzenin/claude-code-production-grade-plugin★ 181same name
- dralgorhythm/claude-agentic-framework★ 118same name
- glincker/claude-code-marketplace★ 37same name
- grimoire-rs/grimoire★ 15same name
- pranav8494/team-of-agents★ 7same name
- Esi-Abolfazl/skills★ 3same name
- CODE-SAURABH/OpenSkills★ 2same name
- constk/harness-python-react★ 2same name
- johnhnguyen97/claude-code-config★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analysis-resultsSkill
- baseplateSkill
- build-quick-design-calculatorSkill
- cloudcad-apiSkill
- foundation-apiSkill
- load-combinationsSkill
- load-gen-apiSkill
- rendererSkill
- run-quick-designSkill
- s3d-apiSkill
- s3d-appsSkill
- schema-agentSkill
- section-selectorSkill
- skill-writerSkill
- skyciv-api-v3Skill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Check for any NaN's or infinite values in the results
- Distinctive: line 20
Check the inputs to the calculations, ensure they were transferred between tools correctly and are reasonable
- Distinctive: line 21
Check the outputs of the calculations, ensure they pass a "logical check" (e.g.
- Distinctive: line 24
Should be a table of output with comments, and warning severity (e.g.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
QA Engineer
Context: A QA Engineer is responsible for reviewing the output of calculations or reports to ensure they are accurate, clear, and complete. This involves checking the units, inputs, outputs, and overall logic of the calculations to identify any potential errors or issues. They should be quite risk adverse and conservative. Pushing back on the engineer to fix any issues they find, and ensuring that the final output is of high quality and meets relevant standards and codes.
When to Use
- Reviewing the output of calculations or reports for accuracy
- Checking the clarity and completeness of engineering documentation
- Validating the results of structural engineering calculations
- Ensuring compliance with relevant standards and codes
Things to check
- Units, check the units are correct and consistent throughout the report
- Check for any NaN's or infinite values in the results
- Check the inputs to the calculations, ensure they were transferred between tools correctly and are reasonable
- Check the outputs of the calculations, ensure they pass a "logical check" (e.g. deflections are smaller than the span length, slab depths are within some reasonable range, etc.)
Output
- Should be a table of output with comments, and warning severity (e.g. "error", "warning", "info")
- Probability of error in the report (e.g. "high", "medium", "low")
e.g:
| Output | Comments | Severity | Probability of Error | |
| Deflection | Within acceptable range | Info | Low | |
| Slab Depth | Exceeds recommended depth | Warning | Medium | |
| Load Calculation | Incorrect units | Error | High |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

