spellbook-security-auditor-delivery-review

Combines role output, risk review, and validation evidence into an operator-ready handoff.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security audit work often ends with scattered findings, unverified claims, and no clear next step. This Skill structures the final delivery stage of a security audit so every handoff includes the result, supporting evidence, known risks, and one executable next action. ## Core Features & Use Cases - Structured Handoff Format: Enforces a fixed output contract of result first, evidence second, risk third, and next action last. - Delivery-Risk Review: Runs a role-specific risk review before delivery and resolves or escalates blockers. - Use Case: After completing a security audit of a web application, use this workflow to assemble the findings, attach validation commands and assumptions, flag unresolved risks, and hand the operator a single actionable next step. ## Quick Start Ask the agent to run the delivery review workflow for the current security audit findings and produce the final handoff with evidence, risks, and next action.

Frequently Asked Questions about spellbook-security-auditor-delivery-review

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

FAQPage Schema
How do I structure a security audit handoff for operators?▼

Lead with the recommendation or completed artifact, then attach evidence and known assumptions, run a delivery-risk review, and end with one executable next action. This workflow enforces that exact ordering as its output contract.

What should a security audit delivery review include?▼

A delivery review should include the final result, supporting validation evidence, a risk assessment with known assumptions, and a single next action. Blockers must be resolved or explicitly handed off before delivery.

When should I use a delivery review workflow instead of a chat summary?▼

Use it when a concrete artifact, evidence gate, or formal handoff is required, such as completing a security audit. It is not intended for generic chat responses or exploratory discussion.

Which AI platforms support this delivery review workflow?▼

The workflow is documented for use in Claude Code, Codex, Gemini, Hermes, and OpenClaw. It is a prompt-based procedure, so it runs on any agent platform that loads skill instructions.

What are the limitations of a prompt-based delivery review?▼

It provides structure and checklists but does not execute validation commands itself. The operator or agent must still run the actual verification steps and record results in the task documentation.