ops-engineer-quality-gate

Reviews role artifacts for evidence, acceptance criteria, and handoff readiness before delivery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delivering operations artifacts without a structured review leads to missing evidence, unverified claims, and unclear handoffs. This Skill provides a repeatable quality gate that checks every artifact before it is delivered. ## Core Features & Use Cases - Evidence Verification: Confirms each major claim in an 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 would produce a useful result. - Ranked Blocker Reporting: Flags missing tests, sources, or owner handoffs and returns ranked blockers with safe fixes. - Use Case: Before handing off an operations runbook or incident report, run the quality gate to confirm all claims are evidenced, risks are documented, and the next action is clearly stated. ## Quick Start Ask the agent to run the quality gate review on the current operations artifact and return ranked blockers with evidence and next actions.

Frequently Asked Questions about ops-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 operations artifact?▼

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

What does a quality gate check before delivery?▼

It checks artifact-to-request alignment, evidence or explicit assumptions for major claims, first-use demo usefulness, and missing tests, sources, or owner handoffs. Output is ordered as result, evidence, risk, then next action.

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 ops-engineer pack.

Can the quality gate skill work in Claude Code, Codex, or Gemini?▼

Yes, the skill is a Markdown-based workflow that can be loaded in Claude Code, Codex, Gemini, Hermes, or OpenClaw. It reuses the same procedure and output contract across these agent platforms.

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 ranked and paired with safe fixes so reviewers can act on them directly.