lean-gateway

Name: lean-gateway
Availability: InStock
Author: r-irbe

Route Lean 4 tasks to downstream skills with per-session state.

2|Updated May 26, 2026

Search Tags:#enforcement #orchestrator #gateway #fan-out #task-routing #fan-in #context-collapse

Ready to run

npx skills add https://github.com/r-irbe/proof-skills --skill lean-gateway

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lean-gateway
Source: https://github.com/r-irbe/proof-skills/tree/main/skills/lean-gateway
Command: npx skills add https://github.com/r-irbe/proof-skills --skill lean-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes Lean 4 tasks to the correct downstream skills and maintains per-session state to prevent context collapse.

Core Features & Use Cases

Task routing and fan-in/fan-out coordination across multiple skills during long-running Lean sessions.
Health monitoring and session state management to prevent context drift and ensure reliable progress.
Use Case: Deploy in a multi-skill session where a single theoretical development spans proofs, reviews, and documentation.

Quick Start

Start a new Lean 4 task session and let lean-gateway delegate each phase to the owning skills.

Frequently Asked Questions about lean-gateway

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

FAQPage Schema

How do I route Lean 4 tasks to downstream skills without losing context?▼

Task routing for Lean 4 is handled by delegating operations through a central gateway that maintains per-session state. This prevents context collapse by applying topology selection and fan-out coordination to dispatch proofs and reviews to the correct downstream skills.

What causes context collapse during long-running Lean 4 sessions?▼

Context collapse in long-running Lean 4 sessions occurs when multi-module developments drift without centralized state management. A gateway prevents this by maintaining per-session state, ensuring reliable progress across proofs, reviews, and documentation spanning multiple files.

How do I coordinate fan-in and fan-out across multiple Lean 4 skills?▼

Fan-in and fan-out coordination across Lean 4 skills is managed by a central orchestrator that distributes tasks to downstream skills and aggregates results. This ensures delegation-only operations during complex theoretical developments spanning multiple files and projects.

Do I need a gateway for Lean 4 multi-skill sessions spanning proofs and reviews?▼

For Lean 4 multi-skill sessions spanning proofs, reviews, and documentation, a gateway is required to manage topology selection and health monitoring. It enforces delegation-only operations and maintains session state to prevent context drift across modules.

Best way to manage session state for Lean 4 theoretical developments across files?▼

The best way to manage Lean 4 session state across files is using a central gateway that implements health monitoring and enforcement hooks. This orchestrator maintains per-session state and applies topology selection to prevent context collapse during long-running developments.