super-loop

Orchestrate bulk headless agent sessions with tree-disjoint lane leases and preflight capacity validation.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill super-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-loop
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/super-loop
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill super-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of managing bulk, parallelized agent work without causing system collisions, account session exhaustion, or build-breaking file edits.

Core Features & Use Cases

  • Bulk Headless Launching: Fans out multiple independent agent sessions to resolve issues in parallel.
  • Safety-First Orchestration: Implements preflight checks, tree-disjoint lane management, and account capacity monitoring to prevent DoS and race conditions.
  • Use Case: When you need to clear a large backlog of issues overnight, use this skill to spin up a fleet of workers that operate within defined safety boundaries and report back on their progress.

Quick Start

Use the super-loop skill to plan and launch a wave of workers to resolve the top-ranked issues in the current repository.

Frequently Asked Questions about super-loop

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

FAQPage Schema
How do I run parallel headless agent sessions to clear a backlog without causing collisions?

Parallel headless agent sessions are orchestrated through bulk deployment with preflight capacity validation and tree-disjoint lane enforcement to prevent file edit collisions and system instability across multi-account environments.

What is the best way to safely fan out detached agent workers for overnight issue resolution?

Detached agent workers are safely fanned out using strict safety protocols that enforce account capacity monitoring and witnessed commit verification, ensuring operational honesty and preventing session exhaustion during overnight backlog maintenance.

How do headless agent dispatch scripts prevent race conditions in multi-account environments?

Headless agent dispatch scripts prevent race conditions by implementing tree-disjoint lane leases and preflight capacity validation, which isolate sessions and prevent overlapping file edits across multiple accounts.

Can I use bulk agent automation to resolve repository issues across multiple accounts simultaneously?

Bulk agent automation supports multi-account environments by validating account capacity and enforcing tree-disjoint lane leases before dispatching parallel workers to resolve top-ranked repository issues simultaneously.

Why does parallelized agent work require preflight capacity validation and witnessed commit verification?

Parallelized agent work requires preflight capacity validation to prevent account session exhaustion and witnessed commit verification to guarantee operational honesty, ensuring system stability during bulk headless launches.

When should I avoid using headless agent orchestration for workflow automation?

Headless agent orchestration should be avoided when local dispatch scripts and strict safety protocols are unavailable, as bulk parallelized workers risk build-breaking file edits and race conditions without proper lane management.