spellbook-security-auditor-scope-contract

Converts ambiguous requests into bounded role contracts with outcomes, non-goals, and validation criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or ambiguous task requests lead to scope creep, unclear deliverables, and unverifiable results. This Skill turns an ambiguous request into a bounded role contract that defines outcomes, non-goals, inputs, outputs, risks, and validation before work begins. ## Core Features & Use Cases - Scope Definition: Restates the user outcome in one sentence and lists role-owned scope plus explicit non-goals. - Input and Artifact Contract: Names required and unavailable inputs, defines the deliverable artifact, and specifies its validation method. - Decision Gate: Returns a stop, go, iterate, or escalate decision with a fixed output order of result, evidence, risk, and next action. - Use Case: When operating the security auditor pack and a concrete evidence gate or handoff is required, load this workflow to bound the audit task before executing any checks. ## Quick Start Load the scope-contract skill and ask it to turn my current security audit request into a bounded contract with outcomes, non-goals, inputs, and a go or stop decision.

Frequently Asked Questions about spellbook-security-auditor-scope-contract

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

FAQPage Schema
How do I turn an ambiguous request into a scoped task contract?▼

Restate the user outcome in one sentence, list role-owned scope and explicit non-goals, name required and unavailable inputs, then define the artifact and its validation method. Finish with a stop, go, iterate, or escalate decision.

What should a scope contract include before starting a security audit?▼

A scope contract should include the one-sentence outcome, owned scope, explicit non-goals, required and missing inputs, the deliverable artifact, and the validation method. This prevents scope creep and unverifiable results.

When should I not use a scope contract workflow?▼

Do not use it for generic chat responses or casual questions. It is designed for situations requiring a concrete artifact, evidence gate, or formal handoff within the security auditor pack.

What output format does the scope contract workflow produce?▼

The output follows a fixed order: result first, evidence second, risk third, and next action last. It ends with a stop, go, iterate, or escalate decision to guide the next step.

Can this workflow be used in Claude Code, Codex, or Gemini?▼

Yes, the workflow is designed to be reusable across Claude Code, Codex, Gemini, Hermes, and OpenClaw. It provides the same role capability as a portable skill document rather than a one-off chat prompt.