Performance profile

Skill manastalukdar/ai-devstudio/skills/performance-profile

Professional development studio for Claude Code CLI

Install

npx -y skills add manastalukdar/ai-devstudio --skill performance-profile

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Performance profiling and bottleneck detection for Node.js, Python, and browser apps

SKILL.md

1.1 KB, 194 tokens by cl100k_base, as published. Nobody here has run it

Performance Profiling & Bottleneck Detection

I'll profile your application to identify performance bottlenecks and provide optimization recommendations.

Supported Environments:

Node.js profiling (--inspect, clinic.js)
Browser performance (Chrome DevTools)
Python profiling (cProfile, line_profiler)
Bottleneck identification
Memory leak detection
Optimization recommendations

Arguments: $ARGUMENTS - optional: node|python|browser or specific file/route to profile

Token Optimization

Expected range: 400–2,500 tokens (initial), 200 tokens (cache hit)

Caching: Caches runtime detection in .claude/cache/performance-profile/runtime.json for 7 days. Invalidated when package.json changes.

Early exit: Returns immediately if the profiling environment is already configured.

Patterns used: Grep-before-Read, early exit, Bash for system queries, caching

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most performance cost skills give in 194 tokens

Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-07

Keep skill files under 500 lines or tokensin 82 of 803, across 16 files
Use imperative form in instructionsin 80 of 803, across 9 files
Draft assertions while test runs are in progressin 75 of 803, across 9 files
Create two to three realistic test promptsin 74 of 803, across 9 files
Write skill descriptions to be pushyin 72 of 803, across 7 files
Save test cases to evals JSONin 72 of 803, across 6 files
Ask questions about edge cases and input formatsin 72 of 803, across 7 files
Save timing data immediately when runs completein 70 of 803, across 5 files
Include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
Launch all test runs in a single turn or simultaneouslyin 69 of 803, across 3 files
Capture intent before writing a skillin 67 of 803, across 1 file
Import directly instead of barrel filesin 52 of 803, across 15 files

Said here and by no other author read

cache runtime detection results
return immediately if environment is configured
use bash for system queries

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.