gate-skill

Evaluates implementation, validation, and policy evidence to produce a structured gate decision.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill gate-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/gate-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill gate-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted re-execution by turning already-collected evidence into a rigorous, policy-aligned gate decision for whether the harness can advance in the current judging phase.

Core Features & Use Cases

  • Gate verdict from orthogonal evidence: Evaluates implementation/validation/policy evidence to derive a structured verdict and confidence.
  • Scoped decision without refresh: Produces an allowed-next-route decision while explicitly avoiding actions like recovery, merge, close, or repo refresh.
  • Noise absorption for low-severity findings: Keeps P2/P3 low-severity items as residual risk unless they form cross-layer, systemic threat patterns.
  • Node-type aware strictness: Tightens or relaxes requirements based on worktrack contract node type (feature/refactor/research/bugfix/docs/config/test) with documented fallbacks.
  • Upstream-constraint routing enforcement: Blocks pure code-repair routing when upstream constraints or contract/boundary/governance dependencies are decisive.

Quick Start

Use gate-skill when your harness is in WorktrackScope.judging and you already have the current round evidence needed to decide whether to pass, soft-fail, hard-fail, or block within the scope.

Frequently Asked Questions about gate-skill

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

FAQPage Schema
How do I decide pass/fail gates from existing evidence without re-executing validation?

Gate adjudication evaluates existing implementation, validation, and policy evidence to produce a structured pass, soft-fail, hard-fail, or block decision. It enforces evidence-ready prerequisites and outputs per-dimension acceptance, confidence scoring, and an allowed-next routing decision.

What is gate adjudication in a worktrack judging phase?

Gate adjudication is the process of determining whether a harness can advance from the WorktrackScope.judging phase. It assesses orthogonal evidence to generate a routing decision while explicitly avoiding inappropriate state-refresh actions like recovery, merge, close, or repo refresh.

How does confidence scoring handle low-severity findings during policy compliance evaluation?

Confidence scoring absorbs noise from P2/P3 low-severity findings by treating them as residual risk. They are only escalated if they form cross-layer, systemic threat patterns, preventing unnecessary re-execution while maintaining policy compliance standards.

Can I adjust gate strictness based on different worktrack contract node types?

Gate strictness adjusts dynamically based on the worktrack contract node type, such as feature, refactor, research, bugfix, docs, config, or test. The evaluation tightens or relaxes requirements and applies documented fallbacks for each specific node type.

When should I block pure code-repair routing during evidence evaluation?

Pure code-repair routing is blocked when upstream constraints or contract, boundary, and governance dependencies are decisive. The gate adjudication process enforces this routing constraint to ensure systemic issues are addressed rather than applying isolated code fixes.