gatekeeper-worker

Validate mission gate claims against evidence and workflow rules.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/LudwigAJ/swell --skill gatekeeper-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gatekeeper-worker
Source: https://github.com/LudwigAJ/swell/tree/main/.factory/skills/gatekeeper-worker
Command: npx skills add https://github.com/LudwigAJ/swell --skill gatekeeper-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gatekeeper Worker prevents false completion claims from slipping through mission control by forcing every gate decision to match the real validation state, evidence, and approved workflow rules.

Core Features & Use Cases

  • Tier Gate Enforcement: Verifies that lower-tier work is green before allowing higher-tier progression.
  • Evidence Cross-Checking: Compares handoff claims against mission sources, validation identifiers, and actual command output.
  • Handoff Hygiene Review: Checks machine-readable progress blocks for required fields, witness and ignore cleanup, and consistent status reporting.
  • Use Case: A reviewer receives a task closure report and uses this Skill to reject unsupported completion claims, missing validation IDs, or flaky proof before the mission state is updated.

Quick Start

Use the gatekeeper-worker skill to review the latest mission handoff against the required validation files and only approve it if every claimed gate, evidence field, and status update is fully supported.

Frequently Asked Questions about gatekeeper-worker

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

FAQPage Schema
How do I validate mission gate claims and block unsupported completion handoffs?

Validating mission gate claims requires cross-checking handoff evidence against AGENTS.md and validation sources, then rejecting mismatched, flaky, or unsupported completion claims before updating mission state.

What is tiered gate enforcement and how does it control workflow progression?

Tiered gate enforcement verifies that lower-tier work is fully validated and green before allowing any higher-tier workflow progression, ensuring strict compliance with mission-controlled review stages.

How do I review progress handoff hygiene for missing evidence fields?

Reviewing progress handoff hygiene involves checking machine-readable progress blocks for required evidence fields, verifying witness and ignore cleanup, and ensuring consistent status reporting across all mission updates.

Can I use automated gatekeeping to reject flaky validation proof in mission control?

Automated gatekeeping rejects flaky validation proof by requiring machine-readable evidence fields and cross-checking actual command output against claimed validation identifiers before approving any task closure report.

What are the limitations of manual progress checkbacks compared to automated gatekeeping?

Manual progress checkbacks lack systematic cross-referencing against AGENTS.md and validation sources, whereas automated gatekeeping strictly enforces evidence matching and blocks unsupported completion claims at scale.