front-end-skill

Brief description of what this Skill does and when to use it (project)

1.09x

Quality

25%

Does it follow best practices?

Impact

91%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xgeorgemathew/splithub/front-end-skill/SKILL.md

Quality

Discovery

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 config files').

Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.

Include domain-specific keywords and file types/formats to make the skill clearly distinguishable from others.

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 good project-specific context and aesthetic direction for a financial app frontend, with clear organizational structure and a useful component directory map. However, it lacks executable code examples (no actual component snippets, font loading code, or animation patterns), which limits actionability. The aesthetic guidelines, while distinctive and opinionated, could be more concise and would benefit from concrete before/after code examples rather than descriptive lists.

Suggestions

Add executable code examples: show a sample component with next/font/google loading, a framer-motion animation pattern for NFC tap feedback, and a CSS variable theme setup

Tighten the typography and color sections by removing explanatory text Claude already knows and replacing with concrete code patterns (e.g., a Tailwind config snippet with the recommended fonts)

Add a validation/verification step to the implementation checklist, such as 'Preview on mobile viewport and verify animations render at 60fps'

Consider splitting detailed font pairings and animation recipes into a separate reference file, keeping SKILL.md as a concise overview

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary elaboration, particularly in the 'Avoid AI Slop' section and the extensive font listing. Claude already knows what Inter and Roboto are; the aesthetic philosophy sections could be tightened. However, the project-specific context (SplitHub, NFC interactions) earns its place.	2 / 3
Actionability	Provides concrete guidance on font choices, color approaches, and component locations, but lacks executable code examples. 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. The checklist is helpful but the skill describes rather than demonstrates.	2 / 3
Workflow Clarity	The implementation checklist provides a reasonable sequence for creating components, 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 UI development workflow, explicit 'preview and verify' steps would strengthen this.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, and the directory tree is helpful for navigation. However, all content is inline in one file with no references to separate detailed guides (e.g., animation patterns, color theme setup, or component examples could be split out). For its length (~90 lines of content), some separation would improve scannability.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: f772de4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.