Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Business Process Bottleneck Analyst

    1

    Diagnose operational bottlenecks, identify root causes, and build prioritized process improvement roadmaps.

    $29.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Business Process Bottleneck Analyst

    Business Process Bottleneck Analyst

    Example session with this skill installed

    Analyze our customer onboarding process. It takes 15 days from contract sign to go-live. We have 3 steps: Technical Setup (2 days), Training (3 days), and Final Review (10 days wait). 20 units/mo.

    • Read your context and instructions
    • Compiled the business process bottleneck

    I have analyzed the customer onboarding workflow. The primary constraint is a significant waiting period at the Final Review stage, which accounts for 66% of the total lead time.

    Process Bottleneck Analysis: Customer Onboarding

    Finding IDFinding TitleAffected StepEvidenceConfidencePriority
    B-001Final Review Queue StagnationFinal Review10-day wait vs 5-day total workHighP0
    B-002Low Process EfficiencyEntire Flow33% Value-Add Ratio (5/15 days)HighP1

    Root Cause Analysis

    • Symptom: Items sit for 10 days in the Final Review queue.
    • Hypothesis 1: Capacity mismatch. The reviewer role has less than 20 units/month capacity.
    • Hypothesis 2: Batching. Work is only reviewed once every two weeks.
    • Hypothesis 3: Dependency. The reviewer is waiting on external inputs not captured in the 3-step map.

    Recommended Improvements

    Implement WIP Limits: Restrict the number of clients in the 'Training' phase to prevent flooding the 'Final Review' queue. (Effort: Small | Owner: Ops Manager)
    2.

    Review Frequency: Shift from bi-weekly batch processing to a daily review cadence to reduce wait time. (Effort: Medium | Owner: Team Lead)
    3.

    Standardized Intake: Ensure 'Technical Setup' and 'Training' meet a specific checklist before hitting 'Final Review' to prevent rework. (Effort: Small | Owner: Success Team)

    Next steps

    1. Provide the specific number of staff members assigned to the 'Final Review' role.
    2. Confirm if reviews are performed on a set schedule (batching) or as they arrive.
    3. Share the current 'rework rate' for items rejected during the Final Review.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Operational inefficiencies and hidden bottlenecks drive up costs and kill customer satisfaction. This skill provides a structured framework to diagnose exactly where work stalls, why tasks accumulate, and how to fix flow issues using evidence-based analysis.

    What it does

    • Process Mapping identifies every step, owner, system, and handoff point to define the full workflow boundary.
    • Metric Calculation establishes baselines for lead time, processing time, throughput, and work-in-progress (WIP) levels.
    • Bottleneck Detection pinpoints where queues form, where waiting time exceeds processing time, and where capacity imbalances occur.
    • Root Cause Analysis uses structured methods like Five Whys and Fishbone to separate visible symptoms from underlying process failures.
    • Impact Quantification estimates lost throughput, rework hours, and missed service-level targets caused by specific constraints.
    • Improvement Roadmapping delivers prioritized recommendations with specific owners, effort levels, and validation metrics.

    How it works

    1. Define the process start trigger, completion event, and success criteria for the investigation.
    2. Input process narratives, task logs, SOPs, or raw operational data for the analyst to ingest.
    3. Analyze the workflow via a nine-phase structured diagnostic to identify constraints and causes.
    4. Review the comprehensive report containing the process map, findings, and the prioritized experiment plan.

    Frameworks & tools

    The skill utilizes Lean and Six Sigma principles, including Five Whys, Fishbone (Ishikawa) diagrams, Pareto analysis, and Theory of Constraints. It processes data from ticket systems, spreadsheets, and operational dashboards.

    Why this beats prompting it yourself

    Generic prompts often confuse symptoms with root causes or jump straight to automation before understanding the constraint. This skill enforces a rigorous nine-phase diagnostic workflow that separates facts from hypotheses, ensuring every recommendation is backed by evidence and measurable validation experiments.

    Use cases

    • Service Desk Optimization to reduce ticket aging and resolve recurring rework loops in support tiers.
    • Supply Chain Review to identify lead time delays and inventory build-up at specific vendor handoffs.
    • Software Development Lifecycle to find wait states in the CI/CD pipeline and approval bottlenecks.
    • Internal Ops Audit to streamline departmental approvals and clarify ownership in complex administrative processes.

    Known limitations

    Analysis quality depends entirely on the accuracy of user-provided cycle times and volumes. It cannot observe live operations or verify physical site conditions.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Relies on user-provided data for metrics. Does not perform real-time monitoring or physical site observation. Scope is limited to process logic and recorded operational evidence.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 16 days ago

    Permissions

    No special permissions declared or detected

    Listed16 days ago

    What's inside

    Frequently Asked Questions

    This skill analyzes operational data and narratives to identify where workflows stall, calculates performance metrics like lead time, and provides a prioritized roadmap to eliminate bottlenecks. It is designed to solve issues like high operational costs, recurring rework, and missed service-level targets.

    The skill is a standalone diagnostic framework designed for use with major LLMs like GPT-4 or Claude 3.5. You can provide data via CSV, task logs, or written process descriptions directly into your agent's interface.

    No complex installation is required; once purchased, you can immediately initiate the nine-phase diagnostic workflow by providing your process parameters and operational data. The package includes a comprehensive user guide to help you structure your inputs for the most accurate analysis.

    Unlike basic prompts, this skill follows a rigid Nine-Phase Diagnostic methodology that prevents the AI from jumping to conclusions. It forces a separation between symptoms and root causes using built-in Lean and Six Sigma frameworks like Fishbone and Pareto analysis.

    You receive the full diagnostic logic, a structured input template for your data, and a guide on interpreting the final improvement roadmap. Buyers also receive free access to any future logic updates or framework enhancements released for this version.

    The skill requires accurate cycle times and volume data to be effective; it cannot 'guess' missing metrics or observe physical workplace behavior. It is best suited for digital or documented workflows where handoff points and processing times are known.

    New in Business & Operations