CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-code-review

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-structured review skill that acts as a router to real bundled reference packs with clear condition-based navigation and severity-ordered output guidance. Could add a short example finding/output template to make the body self-contained.

DimensionReasoningScore

Conciseness

A lean ~40-line router with no concept explanations or padding; assumes Claude's competence and every line is actionable guidance or routing.

5 / 5

Actionability

Provides concrete procedural steps ("Read the changed lines, their behavior owner, and the nearest scoped AGENTS.md") and condition-to-file routing, but the concrete review rules are delegated to reference files and no example finding or output is shown inline.

4 / 5

Workflow Clarity

A clear numbered Evidence-First sequence with a "no findings → state verification gap" checkpoint and severity-ordered output, but no explicit validate-fix-retry feedback loop (acceptable since review is non-destructive).

4 / 5

Progressive Disclosure

A concise overview routing to eight one-level-deep reference files, all verified present in ./references/, each clearly signaled by a matching condition and rendered via link references.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, well-scoped description that clearly states both capability and trigger conditions with explicit exclusions to reduce false activation. Minor improvement possible by adding concrete file-extension triggers.

DimensionReasoningScore

Specificity

Names the frontend-code-review domain and three concrete review modes ("pending-change, file-focused, and pasted-diff reviews") plus scoped paths, which is several specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers what (frontend review/audit with three review modes) and when ("Use only when the user explicitly requests a review or audit..." with scoped paths and negative triggers).

5 / 5

Trigger Term Quality

Includes natural user terms "review" and "audit" as synonyms plus "frontend code", but lacks file-extension variants like .tsx/.jsx that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to `web/` or `packages/dify-ui/` with explicit "Do not use for..." exclusions (implementation-only, diagnosis, backend-only), giving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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
langgenius/dify
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.