CtrlK
BlogDocsLog inGet started
Tessl Logo

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

56

Quality

71%

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 ./.agents/skills/autoreview/SKILL.md
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.

The body is an exemplary thin delegation entrypoint: lean, concrete, and honest that it contains no review implementation. Its only real gaps are the implicit step ordering and the missing exact invocation syntax for the shared helper.

DimensionReasoningScore

Conciseness

The ~19-line body is lean with zero padding: every sentence is a directive (where the canonical skill lives, how to install it if missing, how to run the helper, where fixes belong). It matches anchor 5 ('every token earns its place') and assumes Claude's competence throughout.

5 / 5

Actionability

Concrete guidance dominates: the canonical URL, 'python3 scripts/install-skills autoreview', the Windows 'python' and '--mode copy' caveats, and the 'scripts/autoreview' helper path. It matches anchor 4 ('concrete code or commands with minor gaps'); not 5 because the exact invocation form of the helper (command line, arguments) is not shown.

4 / 5

Workflow Clarity

A discernible sequence exists (locate the installed skill, read its SKILL.md and required references, install only if missing, run the helper, keep fixes upstream) with an explicit conditional-recovery branch for a missing installation. It matches anchor 4 ('clear sequence with most checkpoints'); not 5 because the ordering is implicit across prose paragraphs rather than an explicit numbered flow, and not 3 because the 'if the skill is missing' fallback and precondition ('read before reviewing') act as checkpoints.

4 / 5

Progressive Disclosure

The body is a pure overview under 50 lines with no bundle files; it cleanly delegates one level deep to a clearly signaled external target (the canonical autoreview skill at its URL and installed path). The simple-skill exception applies: well-organized short content with no need for external references scores 5.

5 / 5

Total

18

/

20

Passed

Description

45%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 states a clear domain and an implementation channel but enumerates no concrete review capabilities and gives no 'Use when' trigger guidance. It is more specific than pure fluff, yet well short of the good examples that list actions and trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review code, a diff, or a pull request' — this would raise completeness from 3 and is currently the largest weighted gap.

Enumerate 1-2 concrete capabilities (e.g., 'Reviews the current diff or a PR branch for correctness bugs and quality issues') to lift specificity above anchor 2.

Include natural trigger variations such as 'review my code', 'PR review', or 'review staged changes' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Structured code review') but the only other content is installation plumbing ('through the shared OpenClaw agent-skills installation'), not a concrete capability. It matches anchor 2 ('names the domain but actions are minimal or generic'); it is not level 3 because no distinct concrete review actions are enumerated.

2 / 5

Completeness

A clear 'what' is present (performs structured code review), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This matches anchor 3 ('clear what but when is missing'); not 2 because the 'what' is concrete, and not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'code review' is a natural phrase users would say, giving some relevant keywords, but common variations and synonyms ('review my code', 'review this PR/diff', 'review changes') are missing. This matches anchor 3; it is not 4 because keyword coverage is limited to a single phrase.

3 / 5

Distinctiveness Conflict Risk

'Code review' as a bare phrase overlaps with any generic review skill, but the 'shared OpenClaw agent-skills installation' qualifier narrows it, matching anchor 3 ('somewhat specific but could still overlap with similar skills'). Not 4 because the core trigger phrase is still broad enough to collide with other review skills.

3 / 5

Total

11

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
openclaw/crabbox
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.