CtrlK
BlogDocsLog inGet started
Tessl Logo

performance-expert

Performance optimization - profiling, benchmarking, optimization

52

Quality

65%

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 ./skills/performance-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A well-organized, mostly executable reference catalog of performance techniques that lacks any sequenced workflow with validation checkpoints and keeps everything inline rather than splitting advanced detail into referenced files.

Suggestions

Add validation feedback loops for database work: run EXPLAIN ANALYZE before and after adding an index and verify the index is used before moving on.

Move the longer worked examples (e.g., full profiling workflows, caching patterns) into referenced files (profiling.md, caching.md) and keep SKILL.md as a concise overview with one-level-deep links.

Frame a recommended optimization workflow (measure → identify hot path → optimize → re-measure) so the techniques are sequenced with explicit checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable code with almost no concept explanation Claude doesn't already know; only minor padding (the closing aphorism, a few obvious code comments) keeps it from a 5.

4 / 5

Actionability

Concrete, copy-paste-ready examples span Node.js, Python, SQL, TypeScript, and Redis, covering common cases; the web-vitals snippet only logs to console and a few examples lack surrounding invocation context.

4 / 5

Workflow Clarity

The body is a topic catalog rather than a sequenced process, and database/index operations appear without before/after validation (e.g., EXPLAIN ANALYZE before and after adding an index), capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Sections are clearly headed and well-organized, but all content is inlined monolithically with no references to deeper material despite the skill exceeding 50 lines.

3 / 5

Total

14

/

20

Passed

Description

50%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.

The description states the domain and a few actions but is generic and lacks an explicit trigger clause, capping completeness and distinctiveness at the midpoint.

Suggestions

Add a 'Use when…' clause naming concrete user triggers (e.g., 'Use when the user asks to speed up code, reduce latency, profile a hot path, or improve Core Web Vitals').

Replace the redundant second 'optimization' with a distinct capability (e.g., 'memory profiling' or 'bottleneck analysis').

Include natural synonyms users actually say ('slow', 'latency', 'benchmark') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Performance optimization') plus a couple concrete actions ('profiling, benchmarking'), but 'optimization' restates the domain rather than adding a distinct capability, leaving coverage non-comprehensive.

3 / 5

Completeness

Provides a clear 'what' but no 'Use when…' trigger clause, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('profiling', 'benchmarking', 'performance optimization') but omits common user phrasings like 'speed up', 'slow', 'latency', or 'Core Web Vitals'.

3 / 5

Distinctiveness Conflict Risk

The performance niche is recognizable, but the broad 'optimization' framing could overlap with dedicated database or frontend skills.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
TurnaboutHero/oh-my-antigravity
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.