qa tester
v1.0.0Strict QA and test engineering skill for fullstack repositories. Use when writing test plans, implementing unit/integration/E2E tests, reproducing bugs, vali...
⭐ 0· 87·1 current·1 all-time
byBayu Dwi Satriyo@bayudsatriyo
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (QA/test engineering) align with the content: SKILL.md and the three reference documents focus on test strategy, patterns, E2E reliability, and release gates. There are no unrelated required binaries, credentials, or config paths that would be unexpected for a QA helper.
Instruction Scope
Runtime instructions are scoped to test planning, authoring, and validation. The skill explicitly forbids executing tests without user approval and requires reading only the included reference files before authoring. It expects to inspect repository code when implementing tests (reasonable and expected) and does not instruct the agent to read or exfiltrate unrelated system files or secrets.
Install Mechanism
No install spec and no code files beyond documentation; nothing will be downloaded or written to disk by the skill itself. This is the lowest-risk install footprint.
Credentials
The skill requests no environment variables, credentials, or external config paths. The absence of secrets or external service tokens is appropriate for a purely procedural QA skill.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent presence or to modify other skills or agent-wide settings. It does instruct the agent how to add tests to the repository when asked, which is a normal capability for a QA authoring skill.
Assessment
This skill appears coherent and low-risk: it is documentation/instruction-only, asks for no credentials, and explicitly avoids running tests without approval. Before installing or enabling it for autonomous agents, confirm (1) your agent's permissions — whether it can write to the repository or run commands automatically — and restrict those if you don't want file modifications or test execution without human approval; (2) that any test files the agent would add are reviewed before being run in CI; and (3) you trust the agent's environment (sandboxing) when you later instruct it to run tests, capture logs, or upload artifacts. If you want extra assurance, run the skill in a read-only or isolated workspace first and review its suggested changes prior to applying them.Like a lobster shell, security has layers — review code before you run it.
latestvk971gk1fbdt89wxyx82y60rxwn83qra1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.