react-nextjs-development

React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.

Quality

29%

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/react-nextjs-development/SKILL.md

Quality

Content

23%Scale 1-5

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

This skill is essentially a project management outline that delegates all actual implementation knowledge to external skills that are not provided. It contains no executable code, no concrete configuration examples, and no specific technical guidance—just high-level phase descriptions and vague action items. While the sequential structure is reasonable, the complete lack of actionable content makes this skill nearly useless as a standalone reference.

Suggestions

Replace vague action items with concrete, executable code examples—e.g., show actual Next.js 14 App Router file structure, a sample Server Component, or a TypeScript config snippet.

Add at least one complete, copy-paste-ready example for the most common use case (e.g., scaffolding a Next.js 14 app with App Router and TypeScript).

Include validation commands between phases, such as 'npx tsc --noEmit' after TypeScript setup or 'npm run build' before deployment, with error recovery guidance.

Either provide the referenced skill files in the bundle or inline the critical patterns from those skills; currently all substance is deferred to unverifiable external references.

Dimension	Reasoning	Score
Conciseness	Heavily padded with repetitive structure across 8 phases that each follow the same template. The 'When to Use This Workflow' section explains obvious triggers Claude would already know. The 'Copy-Paste Prompts' sections are not actionable code but rather meta-instructions to invoke other skills, adding bulk without substance.	2 / 5
Actionability	Contains zero executable code, no concrete commands, no specific configuration examples. Every 'action' is a vague directive like 'Set up Tailwind CSS' or 'Configure TypeScript.' The copy-paste prompts are meta-references to other skills rather than actual implementation guidance. Claude gains no concrete knowledge about how to do anything from this skill.	1 / 5
Workflow Clarity	The 8 phases provide a clear sequence for building a React/Next.js app, and the quality gates checklist at the end is a useful validation checkpoint. However, there are no validation steps between phases, no error recovery guidance, and the steps within each phase are too vague to be actionable (e.g., 'Configure TypeScript' with no specifics).	3 / 5
Progressive Disclosure	References many external skills (app-builder, nextjs-app-router-patterns, etc.) but none of these are provided in the bundle, making it impossible to verify they exist or contain useful content. The skill itself is a monolithic document that could benefit from splitting phases into separate files, but instead inlines everything while deferring all actual content to unverifiable external references.	2 / 5
	Total	8 / 20 Passed

Description

36%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 is essentially a technology stack listing rather than a functional skill description. It names relevant technologies that serve as decent trigger terms but fails to describe concrete actions the skill enables and completely lacks 'when to use' guidance. Adding specific capabilities and explicit trigger conditions would significantly improve its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when building React or Next.js applications, creating components, setting up routing, or working with .tsx files'.

Replace the vague 'application development' with concrete actions such as 'Creates page routes, builds React Server Components, configures layouts, sets up API routes, and implements client-side interactivity'.

Include common synonyms and variations users might say, such as 'web app', 'frontend', 'SSR', 'server-side rendering', '.tsx files', or 'component library'.

Dimension	Reasoning	Score
Specificity	Names the domain (React/Next.js development) and lists technologies (App Router, Server Components, TypeScript, Tailwind CSS), but describes no concrete actions. 'Application development' and 'modern frontend patterns' are vague. No specific actions like 'creates components', 'configures routing', or 'sets up API routes' are mentioned.	2 / 5
Completeness	Has a vague 'what' (application development with listed technologies) but completely lacks a 'when' clause. There is no 'Use when...' guidance, which per the rubric should cap completeness at 3, and the 'what' itself is not clearly articulated beyond listing technologies, placing this at a 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'React', 'Next.js 14+', 'App Router', 'Server Components', 'TypeScript', 'Tailwind CSS' that users would naturally mention. However, it misses common variations and synonyms like 'frontend', 'web app', 'SSR', 'server-side rendering', 'RSC', '.tsx', or 'component'.	3 / 5
Distinctiveness Conflict Risk	The combination of React, Next.js 14+, and App Router provides some specificity, but 'application development' is broad enough to overlap with general web development skills, generic React skills, or TypeScript/Tailwind skills. The lack of concrete actions makes it harder to distinguish from related frontend skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/react-nextjs-development/SKILL.md
Commit: 57c135b

Reviewed: 2 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.