QA as a system, not a checklist: the skill I uploaded to skills.sh
I just uploaded a Senior QA Engineer skill and the skills.sh system has already indexed it and is showing it publicly. It's not a resume or a role description. It's QA knowledge structured as a reusable skill.
The idea is simple: QA as a system, not a checklist. Practices that are clear, reproducible, and designed for real workflows — not a list of generic steps someone copies and pastes without understanding them, but codified judgment for an agent to apply with the same rigor a senior QA with years of training would apply.
The fact that an external platform picked it up and published it without me having to ask for anything is a good sign this approach makes sense. Skills.sh indexes skills by their real value, not because someone promotes them — and this one is already circulating.
This skill is part of the same family that later got published here as a project: QA Skills, a pack of 11 installable skills covering the full cycle — story verification, test case design with ISTQB techniques, execution, defects, CI/CD, continuous improvement. What I uploaded to skills.sh was the starting point of that bigger idea.
Tip
Codifying a senior QA's judgment as a skill isn't "replacing" QA. It's capturing their method in a form an agent can run — the same as documenting any critical process, except now the documentation is executable.
What interests me about this in the long run isn't that an agent can run a skill of mine. It's that QA knowledge — the kind that normally lives only in the heads of experienced people — can become something transferable, versioned, installable in a new project with a single command. That doesn't compete with human QA. It multiplies it.
I originally published this on LinkedIn