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.
35
3%
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
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 extremely weak, functioning as little more than a category label with no actionable detail. It lacks concrete capabilities, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from a generic frontend skill in a large skill library.
Suggestions
Add specific concrete actions such as 'Configures dynamic imports, sets up React.lazy and Suspense boundaries, optimizes webpack/Vite chunk splitting, and analyzes bundle sizes for performance improvements.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about lazy loading, dynamic imports, bundle optimization, chunk splitting, reducing bundle size, React.lazy, or route-based code splitting.'
Remove the duplicate trigger term ('code splitting helper' is listed twice) and replace with diverse natural language variations users would actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('code splitting') but describes no concrete actions. There are no specific capabilities listed such as 'configures lazy loading', 'splits bundles', or 'analyzes chunk sizes'. It is essentially just a label. | 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 trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'code splitting helper' repeated twice. It lacks natural variations users would say like 'lazy loading', 'dynamic import', 'bundle splitting', 'chunk optimization', 'React.lazy', or 'webpack chunks'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'code splitting' is somewhat specific to a frontend optimization technique, which gives it some distinctiveness. However, without concrete actions or clear triggers, it could overlap with general frontend performance or bundling 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 template with no actual content about code splitting. It contains only generic boilerplate text that repeats the skill name without providing any actionable guidance, code examples, or technical information. It would be entirely useless to Claude in performing any code splitting task.
Suggestions
Add concrete, executable code examples for code splitting techniques (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 actual step-by-step workflows for common code splitting scenarios, including validation steps like checking bundle sizes.
Include framework-specific guidance (React, Vue) with copy-paste ready examples and link to separate files for advanced topics like prefetching, error boundaries for lazy components, and SSR considerations.
Remove all meta-description text ('This skill provides automated assistance...') and replace with direct, actionable instructions that assume Claude's existing knowledge of JavaScript and bundlers.
| 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 whatsoever—no code examples, no commands, no specific techniques for code splitting. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 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, uninformative page with no references to detailed materials, no links to examples or advanced guides, and no meaningful structure beyond generic placeholder headings. | 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
3e83543
- 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.