providing-performance-optimization-advice

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

54%

Overall

Validation — 81%

Implementation — 20%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

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

	Total	13 / 16 Passed

Implementation

20%

This skill content is overly verbose and lacks actionable guidance. It describes what the skill does conceptually but fails to provide concrete code examples, specific commands, or executable workflows. The repeated references to a 'plugin' are confusing and the content reads more like marketing copy than technical instructions.

Suggestions

Replace vague instructions with concrete, executable examples - show actual code for analyzing frontend performance (e.g., Lighthouse CLI commands, specific profiling tool usage)

Remove the 'How It Works' and 'When to Use' sections entirely - Claude doesn't need to be told when to use a skill or have the process explained abstractly

Add a concrete output template/schema showing exactly what the optimization report should look like with real example content

Include specific validation steps such as 'Run lighthouse --output=json to verify baseline metrics before and after changes'

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanation of concepts Claude already knows. The 'Overview', 'How It Works', 'When to Use', and 'Best Practices' sections are padded with unnecessary context that doesn't add actionable value. References to a non-existent 'plugin' add confusion.	1 / 3
Actionability	No concrete code, commands, or executable guidance provided. The 'Instructions' section lists vague steps like 'Analyze frontend code' without specifying how. Examples describe what the skill 'will do' rather than showing actual implementation or output formats.	1 / 3
Workflow Clarity	Steps are listed in the Instructions section but lack validation checkpoints or feedback loops. No concrete verification steps for the analysis process, and no clear criteria for when each step is complete or how to handle partial failures.	2 / 3
Progressive Disclosure	Content is organized into sections but is monolithic with no references to external files. The 'Resources' section mentions guides but provides no actual links. Content that could be split (detailed examples, error handling) is all inline.	2 / 3
	Total	6 / 12 Passed

Activation

82%

This description has strong completeness with explicit 'Use when' and 'Trigger with' clauses, and good trigger term coverage. However, it lacks specificity in describing concrete actions (what optimization techniques it actually provides) and its broad scope across all layers creates potential conflict risk with more specialized performance skills.

Suggestions

Add specific concrete actions like 'profile slow queries, analyze bundle sizes, identify memory leaks, recommend caching strategies' to improve specificity

Consider narrowing scope or adding distinguishing details to reduce overlap with potential domain-specific optimization skills (e.g., 'for full-stack applications' or 'cross-cutting concerns')

Dimension	Reasoning	Score
Specificity	Names the domain (performance optimization) and mentions areas (frontend, backend, infrastructure) but uses vague language like 'comprehensive prioritized recommendations' without listing concrete actions like 'profile database queries', 'optimize bundle size', or 'configure caching'.	2 / 3
Completeness	Clearly answers both what ('provide comprehensive prioritized performance optimization recommendations for frontend, backend, and infrastructure') and when ('Use when analyzing bottlenecks or seeking improvement strategies. Trigger with phrases like...'). Has explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes explicit trigger phrases users would naturally say: 'optimize performance', 'improve speed', 'performance recommendations', plus 'bottlenecks' and 'improvement strategies'. Good coverage of natural language variations.	3 / 3
Distinctiveness Conflict Risk	While 'performance optimization' is a clear domain, the broad scope (frontend, backend, infrastructure) could overlap with more specific skills like 'database optimization' or 'frontend bundle optimization'. The triggers are somewhat generic and could conflict with domain-specific performance skills.	2 / 3
	Total	10 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.