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".
51
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/performance/performance-optimization-advisor/skills/providing-performance-optimization-advice/SKILL.mdQuality
Discovery
82%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 strong completeness with explicit 'Use when' and trigger phrases, and good trigger term quality. However, it lacks specificity in the concrete actions it performs — 'recommendations' is vague compared to listing specific optimization techniques. The broad scope across frontend, backend, and infrastructure, while comprehensive, slightly increases overlap risk with more targeted skills.
Suggestions
Replace vague 'recommendations' with specific concrete actions, e.g., 'Identifies slow database queries, reduces JavaScript bundle size, recommends caching strategies, and suggests infrastructure scaling approaches'.
Consider narrowing scope or adding distinguishing details to reduce potential overlap with frontend-specific or backend-specific optimization skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (performance optimization) and mentions frontend, backend, and infrastructure, but the actions are vague — 'recommendations' and 'analyzing bottlenecks' are abstract rather than concrete specific actions like 'profile database queries, reduce bundle size, configure CDN 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...'), with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'optimize performance', 'improve speed', 'performance recommendations'. These are realistic phrases a user would type. Also includes 'bottlenecks' and 'improvement strategies' as additional natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | While 'performance optimization' is a recognizable niche, the broad scope covering frontend, backend, and infrastructure could overlap with more specific skills targeting any of those individual areas. The description is somewhat specific but the breadth increases conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely descriptive and abstract, reading more like a product marketing document than actionable instructions for Claude. It lacks any concrete code examples, specific tools or commands, optimization patterns, or measurable techniques. The content is heavily padded with sections explaining concepts Claude already understands and references a nonexistent 'plugin' system.
Suggestions
Replace the abstract 'How It Works' and 'Examples' sections with concrete optimization patterns: specific code snippets for common fixes (e.g., lazy loading images, adding database indexes, implementing caching headers), specific profiling commands to run, and a template for the output report.
Remove the 'Overview', 'When to Use This Skill', 'Best Practices', and 'Integration' sections entirely—these explain things Claude already knows and waste tokens.
Add a concrete output template/schema showing exactly what the optimization report should look like, with example entries including specific impact estimates and effort ratings.
Include validation steps in the workflow, such as 'Run lighthouse audit before and after to measure improvement' or 'Verify query execution plans with EXPLAIN ANALYZE' to add checkpoints and feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections explaining things Claude already knows (what performance optimization is, when to use it, how it works at a high level). The 'Overview', 'How It Works', 'When to Use This Skill', 'Best Practices', and 'Integration' sections are all padding that consume tokens without adding actionable value. References to a nonexistent 'plugin' add confusion. | 1 / 3 |
Actionability | No concrete code examples, commands, specific tools, or executable guidance anywhere. The instructions are entirely abstract ('Analyze frontend code for rendering and asset optimization'). The examples describe what the skill 'will do' in vague terms rather than providing concrete optimization patterns, code snippets, or specific techniques Claude should apply. | 1 / 3 |
Workflow Clarity | The 'Instructions' section lists 6 high-level steps with no specifics on how to perform any of them, no validation checkpoints, and no feedback loops. For a skill involving analysis of codebases and generating optimization recommendations, there are no concrete analysis steps, no tools to run, and no verification that recommendations are valid. | 1 / 3 |
Progressive Disclosure | All content is in a single monolithic file with no references to supporting files. The 'Resources' section lists generic topic areas without links. There are no bundle files, yet the content is long and repetitive rather than being organized into a concise overview with detailed references split out. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.