front-end-skill
Brief description of what this Skill does and when to use it (project)
50
25%
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 an unfilled template placeholder, not an actual skill description. It provides zero information about what the skill does, when to use it, or any distinguishing characteristics. It would be completely useless for skill selection among any set of available skills.
Suggestions
Replace the placeholder text with a concrete description of what the skill does, listing specific actions (e.g., 'Generates project scaffolding, creates directory structures, initializes configuration files').
Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.
Specify the domain or niche clearly to distinguish this skill from others (e.g., mention specific file types, technologies, or workflows).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | This is a placeholder/template text with no concrete actions described whatsoever. It says nothing about what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. This is literally a template placeholder that was never filled in. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords a user would say. The only potentially relevant word is 'project', which is extremely generic and not a meaningful trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | Completely generic with no distinguishing characteristics. The word 'project' could conflict with virtually any skill. There is nothing to differentiate this from any other skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides useful project-specific design guidance and aesthetic direction that Claude wouldn't inherently know, particularly the 'avoid AI slop' patterns and font recommendations. However, it lacks executable code examples (e.g., a sample component demonstrating the patterns), validation steps in the workflow, and could benefit from splitting detailed style guidance into a referenced file. The content reads more like a design brief than an actionable implementation skill.
Suggestions
Add 1-2 executable code examples showing a component that follows the guidelines (e.g., loading fonts via next/font/google, a framer-motion animation pattern, or a component using the project's CSS variables)
Add validation/verification steps to the implementation checklist, such as 'Run dev server and visually verify on mobile viewport' or 'Check accessibility with browser devtools'
Extract the detailed aesthetic guidelines (typography, color, motion, backgrounds) into a separate STYLE_GUIDE.md and reference it from the main skill to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elaboration. The 'Avoid AI Slop' section and font listing are useful project-specific context, but some phrasing could be tightened (e.g., 'Typography signals quality instantly' is filler). The aesthetic guidelines are somewhat verbose for what could be a more concise style guide. | 2 / 3 |
Actionability | The skill provides concrete guidance on font choices, color approaches, and component locations, but lacks executable code examples. There are no code snippets showing how to load fonts via next/font/google, how to set up framer-motion animations, or how to structure a component following these patterns. The checklist is helpful but abstract. | 2 / 3 |
Workflow Clarity | The implementation checklist provides a reasonable sequence of steps, but lacks validation checkpoints. There's no guidance on how to verify the component works correctly, no testing steps, and no feedback loop for catching issues. For a skill involving UI development, a 'preview and verify' step would strengthen the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's somewhat monolithic — the aesthetic guidelines, typography details, and color/motion guidance could be split into a separate STYLE_GUIDE.md reference. The directory tree is helpful, but there are no references to external files for deeper details. | 2 / 3 |
Total | 8 / 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.
- Repository
- NeverSight/skills_feed
- Commit
9f4534c
- 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.