CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

application-performance-performance-optimization

Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.

Quality

77%

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/application-performance-performance-optimization/SKILL.md

The canonical home for this skill is application-performance-performance-optimization in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured orchestration skill with genuinely concrete subagent prompts, explicit success criteria, and a sensible phased workflow including a dedicated validation phase. The main costs are a padded meta-commentary block, template artifacts ('$ARGUMENTS', '{context_from_phase_1}'), and the absence of an explicit failure/retry loop.

Suggestions

Delete the '[Extended thinking: ...]' paragraph and the trailing 'Performance optimization target: $ARGUMENTS' line — neither instructs the model and both waste context tokens (conciseness).

Replace the literal '{context_from_phase_1}' placeholders in step prompts with a concrete instruction (e.g., 'insert the bottleneck summary from Phase 1 here') or drop them (actionability).

Add an explicit feedback loop after Phase 4, e.g., 'If load tests show regressions or misses against Success Criteria, return to the phase owning the bottleneck and re-validate' (workflow_clarity).

DimensionReasoningScore

Conciseness

The body is mostly terse, but the '[Extended thinking: ...]' paragraph is meta-commentary about the workflow's philosophy rather than instruction, and the trailing 'Performance optimization target: $ARGUMENTS' line is a leftover template artifact; both could be cut.

3 / 5

Actionability

Each of the 13 steps supplies a near copy-paste Task prompt naming concrete tools (k6/Gatling/Artillery, OpenTelemetry, Redis/Memcached) plus measurable thresholds (P50 < 200ms, LCP < 2.5s), with the minor gap of unresolved '{context_from_phase_1}' placeholders inside prompts.

4 / 5

Workflow Clarity

Five phases with 13 numbered steps, each carrying Context and Output, give a clear sequence, and Phase 4 plus the Safety section provide explicit validation and rollback guidance. It stops short of anchor 5 because there is no fail-and-revisit feedback loop (e.g., what to do when load testing shows no improvement or a regression).

4 / 5

Progressive Disclosure

With no bundle files present, the skill is self-contained and well-sectioned (Use/Do-not-use, Instructions, Safety, phases, configuration, success criteria). Minor gap: all 13 detailed dispatch prompts are inlined in a ~150-line file rather than split into a reference, which keeps the overview from staying lean.

4 / 5

Total

15

/

20

Passed

Description

75%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 solid description that answers both what the skill does and when to use it in third-person voice with a domain-specific vocabulary. Its main weakness is a somewhat narrow 'Use when' trigger that under-sells the breadth (baselines, load testing, capacity planning) the body actually covers.

DimensionReasoningScore

Specificity

The description lists several specific actions — 'profiling, observability, and backend/frontend tuning' — but 'tuning' and 'end-to-end...across the stack' remain broad, so coverage is good rather than comprehensive.

4 / 5

Completeness

Both 'what' (optimize via profiling, observability, backend/frontend tuning) and 'when' ('Use when coordinating performance optimization across the stack') are explicit, but the 'when' clause is narrow and omits the richer triggers the body itself lists (baselines, load tests, capacity plans).

4 / 5

Trigger Term Quality

Natural terms like 'application performance', 'profiling', 'observability', and 'performance optimization' are present and would be said by users, though common variations such as 'slow', 'speed up', 'latency', 'scalability', and 'load testing' are missing.

4 / 5

Distinctiveness Conflict Risk

The performance-engineering focus is a mostly distinct niche, with only minor overlap risk against narrower database- or frontend-optimization skills.

4 / 5

Total

16

/

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

agent-skills-hub/agent-skills-hub

Path

skills/application-performance-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.