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
Quality
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 placeholder with minimal useful content. It only provides a skill name and category without explaining what the skill does, what specific capabilities it offers, or when Claude should select it. The redundant trigger terms and lack of concrete actions make this description ineffective for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes JavaScript bundle sizes, identifies large dependencies, suggests code splitting opportunities, and generates size reports'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user mentions bundle size, webpack analysis, package bloat, tree shaking, code splitting, or wants to reduce JavaScript payload'
Include relevant file types and tools, e.g., 'webpack-bundle-analyzer, rollup, vite, .js bundles, node_modules size'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bundle Size Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of analyzing, reporting, optimizing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'bundle size analyzer' repeated twice, which is redundant. Missing natural variations users would say like 'webpack bundle', 'package size', 'reduce bundle', 'code splitting', 'tree shaking', or file extensions like '.js bundle'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'bundle size' is somewhat specific to frontend/JavaScript tooling, the lack of detail means it could overlap with general frontend skills or build tools. The category mention 'Frontend Development' is too broad to provide clear distinction. | 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 a template placeholder with no actual content about bundle size analysis. It contains only meta-descriptions of what a skill should do without any concrete information about analyzing bundles, identifying large dependencies, code splitting strategies, or using analysis tools. The content provides zero value to Claude for performing bundle size analysis tasks.
Suggestions
Add concrete code examples for common bundle analyzers (e.g., webpack-bundle-analyzer setup, source-map-explorer commands)
Include specific workflow steps: how to generate bundle stats, interpret results, and identify optimization opportunities
Provide actionable optimization patterns: code splitting, tree shaking verification, identifying duplicate dependencies
Add example output interpretation showing what to look for in bundle analysis reports
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information about bundle size analysis, tools, or techniques. | 1 / 3 |
Actionability | No executable code, commands, or specific guidance provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for analyzing bundle sizes. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate sections. No references to tools (webpack-bundle-analyzer, source-map-explorer), no links to documentation, and no organization of content by complexity or use case. | 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
994edc4
- 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.