CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-code-review

Review Dify frontend code for correctness, accessibility, component design, dify-ui usage, data/query boundaries, performance, and tests. Trigger for `.tsx`, `.ts`, `.js`, UI, React, Next.js, pending-change, or focused frontend review requests.

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured, highly actionable code review skill with excellent progressive disclosure through clearly referenced rule packs. The workflow is well-sequenced with explicit prioritization and severity definitions. Minor verbosity in the 'Required Context' and 'Supported modes' sections prevents a perfect conciseness score, but overall the content is strong and purposeful.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining basic concepts, but some sections like 'Supported modes' and the extensive 'Required Context' list could be tightened. The repeated references to external files add necessary navigation but also bulk.

2 / 3

Actionability

The skill provides concrete, actionable guidance: specific git commands for scoping, explicit severity definitions with clear criteria, a structured output format with markdown template, and precise file paths for every referenced resource. The review process steps are specific and ordered.

3 / 3

Workflow Clarity

The 5-step review process is clearly sequenced with explicit prioritization (user-visible regressions first, then maintainability/performance). The severity classification provides clear decision criteria, and the output format enforces structured reporting. The workflow naturally includes validation through the 'read context first, then review' pattern.

3 / 3

Progressive Disclosure

Excellent progressive disclosure structure: the SKILL.md serves as a clear overview with well-signaled one-level-deep references to 8 rule pack files, each with descriptive summaries. Required context files are listed with specific conditions for when to consult them. Navigation is straightforward.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted skill description that concisely covers specific review dimensions, includes natural trigger terms with file extensions and framework names, and clearly delineates both what the skill does and when to use it. The Dify-specific scoping and enumeration of review areas make it highly distinctive. Uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete review areas: correctness, accessibility, component design, dify-ui usage, data/query boundaries, performance, and tests. These are clearly defined, actionable review dimensions.

3 / 3

Completeness

Clearly answers both 'what' (review Dify frontend code across multiple dimensions) and 'when' (explicit trigger clause listing file types, frameworks, and request types). The 'Trigger for...' clause serves as an explicit 'Use when' equivalent.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: '.tsx', '.ts', '.js', 'UI', 'React', 'Next.js', 'pending-change', 'frontend review'. Good coverage of file extensions and framework names that naturally appear in user requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive by scoping to 'Dify frontend code' specifically, mentioning 'dify-ui usage' as a unique concern, and targeting specific file extensions and frameworks. Unlikely to conflict with generic code review or backend review skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 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.