optimize-code
Analyze and optimize Python code performance in critical paths
67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (Python performance optimization) but is too brief and lacks the explicit trigger guidance needed for Claude to reliably select it. It needs concrete action examples and a 'Use when...' clause to be effective in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with trigger terms like 'slow Python code', 'speed up', 'profiling', 'bottleneck', 'benchmark', or 'memory optimization'.
Expand specific capabilities to include concrete actions like 'profile execution time', 'identify bottlenecks', 'optimize loops and data structures', 'reduce memory usage'.
Clarify what 'critical paths' means or replace with more natural user language like 'hot code paths', 'frequently-called functions', or 'performance-sensitive sections'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Python code performance) and implies actions (analyze, optimize), but lacks concrete specific actions like 'profile execution time', 'identify bottlenecks', 'refactor hot loops', or 'benchmark functions'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Python', 'performance', 'optimize', 'critical paths') but misses common user terms like 'slow code', 'speed up', 'profiling', 'bottleneck', 'benchmark', or 'memory usage'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Python performance optimization, but 'critical paths' is vague and could overlap with general Python coding skills or code review skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill for Python performance optimization with excellent workflow clarity and concrete, executable guidance. The phased approach with mandatory benchmarking checkpoints is well-designed. Main weaknesses are moderate verbosity in explanatory sections and lack of progressive disclosure to separate reference material from the core workflow.
Suggestions
Extract detailed optimization patterns (sections 2.4-2.6) into a separate PATTERNS.md reference file to reduce main skill length
Move the benchmark data table and process isolation details to a BENCHMARKING.md reference for cleaner progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity, such as the detailed explanations of why caches can hurt performance and the extensive benchmark data table. Some sections could be tightened while preserving clarity. | 2 / 3 |
Actionability | Provides fully executable code examples throughout, including timeit oneliners, benchmark scripts, bash commands, and concrete Python patterns. Copy-paste ready with specific file paths and realistic test data references. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with clear sequencing (5 phases), explicit validation checkpoints (benchmark before/after each change, verify correctness, run tests), and feedback loops for incremental optimization with measurement. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear phases and subsections, but it's a monolithic document that could benefit from splitting detailed patterns (2.4-2.6) and benchmark methodology into separate reference files. No external file references provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.