Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    congestion and throughput sensitivity analyst

    1

    Sensitivity analysis for M/M/c queue metrics across parameter sweeps.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    congestion and throughput sensitivity analyst

    congestion and throughput sensitivity analyst

    Example session with this skill installed

    Analyze an M/M/1 queue with lambda=8 and mu=10. Run a sweep for servers [1, 2, 3] to see how it affects wait time and utilization.

    • Read your context and instructions
    • Compiled the congestion and throughput

    I have completed the sensitivity analysis for the M/M/c queue model. The base case (M/M/1) shows high utilization, but increasing the server count significantly reduces wait times and stabilizes the system.

    Queue Sensitivity Analysis Results

    ServersUtilizationP(Wait)Queue Length (Lq)Wait Time (Wq)ThroughputStatus
    1 (Base)0.80000.80003.20000.40008.0000completed
    20.40000.22860.15240.01908.0000completed
    30.26670.05970.02170.00278.0000completed

    Calculation Trace Summary

    • Base Case: Lambda=8.0, Mu=10.0, Servers=1. Utilization is 80%.
    • Stability: All sweep scenarios are stable (rho < 1).
    • Metric Delta: Moving from 1 to 2 servers reduces expected wait time by 95.2%.

    Next steps

    Management decision required: Evaluate if the cost of a second server justifies the 0.381 reduction in wait time units.

    • Validation: Confirm if the arrival rate of 8.0 is an analytical estimate or based on measured historical data.

    Scenario Expansion: Run a sweep on arrival rates (lambda) from 8 to 15 to find the breaking point for a 2-server setup.

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

    About this skill

    Capacity planning fails when you rely on static averages. This skill runs multi-parameter sweeps across M/M/c queue models to pinpoint exactly where utilization spikes and wait times become untenable.

    What it does

    • Parameter sweeps iterates through arrival rates, service rates, and server counts to map system behavior.
    • Congestion metrics calculates utilization, Erlang C probability of waiting, and expected queue lengths.
    • Throughput analysis determines system size and time-in-system metrics for every sweep combination.
    • Stability detection flags unstable configurations where arrival rates exceed service capacity.
    • Audit tracing generates a full calculation trace linking every result to specific formulas and inputs.

    How it works

    1. Provide a base case defining arrival rate (lambda), service rate (mu), and server count.
    2. Define optional arrays for parameter sweeps to test different capacity or demand scenarios.
    3. The system validates inputs and computes the steady-state performance for the entire grid.
    4. Review the sensitivity table and calculation trace to identify optimal server counts.

    Frameworks & tools

    The skill uses a Python-based computational engine for M/M/c queueing theory, utilizing scripts/run.py for grid processing and references/method.md for standardized Erlang C calculations.

    Why this beats prompting it yourself

    Generic LLM prompts often hallucinate Erlang C formulas or fail to maintain precision across large parameter grids. This skill uses a dedicated execution script and formal audit trail to ensure every sensitivity row is mathematically sound and traceable.

    Use cases

    • Identify the break-even server count needed to keep wait times under a specific threshold.
    • Test how a 20% increase in customer arrivals impacts probability of waiting.
    • Compare side-by-side scenarios of hiring more staff versus improving individual service speed.
    • Build data-backed capacity proposals for management approval.

    Known limitations

    Limited to steady-state M/M/c models. It does not support deterministic processing times or non-Poisson arrival patterns.

    Supports only M/M/c steady-state models. Does not handle deterministic or mixed processing times. Requires arrival rates to be less than total service capacity to avoid unstable states.

    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 any payment.

    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 3 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    This skill automates multi-parameter sweeps across M/M/c queue models, allowing you to see how changes in arrival rates or server counts affect wait times and system stability without manual calculation or spreadsheet errors.

    The purchase includes the core execution scripts, a detailed methodology reference for Erlang C calculations, and the configuration schema needed to run sensitivity sweeps.

    While the skill is designed to work with any agent that supports Python-based tool execution, it is optimized for environments where the agent can parse structured data tables and audit traces.

    The skill handles any M/M/c model where the service rate and arrival rate are Markovian (Poisson); however, it is not currently designed for M/G/c or D/D/c models involving non-random or deterministic processing times.

    Yes, the skill includes a stability detection feature that flags 'unstable' configurations where the arrival rate exceeds the total service capacity, preventing skewed or infinite result sets.