front-end-skill

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

1.09x

Quality

—

Does it follow best practices?

Impact

91%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, lean instruction skill with concrete aesthetic and technical guidance. Its main weakness is the workflow, which is a flat checklist without validation checkpoints for the component-creation process.

Suggestions

Convert the Implementation Checklist into a sequenced workflow with an explicit verification step, e.g. confirm the component renders and NFC interactions feel instant before finishing.

Add one short copy-paste example showing the recommended font/color setup so the aesthetic guidance is immediately executable.

Tighten the few directive sentences (e.g. "Typography signals quality instantly", "Generic AI-generated designs are immediately recognizable") that explain rationale Claude can infer.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude knows the stack — it never explains what React, Tailwind, or Next.js are, and every line is directive guidance rather than concept padding.	3 / 3
Actionability	Concrete, specific choices are given throughout: named fonts (JetBrains Mono, Playfair Display), weight extremes (100/200 vs 800/900), size jumps of 3x, `next/font/google`, `framer-motion` as `motion`, and the `~~/*` path alias — actionable without code examples, which the rubric permits for instruction-only skills.	3 / 3
Workflow Clarity	The numbered Implementation Checklist provides a clear sequence, but it has no validation checkpoints or feedback loops; it reads as a checklist rather than a verified workflow.	2 / 3
Progressive Disclosure	No bundle files exist and none are needed; content is organized into clear, well-signaled sections (When to Use, Aesthetic Guidelines, Technical Stack, Component Locations) with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an unfilled template placeholder that fails to convey the skill's purpose or trigger conditions. It scores the minimum on every dimension because no substantive information is present.

Suggestions

Replace the placeholder with concrete actions, e.g. "Build and style Next.js React components with Tailwind and Framer Motion in packages/nextjs/."

Add an explicit 'Use when...' trigger clause naming terms users would naturally say: "Use when working on the SplitHub frontend, creating components, pages, or styling."

Include natural keyword variations (frontend, React components, Tailwind, Next.js) so the skill surfaces on real requests.

Dimension	Reasoning	Score
Specificity	The description is a placeholder — "Brief description of what this Skill does and when to use it (project)" — naming no concrete actions, just a meta-instruction to fill it in.	1 / 3
Completeness	Neither what the skill does nor when to use it is stated; the text literally describes itself as a description-to-be-written rather than answering either question.	1 / 3
Trigger Term Quality	It contains no natural keywords a user would say; "(project)" is a template tag and the rest is boilerplate rather than terms like "frontend", "React", or "Next.js".	1 / 3
Distinctiveness Conflict Risk	The placeholder is maximally generic and would overlap with every other skill, giving Claude nothing to distinguish it by.	1 / 3
	Total	4 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: 26d37ce

Reviewed: 4 days 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.