bundle-size-analyzer
Bundle Size Analyzer - Auto-activating skill for Frontend Development. Triggers on: bundle size analyzer, bundle size analyzer Part of the Frontend Development skill category.
36
3%
Does it follow best practices?
Impact
99%
0.99xAverage 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/bundle-size-analyzer/SKILL.mdQuality
Discovery
7%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 fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes JavaScript bundle sizes, identifies large dependencies, visualizes module composition, and suggests code-splitting or tree-shaking optimizations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about reducing bundle size, analyzing webpack output, finding large dependencies, optimizing JavaScript bundles, or mentions tools like webpack-bundle-analyzer.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'bundle too large', 'reduce JS size', 'chunk optimization', 'dependency size', '.js bundle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bundle Size Analyzer') without describing any concrete actions. There are no specific capabilities listed such as analyzing webpack bundles, identifying large dependencies, generating treemaps, or suggesting optimizations. | 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 with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'bundle size analyzer' repeated twice. It misses natural user phrases like 'reduce bundle size', 'webpack analysis', 'large dependencies', 'code splitting', 'tree shaking', or 'JavaScript bundle'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'bundle size' is somewhat specific to a niche (JavaScript/frontend bundle analysis), which provides some distinctiveness. However, the vague 'Frontend Development' category and lack of concrete actions could cause overlap with other frontend-related skills. | 2 / 3 |
Total | 5 / 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 shell with no substantive content. It contains only generic boilerplate descriptions of what a bundle size analyzer skill might do, without any actual technical guidance, code examples, tool recommendations, or workflows. It provides zero value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable examples using specific tools like webpack-bundle-analyzer, source-map-explorer, or bundlephobia (e.g., `npx webpack-bundle-analyzer stats.json` with setup instructions for generating stats).
Define a clear workflow: 1) Generate bundle stats, 2) Analyze with a specific tool, 3) Identify large dependencies, 4) Apply optimization strategies (code splitting, tree shaking, lazy loading), 5) Verify size reduction.
Include actionable optimization patterns with code examples, such as dynamic imports (`React.lazy`), replacing heavy libraries (e.g., moment.js → date-fns), and configuring webpack splitChunks.
Remove all generic meta-content ('This skill activates automatically when...', 'Provides step-by-step guidance') and replace with actual technical instructions 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, provides no specific technical content about bundle size analysis, and wastes tokens on generic meta-descriptions like 'Provides step-by-step guidance' without any actual guidance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete steps, no tool names (e.g., webpack-bundle-analyzer, source-map-explorer), no configuration examples. Every section describes what the skill could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured sections with real content, and no navigation to deeper material. There are no bundle files to reference either, but the body itself lacks any meaningful organization. | 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.