UX QA Gate
v1.0.0Self-review gate for UI/UX work before delivering to the user. Run automatically after building, modifying, or completing any user-facing feature, page, comp...
⭐ 1· 116·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions. The skill is instruction-only, requests no binaries, env vars, or installs, and everything it asks for (checking UI/UX heuristics, functional checks, state sweeps) is appropriate for a QA gate.
Instruction Scope
SKILL.md confines actions to reviewing the work, re-reading the original request, and using the bundled heuristics checklist file. It does not instruct the agent to read unrelated system files, call external endpoints, or exfiltrate data. Note: the gate assumes the agent can interact with the UI or project artifacts to perform checks (manual or automated), but it does not add any instructions that would expand privilege or access beyond that scope.
Install Mechanism
No install spec and no code files — lowest-risk model. Nothing will be written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. All required artifacts are bundled (heuristics checklist) or are the user's project/request context, which is appropriate for a QA gate.
Persistence & Privilege
always is false and model invocation is normal. The skill does not request persistent system presence or modify other skills or system-wide settings.
Assessment
This skill is coherent and low-risk: it is a textual QA checklist and asks for no credentials or installs. Before using it, confirm the agent already has the necessary access to your project or running app (build artifacts, staging site, or screenshots) so checks are meaningful. If you plan to run this gate in automation/CI, ensure the CI environment gives only the minimal required access (build artifacts, staging URL) and review any QA outputs before sharing externally, as the gate will re-read the original request and inspect the work you point it at. If you expect automated interaction with the UI, note the skill contains no automation tooling — you will need to provide or permit those tools separately.Like a lobster shell, security has layers — review code before you run it.
latestvk972txctjhw843jjff8w7b9mbn835rbw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.