toss-phase13-gate

Evaluate AUTH/IAP/MSG/AD gates and output PASS, PARTIAL, or BLOCKED status.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Jason-hub-star/TaillogToss --skill toss-phase13-gate-jason-hub-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toss-phase13-gate
Source: https://github.com/Jason-hub-star/TaillogToss/tree/main/.agents/skills/_backup/20260301-132020/toss-phase13-gate
Command: npx skills add https://github.com/Jason-hub-star/TaillogToss --skill toss-phase13-gate-jason-hub-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 13 Gate operations require fast, evidence-based judgment to determine release readiness and keep artifacts synchronized.

Core Features & Use Cases

  • Evidence-driven gate checks: verifies AUTH/IAP/MSG/AD/B2B readiness with proof logs and latest deployments.
  • Documentation synchronization: aligns status documents with the latest gate results.
  • Operational procedure: collects current status from MCP logs and local test results, then classifies each item as PASS / PARTIAL / BLOCKED and outputs a summarized gate report.

Quick Start

Run the phase 13 gate assessment using current MCP logs and local test results to produce a consolidated gate report.

Frequently Asked Questions about toss-phase13-gate

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

FAQPage Schema
How do I check release readiness for AUTH, IAP, MSG, and AD gates?

To check release readiness, evaluate AUTH, IAP, MSG, and AD gates by collecting current logs and test outcomes to classify each item as PASS, PARTIAL, or BLOCKED. This process generates a formal gate verdict with remediation guidance for pre-release scenarios.

What is a phase 13 gate assessment?

A phase 13 gate assessment is an evidence-driven evaluation that verifies AUTH, IAP, MSG, AD, and B2B readiness using proof logs and latest deployments. It aligns status documents with gate results to provide a quick verdict and synchronized documents before launch.

How do I automate release gate evidence collection from MCP logs?

Automate release gate evidence collection by pulling current status from MCP edge function logs and local test results. The collected artifacts are evaluated against gate criteria to produce a consolidated gate report with formal status classifications.

Do I need local test outcomes and MCP edge function versions to evaluate gate readiness?

Yes, you need local test outcomes, MCP edge function versions, and current logs as required artifacts to evaluate gate readiness. These inputs provide the necessary proof to classify each gate item and generate a formal PASS, PARTIAL, or BLOCKED status.

What's the best way to document pre-release gate verdicts and remediation steps?

The best way to document pre-release gate verdicts is to synchronize status documents with the latest gate results. By classifying items as PASS, PARTIAL, or BLOCKED, you output a summarized gate report containing formal verdicts and specific remediation guidance.