infra-engineer-quality-gate

Reviews infrastructure 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 infra-engineer-quality-gate-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: infra-engineer-quality-gate
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/infra-engineer/skills/pack-maturity/quality-gate
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill infra-engineer-quality-gate-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Infrastructure engineering deliverables often ship without verified evidence, clear acceptance criteria, or a defined owner handoff, leading to unverifiable claims and failed reviews. This Skill applies a structured quality gate that checks every artifact before delivery. ## Core Features & Use Cases - Evidence Verification: Confirms each major claim in an artifact is backed by 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 Reports: Flags missing tests, sources, or owner handoffs and returns ranked blockers with safe fixes. - Use Case: Before handing off an infrastructure change plan, run the quality gate to confirm every claim has evidence, the demo path works, and the output follows the result-evidence-risk-next-action contract. ## Quick Start Ask the agent to run the quality gate review on the current infrastructure artifact and return ranked blockers with safe fixes.

Frequently Asked Questions about infra-engineer-quality-gate

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

FAQPage Schema
How do I run a quality gate review on an infrastructure artifact?▼

Load the quality-gate skill and provide the artifact to review. The workflow inspects whether the artifact matches the request, verifies evidence for each claim, checks demo usefulness, and returns ranked blockers with safe fixes.

What does the quality gate check before delivery?▼

It checks four areas: whether the artifact matches the request, whether each major claim has evidence or an explicit assumption, whether the first-use demo produces a useful artifact, and whether tests, sources, or owner handoff are missing.

When should I not use a 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 infrastructure engineer pack.

What output format does the quality gate produce?▼

The output contract is fixed: result first, evidence second, risk third, and next action last. Blockers are returned ranked by severity along with safe fixes for each issue found.

Can the quality gate be used in Claude Code, Codex, or OpenClaw?▼

Yes. The skill is packaged as a reusable role capability that works across Claude Code, Codex, Gemini, Hermes, and OpenClaw, so the same quality gate process applies regardless of the agent platform.