bottleneck-map

Map system-level bottlenecks and GitHub issue backlog constraints into actionable reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity of operational bottlenecks by mapping system health against the GitHub issue backlog, preventing the common mistake of launching more workers when the system is already at capacity.

Core Features & Use Cases

  • Fleet Bottleneck Detection: Automatically identifies system-level constraints like rate limits, auth failures, or recovery debt.
  • Issue Triage Integration: Correlates system health with open-work status to determine if the primary blocker is technical or structural.
  • Durable Process Loop: Provides a standardized, read-only audit of system state and backlog health to guide the next operational move.

Quick Start

Ask the agent to map the current system and backlog bottlenecks to identify the next durable process loop.

Frequently Asked Questions about bottleneck-map

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

FAQPage Schema
How do I identify system bottlenecks and backlog constraints in my fleet?

To identify system bottlenecks and backlog constraints, you map fleet health telemetry against GitHub issue triage data to classify blockers by scope, horizon, and weight for actionable reporting.

What is the best way to correlate fleet health with GitHub issue backlog status?

Correlating fleet health with GitHub issue backlog status requires read-only access to fleet registry files and issue metadata to determine if primary blockers are technical or structural.

Can I use read-only access to map operational flow and rate limits?

Yes, you can use read-only access to map operational flow by auditing fleet registry files and issue metadata, detecting system-level constraints like rate limits and recovery debt without modifying state.

How do I triage GitHub issues against fleet telemetry to find blockers?

Triaging GitHub issues against fleet telemetry involves standardizing a read-only audit of system state and backlog health, classifying blockers to guide the next durable process loop.

When should I map system bottlenecks before scaling workers?

You should map system bottlenecks before scaling workers to prevent launching more workers when the system is already at capacity, avoiding the common mistake of worsening operational constraints.