---
name: analyzing-system-throughput
description: Analyze and optimize system throughput including request handling, data processing, and resource utilization. Use when identifying capacity limits or evaluating scaling strategies. Trigger with phrases like "analyze throughput", "optimize capacity", or "identify bottlenecks".
version: 1.24.0
allowed-tools: Read, Write, Bash(performance:*), Bash(monitoring:*), Grep
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - performance
  - scaling
  - analyzing-system
compatibility: Designed for Claude Code
title: analyzing-system-throughput
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [assets/README.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput/assets/README.md), [references/README.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput/references/README.md), [scripts/analyze_throughput.py](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput/scripts/analyze_throughput.py), [scripts/identify_bottlenecks.py](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput/scripts/identify_bottlenecks.py), [scripts/README.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput/scripts/README.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/analyzing-system-throughput`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/analyzing-system-throughput) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/analyzing-system-throughput`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/analyzing-system-throughput --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/analyzing-system-throughput --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Throughput Analyzer

Analyze system throughput across request handling, data processing pipelines, and queue consumers to identify capacity limits and evaluate scaling strategies.

## Overview

This skill allows Claude to analyze system performance and identify areas for throughput optimization. It uses the `throughput-analyzer` plugin to provide insights into request handling, data processing, and resource utilization.

## How It Works

1. **Identify Critical Components**: Determines which system components are most relevant to throughput.
2. **Analyze Throughput Metrics**: Gathers and analyzes current throughput metrics for the identified components.
3. **Identify Limiting Factors**: Pinpoints the bottlenecks and constraints that are hindering optimal throughput.
4. **Evaluate Scaling Strategies**: Explores potential scaling strategies and their impact on overall throughput.

## When to Use This Skill

This skill activates when you need to:

- Analyze system throughput to identify performance bottlenecks.
- Optimize system performance for increased capacity.
- Evaluate scaling strategies to improve throughput.

## Examples

### Example 1: Analyzing Web Server Throughput

User request: "Analyze the throughput of my web server and identify any bottlenecks."

The skill will:

1. Activate the `throughput-analyzer` plugin.
2. Analyze request throughput, data throughput, and resource saturation of the web server.
3. Provide a report identifying potential bottlenecks and optimization opportunities.

### Example 2: Optimizing Data Processing Pipeline

User request: "Optimize the throughput of my data processing pipeline."

The skill will:

1. Activate the `throughput-analyzer` plugin.
2. Analyze data throughput, queue processing, and concurrency limits of the data processing pipeline.
3. Suggest improvements to increase data processing rates and overall throughput.

## Best Practices

- **Component Selection**: Focus the analysis on the most throughput-critical components to avoid unnecessary overhead.
- **Metric Interpretation**: Carefully interpret throughput metrics to accurately identify limiting factors.
- **Scaling Evaluation**: Thoroughly evaluate the potential impact of scaling strategies before implementation.

## Integration

This skill can be used in conjunction with other monitoring and performance analysis tools to gain a more comprehensive understanding of system behavior. It provides a starting point for further investigation and optimization efforts.

## Prerequisites

- Access to throughput metrics in ${CLAUDE_SKILL_DIR}/metrics/throughput/
- System performance monitoring tools
- Historical throughput baselines
- Current capacity and scaling limits

## Instructions

1. Identify critical system components for throughput analysis
2. Collect request and data throughput metrics
3. Analyze resource saturation and queue depths
4. Identify bottlenecks and limiting factors
5. Evaluate horizontal and vertical scaling strategies
6. Generate capacity planning recommendations

## Output

- Throughput analysis reports with current capacity
- Bottleneck identification and root cause analysis
- Resource saturation metrics
- Scaling strategy recommendations
- Capacity planning projections

## Error Handling

If throughput analysis fails:

- Verify metrics collection infrastructure
- Check system monitoring tool access
- Validate historical baseline data
- Ensure performance testing environment
- Review component identification logic

## Resources

- Throughput optimization best practices
- Capacity planning methodologies
- Scaling strategy comparison guides
- Performance bottleneck detection techniques
