CtrlK
BlogDocsLog inGet started
Tessl Logo

code-reviewer

进行系统化的代码审查,检查代码质量、安全性和性能。当用户要求审查代码、review 或检查代码时使用

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/code-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 concise and well-structured with actionable checklists and a concrete output example. The main gap is the absence of verification/validation checkpoints in the review workflow before findings are reported.

Suggestions

Add a validation step to the workflow (e.g. re-confirm each finding against the cited file/line before reporting) to create a feedback loop and raise workflow clarity.

Make abstract checklist items more actionable with concrete signals (e.g. name specific patterns or tooling for N+1 detection, caching, XSS escaping) instead of yes/no questions.

Consider moving the detailed per-dimension checklists into a reference file and keeping SKILL.md as an overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and efficiently organized with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete categorized checklists, a required output structure, and a fully worked example, though some checklist items remain abstract prompts (e.g. 是否合理使用缓存) rather than executable steps.

4 / 5

Workflow Clarity

A clear ordered sequence (必须按以下顺序检查) and severity-based reporting format exist, but there are no validation checkpoints or feedback loops to confirm findings before reporting.

3 / 5

Progressive Disclosure

Well-structured single file with clear section headers and no nested references; the inlined checklist detail is borderline content that could be split out, but the organization is strong for a self-contained skill.

4 / 5

Total

16

/

20

Passed

Description

83%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 concise, third-person, and answers both what and when with explicit trigger guidance. It is strong overall, with only slight room to add more specific review actions and synonyms.

DimensionReasoningScore

Specificity

Names the code-review domain and concrete aspects checked (代码质量、安全性、性能), but stays at a category level rather than enumerating specific review actions.

4 / 5

Completeness

Clearly states what the skill does (systematic code review across quality/security/performance) and explicitly when to use it (当用户要求审查代码、review 或检查代码时).

5 / 5

Trigger Term Quality

Includes natural trigger terms users would say (审查代码、检查代码, plus the English 'review'), with good but not exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to code review with distinct triggers; minor overlap risk with adjacent developer-tooling skills.

4 / 5

Total

17

/

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
einverne/dotfiles
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.