providing-performance-optimization-advice

Provide comprehensive prioritized performance optimization recommendations for frontend, backend, and infrastructure. Use when analyzing bottlenecks or seeking improvement strategies. Trigger with phrases like "optimize performance", "improve speed", or "performance recommendations".

Quality

51%

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 ./plugins/performance/performance-optimization-advisor/skills/providing-performance-optimization-advice/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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

The skill body is well-structured into clear sections but is largely conceptual: it describes what to do rather than giving executable guidance, and it ignores its own bundle directories. Actionability is the main weakness, followed by verbosity and lack of progressive disclosure.

Suggestions

Add concrete, executable guidance: example profiling commands, the actual invocation of scripts/performance_profiler.py and impact_estimator.py, and a sample prioritized recommendation entry.

Tighten the prose by collapsing Overview/How It Works/Examples into a lean quick-start with one worked example, removing restated marketing language.

Move detailed material (layer-specific checklists, report templates, example reports) into the existing references/ and assets/ files and link to them from the body so content is split one level deep.

Dimension	Reasoning	Score
Conciseness	The body restates the skill's purpose across Overview, How It Works, and Examples with marketing prose ("empowers Claude", "comprehensive report") that could be trimmed without losing information.	2 / 3
Actionability	The Instructions are vague directives ("Analyze frontend code for rendering and asset optimization") with no executable code, commands, or tool invocations, and the bundled profiler scripts are never referenced or demonstrated.	1 / 3
Workflow Clarity	A six-step sequence is present (analyze frontend, review backend, examine infra, identify, prioritize, generate roadmap) but steps are abstract and lack validation checkpoints or feedback loops.	2 / 3
Progressive Disclosure	Section headers are well-organized, but the body is a single monolithic document that references none of the existing bundle files (references/, scripts/, assets/); content that belongs in references stays inline.	2 / 3
	Total	7 / 12 Passed

Description

67%Weight 40%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 clearly answers both what the skill does and when to use it with explicit triggers, but its action language is somewhat abstract and its trigger coverage lacks common variations. It is a solid, above-average description with room to be more concrete and distinctive.

Suggestions

Replace abstract verbs with concrete actions, e.g. "Profile bottlenecks, estimate impact, and produce a phased optimization roadmap across frontend, backend, and infrastructure".

Broaden trigger terms with natural variations users say: "slow", "latency", "speed up", "response time", "make it faster".

Sharpen distinctiveness by scoping triggers to multi-layer optimization advice so it does not fire for single-layer tasks like database tuning alone.

Dimension	Reasoning	Score
Specificity	Names the domain ("frontend, backend, and infrastructure") and an action ("Provide... recommendations") but does not list multiple concrete actions, and "comprehensive prioritized" reads as mild fluff.	2 / 3
Completeness	Explicitly states what it does ("Provide comprehensive prioritized performance optimization recommendations") and when to use it via an explicit "Use when..." clause plus trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Includes natural phrases ("optimize performance", "improve speed", "performance recommendations") but misses common variations users would say such as "slow", "latency", "speed up", or "response time".	2 / 3
Distinctiveness Conflict Risk	Performance optimization is a recognizable niche, but broad triggers like "improve speed" and "optimize performance" could overlap with layer-specific (database, frontend) optimization skills.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/performance-optimization-advisor/skills/providing-performance-optimization-advice/SKILL.md
Commit: bddba3c

Reviewed: 3 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.