cc-skill-frontend-patterns

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cc-skill-frontend-patterns/SKILL.md

Quality

Content

57%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 SKILL.md is a lean pointer skill with excellent progressive disclosure to a real, well-organized reference file, but the body itself contains no executable guidance or validation checkpoints and includes a generic filler "When to Use" line. Actionability and workflow clarity are limited because everything actionable lives in the reference rather than the body.

Suggestions

Add a brief inline quick-start snippet or 2-3 concrete commands/examples in the body so it is actionable without forcing a full reference load.

Replace the circular "When to Use" filler with concrete triggering conditions and a short sequenced workflow with an explicit validation checkpoint.

Trim the generic "applicable to execute the workflow or actions described in the overview" sentence to tighten conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and delegates detail to the reference with no concept over-explanation, but the "When to Use" line ("applicable to execute the workflow or actions described in the overview") is generic filler, matching anchor 4 rather than 5.	4 / 5
Actionability	The body provides no inline code or concrete steps, only a directive to "Read [the detailed guide]" with abstract guidance to treat safety/validation as mandatory, matching anchor 2 (minimal concrete guidance, relies on reference); not 1 because it points to a specific executable file, not 3 because no executable steps appear in-body.	2 / 5
Workflow Clarity	Only a minimal read-then-apply sequence exists with no explicit validation checkpoints specified in the body (validation is merely referenced as "mandatory"), matching anchor 3; not 4 because no concrete checkpoint steps are written and not 2 because the sequence is coherent.	3 / 5
Progressive Disclosure	The body is a clear overview with one well-signaled one-level-deep reference (references/detailed-guide.md, verified present, 633 lines, 8 organized sections), matching anchor 5; not 4 because the split is clean and navigation is easy.	5 / 5
	Total	14 / 20 Passed

Description

61%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 description clearly names the frontend domain and several relevant subdomains with good trigger keywords, but it omits any concrete actions and lacks a "Use when..." trigger clause, capping completeness at 3. It is mostly distinct from other skills though "UI best practices" invites minor overlap.

Suggestions

Add an explicit "Use when..." trigger clause naming concrete user requests (e.g., "Use when building React/Next.js components, managing state, or optimizing render performance").

Replace the topic catalog with concrete actions (e.g., "Build, refactor, and optimize React/Next.js components") to lift specificity above 3.

Tighten "UI best practices" to a more specific phrase to reduce overlap with general web/CSS skills.

Dimension	Reasoning	Score
Specificity	Quotes "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices." list five concrete subdomains but no verbs/actions, matching anchor 3 (names domain plus partial coverage) rather than 2 (more than minimal) or 4 (no explicit actions).	3 / 5
Completeness	A clear "what" is present but "when" is entirely missing with no "Use when..." clause, matching anchor 3 and capped at 3 per the missing-trigger guideline; not 4 (no explicit when) and not 2 (the what is clear).	3 / 5
Trigger Term Quality	Natural keywords users say are present ("React", "Next.js", "state management", "performance optimization") with good coverage; not 5 because common variations like "components", "hooks", or "frontend" are missing, and not 3 because coverage is strong.	4 / 5
Distinctiveness Conflict Risk	The React/Next.js frontend niche is mostly distinct with minor overlap risk from the broad "UI best practices" phrase, matching anchor 4; not 5 due to that breadth and not 3 because it is clearly more specific than generic document skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/cc-skill-frontend-patterns/SKILL.md
Commit: b1aebac

Reviewed: ~18 hours 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.