Code Profiling

VerifiedSafe

Profiles code execution speed to pinpoint performance bottlenecks. Supports simple timers, cProfile, and line profiler, analyzing cumulative time and call counts to suggest optimizations like vectorization or caching.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#python#profiling#performance#optimization

Recommended for

Automated summary

This skill profiles Python code to identify performance bottlenecks.

Strengths

  • Supports multiple profiling tools (simple timer, cProfile, line_profiler) for different needs.
  • Analyzes output focusing on cumulative time and call counts.
  • Suggests concrete optimizations like vectorization, caching, or algorithm changes.

Limitations

  • Requires the user to have dependencies installed (line_profiler) for line-by-line analysis.
  • Profiling can slow down execution significantly, especially cProfile on large scripts.
  • Does not cover memory or I/O profiling, only CPU time.
When to use it

When a Python script is slow and you need to pinpoint the exact parts to optimize.

When not to use it

For obvious performance issues (e.g., infinite loop) or when code is already well-optimized and expected gain is small.

Security analysis

Safe
Quality score80/100

The skill uses standard Python profiling tools and does not instruct to perform any destructive, exfiltrating, or obfuscated actions. It runs user-provided scripts, but that is inherent to its profiling purpose and not an added risk beyond typical code execution.

No concerns found

How this analysis is made

Examples

Profile a Python script for bottlenecks
Profile my script 'data_processing.py' using cProfile and show me which functions take the most time.
Line-by-line profiling with line_profiler
I have a function 'process_data' in 'analysis.py' that is slow. Can you add the @profile decorator and run kernprof to show line-by-line timing?

name: profile description: 指定したコードの実行速度をプロファイリングし、ボトルネックを特定する

Profile Code

This skill helps find performance bottlenecks in the code.

Instructions

  1. Identify Target:

    • Ask user for the script or function call to profile.
  2. Run Profiler:

    • Simple Timer: For quick checks, wrap code in time.perf_counter().
    • cProfile: Run python -m cProfile -s cumulative <script_name.py>.
    • Line Profiler: If detailed line-by-line analysis is needed, suggesting adding @profile decorator and running kernprof -l -v <script_name.py> (requires line_profiler installed).
  3. Analyze Output:

    • Look for functions with high cumtime (cumulative time).
    • Look for functions with high call counts (ncalls).
  4. Report:

    • Summarize which parts of the code are consuming the most time.
    • Suggest potential optimizations (vectorization, caching, algorithm change).

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/code-profiling-mmbizkxd/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/code-profiling-mmbizkxd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-profiling-mmbizkxd/download' --output '.skill-downloads/code-profiling-mmbizkxd/SKILL.md.part' && mv '.skill-downloads/code-profiling-mmbizkxd/SKILL.md.part' '.skill-downloads/code-profiling-mmbizkxd/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/code-profiling-mmbizkxd/SKILL.md' && test -s '.skill-downloads/code-profiling-mmbizkxd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/profile' && cp -R '.skill-downloads/code-profiling-mmbizkxd' '.claude/skills/profile'

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/code-profiling-mmbizkxd'

openskills read 'code-profiling-mmbizkxd'

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/code-profiling-mmbizkxd/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