CtrlK
BlogDocsLog inGet started
Tessl Logo

front-end-skill

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

58

1.09x
Quality

37%

Does it follow best practices?

Impact

91%

1.09x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xgeorgemathew/splithub/front-end-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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 lean, well-structured, opinionated frontend guide with concrete stack specifics and a sequenced checklist, consistently landing just above midpoint on every dimension. Its main gap is the absence of executable code examples and an explicit build-verification step.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it does not explain what Next.js or Tailwind is — with only minor prose flourishes ("Typography signals quality instantly", "surprise and delight") that could be trimmed.

4 / 5

Actionability

Concrete specifics abound (Next.js 15 App Router, framer-motion as `motion`, `next/font/google`, path alias `~~/*`, named fonts, a component-location tree), but no copy-paste code snippets for common tasks like font loading or CSS-variable setup leave minor gaps.

4 / 5

Workflow Clarity

The Implementation Checklist gives a clear 7-step sequence with a final verification step ("Test NFC-related flows"), though it lacks an explicit build/typecheck checkpoint; this is a creative task so the destructive-validation cap does not apply.

4 / 5

Progressive Disclosure

Single self-contained file with well-signaled sections and no nested references; the font/color/motion guidance is reasonably inline rather than buried, with only minor organization gaps that a separate reference file could absorb.

4 / 5

Total

16

/

20

Passed

Description

0%Weight 40%Scale 1-5

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 frontmatter description was never filled in and remains a template placeholder, so it provides zero information about the skill's purpose or triggers. Every dimension scores the floor because nothing concrete is stated.

Suggestions

Replace the placeholder with a concrete statement of what the skill does, e.g. "Builds and styles Next.js frontend components for the SplitHub tap-to-pay app."

Add an explicit 'Use when...' trigger clause naming natural phrases like "frontend", "React components", "Tailwind styling", or "UI/UX" work in packages/nextjs/.

Use third-person voice and include concrete triggers (component creation, animations, page layouts) to lift completeness and distinctiveness above the floor.

DimensionReasoningScore

Specificity

The description is a template placeholder ("Brief description of what this Skill does and when to use it") with no concrete actions or domain named, matching the entirely-vague anchor.

1 / 5

Completeness

It answers neither "what does this do" nor "when to use it" — it merely instructs the author to fill those in, fitting the missing-both anchor.

1 / 5

Trigger Term Quality

No natural keywords appear at all; the text is meta-instructional filler rather than terms a user would say, so it cannot match any anchor above 1.

1 / 5

Distinctiveness Conflict Risk

The placeholder is entirely generic and would conflict with virtually any skill, as it carries no distinguishing signal.

1 / 5

Total

4

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.