Qa Gate
v1.1.0Final quality validation gate for any artifact before human review. Run this skill on documents, skills, PRDs, blog posts, or code artifacts to validate fact...
⭐ 0· 145·1 current·1 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 instructions: the SKILL.md defines a read-only quality gate for artifacts. It does not request unrelated binaries, credentials, or installs.
Instruction Scope
Instructions are focused on inspection and producing a pass/fail report. They explicitly state the skill is read-only and should not modify artifacts. Two points to note: (1) the gate expects the agent to 'read the entire file' — this requires the agent to have access to the artifact content or workspace; (2) verification of factual claims implies searching external sources (web access) although no network policy is declared. Both are coherent with the purpose but are operational considerations.
Install Mechanism
No install spec and no code files — instruction-only skill. Lowest installation risk; nothing is written to disk by an installer.
Credentials
The skill declares no required env vars, credentials, or config paths. The lack of credential requests is appropriate for a read-only QA gate.
Persistence & Privilege
The skill is not marked always:true and does not request persistent privileges. It does instruct the agent to write reports to a relative path (qa-gate/YYYY-MM-DD-<artifact-slug>.md) — this is reasonable for its purpose but means the agent needs write access to the workspace/evidence directory.
Assessment
This skill is instruction-only and appears coherent for a final QA pass. Before installing/using it: (1) Confirm the agent will be given only the artifact content you intend it to read — do not pass files containing secrets or private data. (2) Be aware the instructions expect the agent to verify factual claims, which likely requires web/network access; if you want to restrict outbound access, you should enforce that separately. (3) The skill writes a report file to a relative workspace path; ensure that the workspace location is acceptable and that generated reports will not leak sensitive content. (4) If you need stronger controls, consider adding explicit constraints to SKILL.md (e.g., 'do not access the network' or 'mask any secrets before ingestion').Like a lobster shell, security has layers — review code before you run it.
latestvk979vfswkk4z8nvrjn5cmxqygx83xpq0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.