System Load Profile Outline

VerifiedSafe

Outlines the load profile of a system or component by mapping request flows, peak usage, data growth, and resource consumption. Helps identify bottlenecks and scaling risks directly from the source code.

Sby Skills Guide Bot
TestingIntermediate
6/2/2026
Claude Code
#load-profile#scaling#performance#bottlenecks

Recommended for

Automated summary

This skill maps the load profile of a system or component by tracing request flows and identifying bottlenecks and scaling risks.

Strengths

  • Systematic identification of common bottlenecks (N+1 queries, unbounded collections, etc.)
  • Multi-scale load estimation (current, 10x, 100x) to anticipate growth
  • Step-by-step workflow ensures reproducible analysis

Limitations

  • Relies on static code analysis, not runtime profiling or monitoring
  • Load estimates are speculative without production traffic data
  • Requires familiarity with the codebase to trace flows accurately
When to use it

Use when preparing for a scalability review, planning capacity, or before deploying performance-sensitive changes.

When not to use it

Do not use for actual load testing or when precise capacity planning metrics are needed from real traffic.

Security analysis

Safe
Quality score85/100

The skill only reads and explores code using Read, Grep, Glob, and Bash for analysis. It does not execute destructive commands, exfiltrate data, or disable safety measures. Bash usage is limited to code exploration, not arbitrary execution.

No concerns found

How this analysis is made

Examples

Authentication service load profile
Outline the load profile for the user authentication service in the auth/ directory.
Database layer scaling analysis
Map the load characteristics of the database access layer in src/db/.
API endpoint scaling risks
Outline load for the /api/orders endpoint and identify bottlenecks.

name: outline-load description: Outline the load profile for a system or component — map traffic patterns, peak usage, data growth, and resource consumption over time. user_invocable: true argument-hint: <component or system path> allowed-tools: ["Read", "Grep", "Glob", "Bash"]

Outline Load Profile

Map the load characteristics of a component or system to understand its scaling behavior.

Arguments: $ARGUMENTS

Workflow

Step 1: Identify the Component

Read the target component from $ARGUMENTS. Explore its:

  • Entry points (API endpoints, CLI commands, event handlers, scheduled jobs)
  • Data stores it reads from and writes to
  • External service calls

Step 2: Map Request Flow

For each entry point, trace the request path:

  1. Ingress: How does work arrive? (HTTP, queue, cron, user action)
  2. Processing: What computation happens? (CPU-bound, I/O-bound, memory-bound)
  3. Egress: Where do results go? (response, database write, file output, notification)

Step 3: Estimate Load Dimensions

For each flow, estimate:

| Dimension | Current | 10x | 100x | |-----------|---------|-----|------| | Requests/sec | | | | | Data per request | | | | | Total storage | | | | | Concurrent connections | | | | | Memory per request | | | |

Fill in what can be determined from code. Mark unknowns as ?.

Step 4: Identify Bottlenecks

Look for:

  • Single-threaded paths: Synchronous processing that blocks
  • Unbounded collections: Arrays/lists that grow with input size
  • N+1 queries: Database/API calls inside loops
  • Global state: Shared mutable state across requests
  • Missing pagination: Queries without LIMIT/OFFSET
  • Large file reads: Reading entire files into memory

Step 5: Output the Load Profile

## Load Profile: [Component]

**Entry Points**: [count] ([list])
**Processing Type**: [CPU-bound | I/O-bound | Memory-bound | Mixed]

**Current Load Estimate**:
[table from Step 3]

**Bottlenecks Identified**:
1. [file:line] — [description]
2. [file:line] — [description]

**Scaling Risks**:
- [risk 1]
- [risk 2]

**Recommendation**: [scale-ready | needs-work | redesign-required]

This feeds into /scale-review:evaluate for detailed analysis.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/system-load-profile-outline-mma3jrru' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/system-load-profile-outline-mma3jrru/download' --output '.skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md.part' && mv '.skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md.part' '.skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md' && test -s '.skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/outline-load' && cp -R '.skill-downloads/system-load-profile-outline-mma3jrru' '.claude/skills/outline-load'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/system-load-profile-outline-mma3jrru'

openskills read 'system-load-profile-outline-mma3jrru'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/system-load-profile-outline-mma3jrru/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills