qa-test-automation-engineer
Skill3 starsChanged 35 days agoApache-2.0View on GitHub
Read acceptance criteria, architecture, critical paths, and current test coverage. Use for qa test automation engineer tasks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- suhanr/next-gen-claude-skillstheir own version, first seen Aug 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- suhanr/next-gen-claude-skills★ 2same name
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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- admin-hr-legal-officerSkill
- ai-voice-audio-engineerSkill
- automation-ops-engineerSkill
- b2b-sales-hunterSkill
- brand-identity-engineerSkill
- business-analyst-discoverySkill
- client-success-guardianSkill
- competitor-spy-analystSkill
- context-guardianSkill
- creative-directorSkill
- creative-frontend-designerSkill
- data-harvesterSkill
- deal-closerSkill
- delivery-directorSkill
- distributed-systems-architectSkill
- executive-accountantSkill
- frontend-ux-auditorSkill
- fullstack-mvp-engineerSkill
- funnel-cro-auditorSkill
- graphic-design-producerSkill
- growth-director-orchestratorSkill
- legacy-code-rescue-specialistSkill
- machine-control-operatorSkill
- mcp-integration-builderSkill
- network-infra-engineerSkill
- paid-media-buyerSkill
- reverse-engineering-analystSkill
- rfp-proposal-engineerSkill
- security-operations-guardianSkill
- seo-growth-engineerSkill
- short-form-paid-boosterSkill
- skill-forge-recruiterSkill
- skill-improvement-engineerSkill
- skill-performance-auditorSkill
- studio-directorSkill
- tech-stack-architectSkill
- toolbox-integration-stewardSkill
- trend-hunter-ideatorSkill
- ultra-light-optimizerSkill
- video-assembly-editorSkill
- video-script-architectSkill
- viral-hook-architectSkill
- visual-qa-reviewerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this role for qa test automation engineer work.
- Very specific: line 14
Read the workspace constitution and the five files in brain/ before execution.
- Distinctive: line 18
Read acceptance criteria, architecture, critical paths, and current test coverage.
- Distinctive: line 21
Run the suite and record exact results, unresolved failures, and scope limitations.
- Distinctive: line 29
Update completed work, challenges, ideas, and backlog with concise records.
- Distinctive: line 43
Read the English playbook and the execution guide before owning a software workflow step.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Qa Test Automation Engineer
When to use
Use this role for qa test automation engineer work. Match the task scope before activation; do not assume the host has external tools or account permissions.
Brain and preflight
Read the workspace constitution and the five files in brain/ before execution. Confirm the requested output language, input facts, authority, dependencies, and acceptance criteria.
Procedure
- Read acceptance criteria, architecture, critical paths, and current test coverage.
- Choose component, integration, end-to-end, or performance tests based on real risks.
- Implement meaningful fixtures covering successful and failing behavior.
- Run the suite and record exact results, unresolved failures, and scope limitations.
Deliverable and verification
Deliver the concrete artifact or findings, the evidence used, checks performed, and remaining limitations. Use Arabic or English as requested. Identify missing tools or facts explicitly; do not fill gaps with invented results.
Closure
Update completed work, challenges, ideas, and backlog with concise records. Keep credentials and private customer records out of shared memory.
Detailed procedures and specialist references
Read the full Arabic playbook for role boundaries, step-by-step procedures, acceptance conditions, and handoff requirements. Read the specialist architecture when selecting tools and project inputs. The English entry point and shared constitution govern public task execution. Source-specific external documents are project inputs, not bundled private records.
Included executable tools
- delivery-evidence: Verify evidence bookkeeping, revision and hashes; not evidence truth.
See the tool catalog for commands, inputs, side effects and exit behavior.
English software workflow contract
Read the English playbook and the execution guide before owning a software workflow step.
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.

