CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-performance-optimization

Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/python-development/skills/python-performance-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body functions as a serviceable overview with a clean progressive-disclosure pointer and one solid executable example, but roughly half of it restates concepts and generic advice Claude already knows. It also lacks an explicit profile-then-optimize-then-verify workflow, and one of the two bundle reference files is orphaned from the top-level navigation.

Suggestions

Delete the Core Concepts section (profiling types, performance metrics, optimization strategies) and the 9-bullet When to Use list — Claude already knows these, and the frontmatter description already covers the use cases; keep only the Quick Start, the reference pointer, and a trimmed best-practices list.

Add an explicit sequenced workflow with a verification checkpoint, e.g.: 1. Time/baseline with timeit, 2. Profile with cProfile (see references/details.md), 3. Optimize the top bottleneck, 4. Re-benchmark to confirm the speedup before moving on.

Surface references/advanced-patterns.md in the body alongside details.md (e.g., 'Advanced patterns (NumPy, parallelization, async I/O): see references/advanced-patterns.md') so both bundle files are one level deep and discoverable from the skill overview, instead of chained through details.md.

DimensionReasoningScore

Conciseness

Several padded sections explain concepts Claude already knows: "CPU Profiling: Identify time-consuming functions", "Execution Time: How long operations take", "Caching: Avoid redundant computation", plus a 9-bullet "When to Use" list that duplicates the frontmatter description. This matches the anchor for noticeably verbose with several unnecessary explanations; not 3 because the known-concept definitions (the entire Core Concepts section) and generic Best Practices/Pitfalls are more than 'some' unnecessary explanation, but not 1 since there is no long padded prose and the Quick Start code is tight.

2 / 5

Actionability

The Quick Start timing code (time.time / timeit) is executable and complete, but the skill's headline capabilities — "cProfile, memory profilers" — have no code or commands in the body, and tips like "Use py-spy for live systems" and "Cache expensive computations - Use lru_cache" name tools without any commands. This sits between the anchor for some concrete but incomplete guidance (3) and mostly executable guidance (4): key profiling commands are deferred to references/details.md, which is a central gap rather than a minor one.

3 / 5

Workflow Clarity

The optimize-after-measuring sequence is only implicit ("Profile before optimizing - Measure to find real bottlenecks") — no numbered or ordered workflow exists in the body, and there is no verification step (re-benchmark to confirm an improvement). Matches the anchor for sequence present but checkpoints missing or implicit; not 4 because no explicit ordered steps or checkpoints are written, not 2 because the structure and profile-first principle do convey a coherent rough order.

3 / 5

Progressive Disclosure

The body clearly signals one reference ("Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient."), but the second bundle file, references/advanced-patterns.md, is never mentioned in the body — it is only linked from inside details.md ("see [references/advanced-patterns.md]"), creating a buried two-level chain. Scoring against the actual bundle structure, this matches the anchor for references present but not clearly signaled / could be better organized; not 4 because an entire bundle file being undiscoverable from the top level is more than a minor gap, not 2 because the overview-plus-one-clear-reference split is genuinely present.

3 / 5

Total

11

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states what the skill does with named tools (cProfile, memory profilers) and includes a well-formed 'Use when' clause with natural trigger phrases. The only weaknesses are the generic "performance best practices" tail and a few missing natural synonyms (e.g., "speed up", "latency").

DimensionReasoningScore

Specificity

"Profile and optimize Python code using cProfile, memory profilers" names concrete actions and specific tools, matching the anchor listing several specific actions with minor gaps. Not 5 because "and performance best practices" is generic filler and coverage of capabilities (e.g., line profiling, production profiling) is incomplete; not 3 because naming concrete tools goes beyond the 1–2-action anchor example.

4 / 5

Completeness

Both halves are explicit: the what ("Profile and optimize Python code using cProfile, memory profilers") and the when ("Use when debugging slow Python code, optimizing bottlenecks, or improving application performance") with three concrete trigger phrases. This matches the anchor for clearly and explicitly answering both what AND when; neither the 4 anchor (when only weakly specified) nor below fits better.

5 / 5

Trigger Term Quality

"debugging slow Python code, optimizing bottlenecks, or improving application performance" covers natural phrases users would say (slow code, optimize, bottleneck, performance). Not 5 because common synonyms like "speed up", "faster", "latency", or "memory usage" are missing; not 3 because coverage goes beyond a single generic keyword with several relevant natural terms.

4 / 5

Distinctiveness Conflict Risk

"Profile and optimize Python code" carves a clear niche with performance-specific triggers, but "debugging" and "improving application performance" leave minor overlap risk with general debugging or Python-development skills. Not 5 because the triggers are not as narrowly fenced as a file-extension-anchored niche; not 3 because the domain is distinctly Python performance, not broadly "document files".

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/python-development/skills/python-performance-optimization/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.