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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill bundle-size-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The repeated trigger term and boilerplate category text provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes JavaScript bundle sizes, identifies large dependencies, suggests code splitting strategies, and generates size reports'
Include a 'Use when...' clause with natural trigger terms like 'webpack bundle too large', 'reduce package size', 'analyze dependencies', 'tree shaking', 'code splitting'
Add file types and tool names users might mention: '.js bundles', 'webpack', 'rollup', 'vite', '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, measuring, optimizing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 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, build tools, or performance optimization skills. The category mention helps slightly but doesn't provide clear boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about bundle size analysis. It contains only meta-descriptions of what a skill should do without any concrete guidance on tools (webpack-bundle-analyzer, source-map-explorer), techniques, or workflows for analyzing JavaScript bundle sizes.
Suggestions
Add concrete code examples showing how to set up and use bundle analysis tools like webpack-bundle-analyzer or source-map-explorer
Include a clear workflow: 1) Generate bundle stats, 2) Analyze output, 3) Identify large dependencies, 4) Apply optimization strategies
Provide specific commands for common bundlers (webpack, vite, rollup) to generate analyzable output
Add examples of interpreting bundle analysis results and actionable optimization patterns (code splitting, tree shaking, lazy loading)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | No executable code, commands, or specific instructions are 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 is 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 generic headings. No references to detailed documentation, no examples, and no navigation to related resources that would actually help with bundle size analysis. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.