CtrlK
BlogDocsLog inGet started
Tessl Logo

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

47

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/autoreview/SKILL.md

The canonical home for this skill is autoreview in openclaw/openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 content is highly actionable with concrete commands and a clear, validated closeout workflow, but it is notably verbose and inlines reference-grade tables and engine details that would be better placed in separate reference files. Progressive disclosure is moderate due to the monolithic inlining of model/isolation/env reference material.

Suggestions

Move the model-default tables, thinking-level tables, isolation-flag tables, and environment-variable tables into separate reference files (e.g., references/models.md, references/isolation.md) and link to them from the body to improve progressive disclosure and conciseness.

Trim repeated restatements of engine defaults and isolation behavior that appear in both the Contract and Helper sections; state each once.

Consolidate the overlapping 'Models and thinking' prose and table content to reduce token cost while preserving the executable examples.

DimensionReasoningScore

Conciseness

The ~440-line body is noticeably verbose: it repeatedly re-explains engine behavior, isolation flags, and default models across the Contract, Helper, Models, and Review engine isolation sections, and reuses paragraphs of detail that could be trimmed, matching the 'noticeably verbose; several padded sections' anchor.

2 / 5

Actionability

It provides mostly executable guidance: concrete bash/powershell invocations like '"$AUTOREVIEW" --mode branch --base origin/main' and real flag examples cover the common cases, with minor gaps where behavior is described rather than shown.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (set paths, pick target, run, rerun until clean) with explicit validation/feedback checkpoints ('rerun focused tests and rerun the structured review helper', 'stop as soon as the helper exits 0 with no accepted/actionable findings'); only minor validation gaps keep it below 5.

4 / 5

Progressive Disclosure

Bundle files exist (scripts/autoreview, test-review-harness, autoreview_test.py) but the body inlines a large amount of reference-grade material (model tables, isolation-flag tables, env-var tables) that could live in separate reference files; structure is present with section headers but content is not split out, matching the 'some structure but content that should be separate is inline' anchor.

3 / 5

Total

13

/

20

Passed

Description

43%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 specific and narrowly scoped to multi-engine pre-commit code review, but it lacks an explicit 'Use when...' trigger clause and natural trigger phrases, which limits completeness and trigger-term quality. It reads in acceptable third-person voice.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers such as 'Use when the user asks for a code review, a second-model review, or a pre-commit/pre-ship check on a branch or PR.'

Include more natural user phrasings (e.g., 'review my changes', 'second opinion', 'review the PR') rather than relying on engine names as triggers.

Mention the target artifacts (local diff, branch, PR, commit) in the description so the 'what' is more comprehensive.

DimensionReasoningScore

Specificity

Quotes 'Pre-commit/ship code review' and 'Codex default; optional Claude or Pi' name the domain and a concrete action (code review) plus engine selection, but no further concrete actions are enumerated, matching the 3 anchor (domain + 1-2 concrete actions, not comprehensive).

3 / 5

Completeness

It states a clear 'what' (pre-commit/ship code review) but the 'when' is only weakly implied by 'Pre-commit/ship'; no explicit 'Use when...' clause is present, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The only natural trigger terms are 'code review' and the engine names; it omits common user phrasings like 'review my changes', 'second opinion', or 'review the PR', so it has a few generic keywords but misses the natural phrases users say.

2 / 5

Distinctiveness Conflict Risk

The narrow niche (multi-engine pre-commit code review with named engines Codex/Claude/Pi) is fairly distinct from generic review skills, with only minor overlap risk against a plain 'code review' skill.

4 / 5

Total

12

/

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