image-optimization-helper
Image Optimization Helper - Auto-activating skill for Frontend Development. Triggers on: image optimization helper, image optimization helper Part of the Frontend Development skill category.
32
0%
Does it follow best practices?
Impact
92%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/image-optimization-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a template placeholder with no substantive content. It lacks any concrete actions, natural trigger terms, explicit usage guidance, or distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Compresses images, converts to modern formats (WebP, AVIF), implements lazy loading, generates responsive image srcsets, and optimizes image delivery for web performance.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about image compression, reducing page load time due to images, converting image formats, lazy loading images, responsive images, or optimizing assets for the web.'
Remove the duplicate trigger term and replace with diverse natural keywords users would actually say, such as 'compress images', 'image size', 'WebP', 'lazy load', 'srcset', 'image performance', '.png', '.jpg'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Image Optimization Helper') and mentions 'Frontend Development' as a category, but never describes what it actually does—no mention of compressing images, converting formats, lazy loading, responsive images, or any other specific capability. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. The phrase 'Auto-activating skill' is vague and does not substitute for clear usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'image optimization helper' repeated twice, which is not a natural phrase users would say. Users would more likely say things like 'compress images', 'reduce image size', 'lazy loading', 'WebP', 'responsive images', or 'image performance'. No natural keyword variations are provided. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Frontend Development' category and 'image optimization' title could overlap with many other frontend, performance, or image-related skills. Without specific actions or distinct triggers, it would be very difficult to distinguish this from other skills. | 1 / 3 |
Total | 4 / 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 an empty template/placeholder with no substantive content. It contains no actionable guidance on image optimization — no mention of formats (WebP, AVIF), responsive images, lazy loading, compression tools, CDN strategies, or any concrete techniques. Every section restates the skill name without teaching anything.
Suggestions
Replace the boilerplate with concrete, executable guidance: include specific image optimization techniques like format selection (WebP/AVIF), responsive image markup (<picture>, srcset), lazy loading attributes, and compression tool commands (e.g., sharp, imagemin).
Add copy-paste ready code examples for common scenarios: Next.js Image component usage, CSS background-image optimization, build-time optimization with webpack/vite plugins.
Define a clear workflow for optimizing images in a project: audit existing images → choose target formats → implement responsive markup → validate with Lighthouse → verify output sizes.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that just restate the skill name, and replace with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'image optimization helper' excessively, and provides zero domain-specific information about actual image optimization techniques. | 1 / 3 |
Actionability | There are no concrete code examples, commands, tools, configurations, or specific techniques. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined at all. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external resources, and the content itself is a shallow placeholder with no meaningful structure or navigation to deeper content. | 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
13d35b8
- 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.