algorithm-engineer-quality-gate

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delivering algorithm engineering artifacts without a structured review leads to missing evidence, unverified claims, and unclear handoffs. This Skill provides a repeatable quality gate that checks artifacts against evidence, acceptance criteria, and install usefulness before delivery. ## Core Features & Use Cases - Evidence Verification: Confirms each major claim in an artifact has supporting evidence or an explicit assumption. - Acceptance & Demo Checks: Validates that the artifact matches the request and that a first-use demo produces 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 a model evaluation report in an algorithm engineering pack, run this gate to confirm every metric claim is backed by evidence and receive a prioritized list of blockers to resolve. ## Quick Start Ask the agent to run the quality gate on the current algorithm engineering artifact and return ranked blockers with evidence and next actions.

Frequently Asked Questions about algorithm-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 AI artifact?▼

Load the quality-gate skill and point it at the artifact to review. It inspects whether the artifact matches the request, verifies evidence for major claims, 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 each major claim, first-use demo usefulness, and missing tests, sources, or owner handoffs. Output follows a result, evidence, risk, next-action contract.

When should I not use a quality gate workflow?▼

Do not use it for generic chat responses or open-ended discussion. It is designed for concrete artifacts, evidence gates, or handoffs within the algorithm engineer pack where a deliverable must be verified.

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

Yes, the skill is a Markdown-based workflow that runs 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?▼

It produces a four-part output: result first, evidence second, risk third, and next action last. Blockers are ranked and paired with safe fixes so reviewers can act on them in priority order.