Name: application-performance-performance-optimization
Rating: 45.6 (1 reviews)
Author: popey

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

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/application-performance-performance-optimization/SKILL.md

Quality

Content

27%Scale 1-3

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

This skill is an ambitious end-to-end performance optimization orchestration guide, but it suffers from extreme verbosity—most of the content is lengthy prompt templates that repeat structural patterns Claude already knows. It lacks executable code, concrete commands, and explicit validation checkpoints between phases. The monolithic structure with no supporting bundle files makes it a poor fit for the progressive disclosure model expected of well-structured skills.

Suggestions

Drastically reduce prompt templates to concise bullet points of key concerns per step rather than full natural-language prompts—Claude can compose prompts from brief instructions.

Add explicit validation gates between phases (e.g., 'Verify baseline metrics are captured and documented before proceeding to Phase 2') to improve workflow clarity for this multi-step, potentially destructive process.

Split detailed phase instructions, configuration options, and success criteria into separate bundle files (e.g., PHASES.md, CONFIG.md) and reference them from a concise overview in SKILL.md.

Remove the extended thinking block and 'Use this skill when / Do not use' sections, which add little value for Claude's execution and consume significant tokens.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive prompt templates that are largely boilerplate. The extended thinking block is unnecessary filler. Each step repeats context-passing patterns and tool invocation patterns that Claude already understands. The entire document could be condensed to roughly 1/4 its size without losing actionable information.	1 / 3
Actionability	The skill provides structured phases and named tools/subagent types, giving some concrete guidance on orchestration. However, it contains no executable code, no real commands, and relies entirely on prompt templates with placeholder variables like {context_from_phase_1} and $ARGUMENTS. The guidance is more of a high-level playbook than copy-paste-ready instructions.	2 / 3
Workflow Clarity	The 5-phase structure with 13 numbered steps provides a clear sequence, and the safety section mentions rollback plans and approval requirements. However, there are no explicit validation checkpoints between phases—no 'stop and verify before proceeding' gates. For a workflow involving production load testing and infrastructure changes, the lack of feedback loops and go/no-go decision points is a significant gap.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to external files and no bundle files to support it. All 13 steps with their full prompt templates are inlined, making the document extremely long. Content like configuration options, success criteria, and individual phase details could be split into separate reference files.	1 / 3
	Total	6 / 12 Passed

Description

67%Scale 1-3

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 has good structural completeness with both a 'what' and 'when' clause, but it relies on broad category terms rather than specific concrete actions. The trigger terms cover the general domain but miss many natural phrases users would employ when experiencing performance issues. It would benefit from more specific actions and richer trigger vocabulary.

Suggestions

Add specific concrete actions such as 'analyze flame graphs, set up distributed tracing, optimize database queries, reduce bundle size, configure caching strategies' to replace the broad categories.

Expand trigger terms to include natural user language like 'slow,' 'latency,' 'bottleneck,' 'load time,' 'memory leak,' 'CPU usage,' 'response time,' or 'page speed.'

Dimension	Reasoning	Score
Specificity	Names the domain (performance optimization) and mentions some areas like 'profiling, observability, and backend/frontend tuning,' but these are broad categories rather than concrete specific actions like 'run flame graphs,' 'set up distributed tracing,' or 'optimize database queries.'	2 / 3
Completeness	Clearly answers both 'what' (optimize end-to-end application performance with profiling, observability, and backend/frontend tuning) and 'when' (Use when coordinating performance optimization across the stack) with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'performance,' 'profiling,' 'observability,' and 'tuning,' but misses many natural user terms such as 'slow,' 'latency,' 'bottleneck,' 'load time,' 'memory leak,' 'CPU usage,' 'caching,' 'APM,' or 'metrics.'	2 / 3
Distinctiveness Conflict Risk	The scope is somewhat specific to cross-stack performance optimization, but terms like 'profiling,' 'observability,' and 'tuning' are broad enough to overlap with more focused skills for backend optimization, frontend optimization, or monitoring/observability individually.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: popey/claude-code-skills
Path: skills/application-performance-performance-optimization/SKILL.md
Commit: a5a6601

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.