CtrlK
BlogDocsLog inGet started
Tessl Logo

backend-code-review

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

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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, actionable instruction-only skill that routes to real bundled rule packs with clear navigation and a concrete severity/output contract. It respects the context budget and provides specific, executable review guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no padding, no explanation of what a review or framework is, and every section (Evidence First, Rule Routing, Severity And Output) earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: a numbered evidence-gathering procedure, an explicit diff-type to rule-pack routing table, severity criteria with examples, and a precise output contract (file/line, contract, reproduction path, impact, fix direction).

5 / 5

Workflow Clarity

Evidence First is a clear numbered sequence with an implicit validation gate ('Report only findings tied to an observable failure...'), but it lacks an explicit validate/feedback loop; acceptable since reviews are read-only, so just short of 5.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with a well-signaled one-level-deep reference routing table; all four referenced packs (architecture-rule, db-schema-rule, repositories-rule, sqlalchemy-rule) exist in ./references/ and are mapped to clear trigger conditions.

5 / 5

Total

19

/

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.

The description is tightly scoped with explicit trigger guidance and a concrete exclusion list, making activation unambiguous. It is concise, third-person imperative, and free of fluff.

DimensionReasoningScore

Specificity

Names the domain (backend code review under `api/`) and several concrete review modes ('pending-change, file-focused, and pasted-diff reviews'), short of comprehensive coverage of distinct review actions.

4 / 5

Completeness

Explicitly answers what ('review or audit of backend code', three review modes) and when ('Use only when the user explicitly requests a review or audit... Do not use for...') with concrete trigger and exclusion phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('review or audit of backend code', 'pasted-diff', 'frontend code') plus an explicit exclusion list, though it lacks broader synonyms beyond review/audit.

4 / 5

Distinctiveness Conflict Risk

A clear niche (backend code under `api/`) with explicit exclusion of frontend, implementation-only, diagnosis-only, and backend outside `api/`, minimizing conflict with adjacent skills.

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.