CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-best-practices

React best practices e frameworks modernos

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend/react/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 an efficient, code-first conventions sheet with well-organized sections and concrete, near-executable examples for both Next.js and Vite setups. Its main gaps are small: a few incomplete code details (missing imports, undefined helper functions), a redundant intro line and checklist, and no explicit guidance on how to apply the conventions to an existing project.

Suggestions

Make snippets fully self-contained: add the missing `useEffect` import in useUser, type `useState<User | null>(null)`, and note that getUser/fetchUser are placeholders to be replaced by the project's data layer.

Trim the redundant intro sentence and either expand the checklist into concrete verification items (e.g. 'TypeScript strict mode on', 'no default-export pages outside pages/') or remove it.

Add one short 'Como aplicar' section sequencing the guidance (choose framework → scaffold structure → type components → extract hooks) to make application order explicit.

DimensionReasoningScore

Conciseness

The body is lean and mostly code, assuming Claude's knowledge of React basics — no padding explaining what React or SSR is. Minor trimmable elements remain: the intro line 'Convenções para React com frameworks modernos.' restates the description, and the closing checklist largely repeats the section headings. Fits anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed'); not 5 because of that small redundancy, not 3 because there is no real over-explanation.

4 / 5

Actionability

Concrete TypeScript/TSX snippets cover the common cases (Next.js page with getServerSideProps, Vite App, typed component, custom hook) and are close to copy-paste ready. Minor gaps keep it from 5: the useUser hook omits the useEffect import, getUser/fetchUser are undefined, and useState(null) lacks a type. Not 3 because the code is real and executable, not pseudocode.

4 / 5

Workflow Clarity

This is a conventions/reference skill, not a multi-step pipeline, so no validation checkpoints are required. Decision guidance is present ('Para projetos que precisam de SEO, SSR ou roteamento' → Next.js; SPA → Vite) and a checklist closes the doc, but applying the conventions to a real project is left implicit. Fits anchor 4; not 5 because there is no explicit sequence for when/how to apply each section.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body references no external files, so the skill is a single well-organized file with clear section headers — nothing that clearly belongs in a separate file is inlined. Fits anchor 4 ('Good structure; most content is appropriately placed'); not 5 because the body exceeds the under-50-lines simple-skill case and offers no navigation/signposting beyond flat headings.

4 / 5

Total

16

/

20

Passed

Description

36%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 is a bare domain label rather than a capability statement: it names React and modern frameworks but gives no concrete actions, no 'when to use' guidance, and few natural trigger phrases. It would rarely be selected over more explicitly described React-related skills.

Suggestions

State concrete capabilities in the description, e.g. 'Aplica convenções de React: escolha entre Next.js (SSR/SSG) e Vite (SPA), estrutura de projeto, componentes TypeScript e hooks customizados.'

Add an explicit trigger clause: 'Use quando criar ou estruturar projetos React, Next.js, Vite ou componentes TypeScript/JSX.'

Include natural synonyms and file/framework names users actually say (Next.js, Vite, componente, hook, .tsx) to improve trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

The description 'React best practices e frameworks modernos' names the domain (React, modern frameworks) but lists no concrete actions at all — it says nothing about what the skill actually does (conventions, project structure, hooks, framework selection). Matches anchor 2 ('Names the domain but actions are minimal or generic'); not 3 because no concrete action is stated, not 1 because the domain is clearly identified.

2 / 5

Completeness

The 'what' is vague ('best practices' with no enumerated capabilities) and there is no 'Use when...' clause or any 'when' guidance in the description. This matches anchor 2 ('Has a vague what and no when'); not 3 because the what is not clear, and the missing explicit trigger guidance caps completeness at 3 anyway.

2 / 5

Trigger Term Quality

'React' is a natural term users would say, and 'frameworks modernos' gestures at Next.js/Vite, but common variations users actually mention (Next.js, Vite, component, hook, TypeScript) are absent from the description text. Fits anchor 3 ('Some relevant keywords but missing common variations or synonyms'); not 4 because most natural trigger phrases are missing.

3 / 5

Distinctiveness Conflict Risk

'React best practices' is somewhat specific (distinct from non-React skills) but 'best practices' plus 'frameworks modernos' would overlap with any general React/TypeScript/web-development skill. Fits anchor 3 ('Somewhat specific but could still overlap with similar skills'); not 4 because nothing in the description carves out a distinct niche or concrete trigger set.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/frontend/react/SKILL.md

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.