CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-architecture-review

Reviews Next/React boundaries, state ownership, duplicated client state, rendering contracts, and component boundaries. Use during frontend architecture refactoring.

Quality

80%

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 ./.cursor/skills/frontend-architecture-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A tight, actionable review checklist with concrete API-level guidance and a well-organized structure appropriate for a short, bundle-free skill. The main improvements are removing the description-duplicating opening line, fixing the malformed hook names, and adding example patterns or an explicit findings format.

Suggestions

Drop or compress the opening line that restates the frontmatter description, reclaiming tokens without losing information.

Fix the malformed hook references ('use state', 'use effect' should be 'useState', 'useEffect') and add one or two example code smells per checklist item so the reviewer knows exactly what pattern to flag.

Specify the expected output of a review (e.g., findings format for the 'Review record' PR comment) to complete the workflow.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanations of concepts Claude already knows, but the opening line ('Use this skill when reviewing Next.js App Router structures, component boundaries, state management, and React performance') near-duplicates the frontmatter description and could be trimmed. This matches anchor 4 ('efficient; minor instances... that could be trimmed') rather than 5's 'every token earns its place'.

4 / 5

Actionability

Concrete, executable guidance naming exact APIs ('"use client"', 'URLSearchParams and next/navigation controls', 'internal /api/... endpoints') and specific checks ('un-memoized expensive calculations', 'excessive component mount/unmount cycles'). Minor gaps — no example code smells to flag and the oddly spaced '`use state`, `use effect`' muddies the hook names — place it at anchor 4 rather than 5's fully example-covered level.

4 / 5

Workflow Clarity

A clear sequence exists: protocol prerequisites (AGENTS.md, codex review protocol) -> two numbered checklist sections -> post one 'Review record' comment, with an explicit safety constraint ('Do not review opportunistically or mutate files during pure review'). It sits at anchor 4 rather than 5 because there is no explicit output format for findings and no error-recovery guidance; the destructive-operation cap does not apply since this is a read-only review skill.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, and the content is well-organized into clearly signaled sections; its external doc references (AGENTS.md, docs/codex-review-protocol.md, pull-request-workflow.md) are one level deep and clearly labeled. Per the simple-skill guideline this earns a 5; nothing that belongs in a separate file is inlined.

5 / 5

Total

17

/

20

Passed

Description

75%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.

A solid third-person description with specific review targets and an explicit use-when clause. Its main weaknesses are a narrow trigger clause and missing common variations like 'App Router', 'server components', or 'use client' that users would naturally say.

Suggestions

Broaden the trigger clause to concrete phrases users would say, e.g., 'Use when the user mentions Next.js App Router, server vs. client components, React state management, or asks for a frontend architecture refactor.'

Include natural synonyms and specific terms like 'App Router', 'RSC', 'use client', and 'component re-renders' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete review targets ('state ownership, duplicated client state, rendering contracts, and component boundaries'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because every item hangs off the single verb 'Reviews' with no other action types, and is well above 3's '1-2 concrete actions'.

4 / 5

Completeness

Has a clear 'what' (reviews five named concerns) and an explicit 'when' ('Use during frontend architecture refactoring'), so the missing-trigger-clause cap at 3 does not apply. The 'when' clause is narrow and could name more concrete trigger situations, which is exactly the anchor-4 condition rather than 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('Next/React', 'frontend architecture refactoring', 'component boundaries', 'state ownership') that users would plausibly say. A few natural terms are missing (e.g., 'App Router', 'server components', 'use client', 'performance'), keeping it below the comprehensive-synonyms bar of 5 and clearly above 3.

4 / 5

Distinctiveness Conflict Risk

Scoped to a fairly distinct niche (Next/React frontend architecture) with only minor overlap risk against generic code-review or React-performance skills. Broad terms like 'boundaries' keep it from the minimal-conflict clarity of 5, but it is far more specific than the anchor-3 overlap example.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.cursor/skills/frontend-architecture-review/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.