spellbook-security-auditor-quality-gate

Reviews security auditor artifacts for evidence, acceptance criteria, and delivery readiness.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill spellbook-security-auditor-quality-gate-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spellbook-security-auditor-quality-gate
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/spellbook-security-auditor/skills/pack-maturity/quality-gate
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill spellbook-security-auditor-quality-gate-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security audit deliverables often ship without verified evidence, clear acceptance criteria, or a defined owner handoff, leading to unreliable findings and rework. This Skill applies a structured quality gate that checks every artifact before delivery. ## Core Features & Use Cases - Evidence Verification: Confirms each major claim in the artifact has supporting evidence or an explicit assumption. - Acceptance Criteria Checks: Validates that the artifact matches the original request and that a first-use demo produces a useful result. - Ranked Blocker Reporting: Returns blockers and safe fixes in a fixed output contract: result first, evidence second, risk third, next action last. - Use Case: Before handing off a security audit report, run the quality gate to flag missing tests, unsourced claims, or absent owner handoff, then deliver a ranked list of fixes. ## Quick Start Ask the agent to run the quality gate review on the current security audit artifact and return ranked blockers with evidence and next actions.

Frequently Asked Questions about spellbook-security-auditor-quality-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I quality-check a security audit report before delivery?▼

Run the quality gate workflow on the artifact. It inspects whether the report matches the request, verifies each major claim has evidence or an explicit assumption, and returns ranked blockers with safe fixes.

What does the quality gate check in an artifact?▼

It checks four areas: artifact-to-request match, evidence backing for major claims, usefulness of the first-use demo output, and presence of tests, sources, and owner handoff. Findings are returned as ranked blockers.

When should I not use the quality gate workflow?▼

Do not use it for generic chat responses or open-ended discussion. It is designed only for cases where a concrete artifact, evidence gate, or formal handoff is required in the security auditor pack.

What output format does the quality gate produce?▼

It follows a fixed output contract: result first, evidence second, risk third, and next action last. This keeps reviews consistent and makes blockers easy to act on.

Can the quality gate be used outside the security auditor pack?▼

The workflow is written for the security auditor pack context, but its review steps—evidence checks, acceptance criteria, and ranked blockers—can be applied to any artifact requiring a pre-delivery gate.