Brief description of what this Skill does and when to use it (project)
52
Quality
28%
Does it follow best practices?
Impact
91%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xgeorgemathew/splithub/front-end-skill/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 is unfilled template/placeholder text rather than an actual skill description. It provides zero information about the skill's purpose, capabilities, or appropriate use cases. The description is entirely non-functional for skill selection purposes.
Suggestions
Replace the placeholder text with actual concrete actions the skill performs (e.g., 'Generates reports, analyzes metrics, creates dashboards').
Add an explicit 'Use when...' clause with specific trigger terms users would naturally say when needing this skill.
Include domain-specific keywords and file types/formats to distinguish this skill from others in the skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever - it's a placeholder template text ('Brief description of what this Skill does') rather than an actual description of capabilities. | 1 / 3 |
Completeness | This is placeholder text that answers neither 'what does this do' nor 'when should Claude use it' - it merely references that such information should exist. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. The only term present is 'project' in parentheses, which is too generic to serve as a meaningful trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | Completely generic placeholder text with no distinguishing characteristics; would provide no basis for selecting this skill over any other. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid aesthetic direction and project context for frontend development, with good organization and clear navigation to component locations. However, it leans heavily on conceptual guidance without executable code examples, and the implementation checklist lacks validation steps to ensure quality outcomes.
Suggestions
Add executable code snippets showing font loading with next/font/google and a basic framer-motion animation pattern
Include a concrete example of CSS variable setup for the color theme system
Add validation steps to the checklist (e.g., 'Run on mobile viewport', 'Verify animation performance with React DevTools')
Condense the typography font lists into a shorter 'preferred fonts' reference, moving detailed options to a separate TYPOGRAPHY.md if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elaboration, particularly in the 'Avoid AI Slop' section with extensive font lists and the aesthetic philosophy explanations that Claude could infer from shorter guidance. | 2 / 3 |
Actionability | Provides good conceptual guidance and a checklist, but lacks executable code examples. No concrete snippets showing how to load fonts via next/font/google, implement framer-motion animations, or set up CSS variables despite referencing these patterns. | 2 / 3 |
Workflow Clarity | The implementation checklist provides a sequence but lacks validation checkpoints. No guidance on how to verify typography choices work, test animations, or validate responsive design before considering a component complete. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for a SKILL.md overview, and the component locations section provides clear navigation to relevant code areas without requiring external file references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
5342bca
Table of Contents
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.