code-splitting-helper
Code Splitting Helper - Auto-activating skill for Frontend Development. Triggers on: code splitting helper, code splitting helper Part of the Frontend Development skill category.
33
0%
Does it follow best practices?
Impact
94%
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/code-splitting-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 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 it. It would be nearly impossible for Claude to reliably choose this skill from a pool of similar frontend-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements route-based code splitting, configures dynamic imports with React.lazy and Suspense, analyzes bundle sizes, and sets up webpack chunk optimization.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about lazy loading, dynamic imports, bundle splitting, reducing bundle size, React.lazy, Suspense boundaries, or webpack code splitting.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually say, such as 'lazy load', 'chunk', 'bundle optimization', 'split bundles', 'dynamic import'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('code splitting') but provides no concrete actions. It doesn't describe what the skill actually does—no mention of lazy loading, dynamic imports, bundle analysis, route-based splitting, or any other specific capability. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'Use when...' clause or equivalent guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'code splitting helper' repeated twice. It misses natural user terms like 'lazy loading', 'dynamic import', 'bundle size', 'React.lazy', 'webpack chunks', 'route splitting', or 'performance optimization'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any frontend performance, bundling, or webpack-related skill. 'Frontend Development skill category' is extremely broad and provides no distinct niche. | 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 with no substantive content about code splitting. It contains only generic boilerplate descriptions that repeat the skill name without providing any actual guidance, code examples, or technical information. It fails on every dimension as it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable code examples for code splitting patterns (e.g., React.lazy(), dynamic import(), route-based splitting with React Router, webpack chunk configuration).
Replace the generic 'Capabilities' and 'When to Use' boilerplate with an actionable workflow: identify splitting candidates → implement lazy loading → verify bundle sizes → handle loading/error states.
Include specific framework examples with before/after code showing how to split a monolithic bundle, including validation steps like checking bundle analyzer output.
Remove all meta-description content ('This skill provides automated assistance...') and replace with lean, technical reference material that adds value beyond Claude's existing knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'code splitting helper' excessively, and provides zero actual technical content about code splitting. | 1 / 3 |
Actionability | There is no concrete guidance, no code examples, no commands, and no specific instructions. The skill describes what it could do in abstract terms without actually providing any actionable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' as a capability but never provides any steps. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed materials, no structured navigation, and no meaningful organization of content across sections. | 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
3076d78
- 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.