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.
34
0%
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
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 repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among multiple frontend-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes JavaScript bundle sizes, identifies large dependencies, recommends code splitting strategies, and visualizes chunk composition.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about bundle size, webpack analysis, large bundles, code splitting, tree shaking, chunk optimization, or reducing JavaScript payload size.'
Include relevant file types and tool names as trigger terms, such as '.js bundles', 'webpack', 'rollup', 'vite', 'esbuild', 'source map explorer', or 'bundle-analyzer'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Frontend Development') and the skill name ('Bundle Size Analyzer') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'analyze', 'report', 'optimize', 'identify large dependencies', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'bundle size analyzer' repeated twice. It misses natural variations users would say such as 'webpack bundle', 'chunk size', 'tree shaking', 'reduce bundle', 'large dependencies', 'code splitting', or 'bundle optimization'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any frontend performance or build tool skill. Without specific actions or distinct triggers, it provides no clear niche to differentiate it from other frontend development 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 shell with no actual instructional content. It consists entirely of boilerplate meta-descriptions that repeat 'bundle size analyzer' without ever explaining what it is, how to do it, or providing any tools, commands, or code. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples using real bundle analysis tools (e.g., webpack-bundle-analyzer, source-map-explorer, bundlephobia) with actual CLI commands and configuration snippets.
Define a clear workflow: e.g., 1) Install analyzer tool, 2) Generate bundle stats, 3) Analyze output, 4) Identify optimization targets, 5) Validate improvements—with specific commands at each step.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable technical content such as code examples, threshold configurations, and CI integration patterns.
Add concrete optimization techniques (tree shaking, code splitting, lazy loading) with before/after examples showing measurable bundle size reductions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'bundle size analyzer' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no tool recommendations, no specific techniques for analyzing bundle size. The content describes rather than instructs, offering nothing executable or actionable. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. Sections like 'Capabilities' and 'Example Triggers' contain no real content. There are no references to detailed materials, examples, or external files. | 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
c8a915c
- 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.