gate

Evaluate CAPPY investigation phase metrics against quality thresholds and return pass/fail status.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate
Source: https://github.com/theLightArchitect/cappy-toolkit/tree/main/skills/gate
Command: npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CAPPY’s investigations can progress with insufficient confidence or incomplete evidence, leading to unreliable conclusions; the gate skill enforces explicit quality thresholds at each phase to halt advancement until standards are met.

Core Features & Use Cases

  • Phase‑specific thresholds: confidence ≥ 70 %, completeness ≥ 80 %, coherence ≥ 85 %, solution quality ≥ 85 %, verification ≥ 90 %.
  • Automated hook triggering: evaluates metrics, compares to thresholds, and blocks or allows phase transition.
  • Recovery guidance: provides prioritized actions when a gate fails, such as requesting additional evidence or escalation.
  • Use case: During a TAC investigation, the skill ensures that Phase 3 evidence extraction meets the 80 % completeness requirement before moving to hypothesis design.

Quick Start

Run the /gate skill to evaluate the current phase’s quality gate and receive immediate pass/fail feedback with suggested recovery steps.

Frequently Asked Questions about gate

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

FAQPage Schema
How do I enforce quality thresholds for investigation phases to prevent unreliable conclusions?

To enforce quality thresholds for investigation phases, you apply explicit confidence, completeness, and coherence metrics checks that block phase advancement until standards are met. This prevents unreliable conclusions by halting progress when evidence is insufficient.

What metrics are evaluated during an investigation quality gate check?

An investigation quality gate evaluates confidence, completeness, coherence, solution quality, and verification metrics. It compares these extracted metrics against defined thresholds, such as requiring 80% completeness and 70% confidence, to return a pass or fail status.

How do I stop an investigation from advancing to hypothesis design with incomplete evidence?

To stop an investigation from advancing with incomplete evidence, you apply phase-specific quality gates. The gate enforces an 80% completeness requirement during evidence extraction, blocking the transition to hypothesis design until the threshold is met.

What happens when a quality gate fails during an investigation phase?

When a quality gate fails during an investigation phase, it triggers corresponding hooks to block advancement and returns a fail status with prioritized recovery options. This recovery guidance suggests actions like requesting additional evidence or escalating the issue.

Can I use automated hooks to block phase transitions in a CAPPY investigation?

Yes, you can use automated hook triggering to block phase transitions in a CAPPY investigation. The quality gate evaluates metrics, compares them to defined thresholds, and automatically triggers hooks to block or allow the phase transition.

Do I need defined threshold values to apply quality gates to my investigation workflow?

Yes, you need defined threshold values to apply quality gates to your investigation workflow. The gate enforces explicit thresholds, such as 85% for coherence and 90% for verification, comparing extracted metrics against them to determine if progress is reliable.