CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-slop

Review one code change for agent slop and rate it Low, Medium, or High. Slop is avoidable, low-trust work that comes from not understanding the repo, such as wrong assumptions, broken flows, duplicate systems, weak tests, comment noise, and leftover dead code. Use when asked to "review this diff for slop", "check this PR for slop", "is this change sloppy", or when a review loop runs the slop lens. Read-only; it reports findings and does not fix them.

Quality

88%

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

71%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 a tight, well-structured instruction sheet with an exact output contract and sensible rules, and it makes the right call keeping the lens out of SKILL.md. Its critical flaw is that the referenced lens.md — which the body says defines slop, what to look for, and how to choose the rating — is missing from the bundle, leaving the skill's core evaluation criteria unavailable.

Suggestions

Ship lens.md alongside SKILL.md (or inline a condensed version of its slop definitions and the Low/Medium/High rating bands) so the core detection criteria and rating-selection rules are actually reachable.

Add a brief fallback in the body for when lens.md cannot be found, e.g. a one-line summary of each rating band, so the review can still produce a defensible Rating line.

Number the workflow steps (gather inputs → read the diff → apply the lens → write the report) so the sequence and the rating checkpoint are explicit rather than implied by section order.

DimensionReasoningScore

Conciseness

The ~60-line body is lean throughout: concrete inputs, a one-line git command, terse rules ("Do not charge the change for problems in code it does not touch"), and an output template with no concept re-teaching or padding. Every token earns its place and it assumes Claude's competence, matching anchor 5; the only mild redundancy (read-only stated in the intro and Rules) is not enough to drop to 4.

5 / 5

Actionability

Concrete guidance is present — "git -C <checkout> diff <base> <head>" with the "-- <path>" variant and an exact machine-readable report template ("The last line must be `Rating: <value>` with nothing after it") — but the core detection criteria and how to choose Low/Medium/High are delegated to lens.md ("Read lens.md in this skill's directory and apply it. It defines slop, what to look for, and how to choose the rating"), and that file does not exist in the bundle. Key details are missing, fitting anchor 3; not 4 because the central evaluation guidance is unresolvable, not 2 because the commands and output contract are fully executable.

3 / 5

Workflow Clarity

The flow — gather inputs (with a recovery path: "If the caller leaves one out, work it out and say what you used"), read the diff, apply the lens, emit the fixed report — is clear and the read-only rules remove risky operations. Minor gaps keep it at anchor 4: the steps are implied by section order rather than sequenced, and the rating-decision step is underspecified because the lens that defines it is absent; not 5 since a checkpoint on how findings map to the rating is missing.

4 / 5

Progressive Disclosure

The architecture is right — a lean SKILL.md delegating definitions, detection criteria, and rating method to a single clearly-signaled, one-level-deep file — but the referenced lens.md is not present in the skill's directory (no references/, scripts/, or assets/ exist, and no lens.md anywhere in the bundle). The promised detail layer is absent and navigation is broken, which fits anchor 3; not 4/5 because the disclosure structure does not function as written, not 2 because nothing is inlined or buried and the reference is well signaled.

3 / 5

Total

15

/

20

Passed

Description

100%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 exemplary: concrete actions with an explicit rating scale, a precise definition of slop, a clear read-only boundary, and quoted natural trigger phrases covering direct requests and pipeline usage. It explicitly answers both what and when with no fluff or over-claims, in third person throughout.

DimensionReasoningScore

Specificity

"Review one code change for agent slop and rate it Low, Medium, or High" names the action, the scale, and the read-only behavior ("it reports findings and does not fix them"), and the slop taxonomy ("wrong assumptions, broken flows, duplicate systems, weak tests, comment noise, and leftover dead code") makes the capability concrete. Multiple specific actions with comprehensive coverage of the skill's surface, matching the anchor-5 example; no coverage gap justifies 4.

5 / 5

Completeness

Explicitly answers both what ("Review one code change for agent slop and rate it Low, Medium, or High", read-only, reports findings) and when ("Use when asked to..." with three quoted trigger phrases), matching the anchor-5 pattern exactly. The 'when' clause is explicit with concrete triggers, so the anchor-4 'could be more explicit' case does not apply.

5 / 5

Trigger Term Quality

Verbatim natural user phrases — "review this diff for slop", "check this PR for slop", "is this change sloppy" — cover diff/PR/change and slop/sloppy variants, plus an automation trigger ("when a review loop runs the slop lens"). No natural phrasing a user would plausibly say is missing, so it fits anchor 5 rather than 4.

5 / 5

Distinctiveness Conflict Risk

"Agent slop" is a clear niche and every trigger phrase carries the distinguishing slop/sloppy qualifier, so a generic code-review skill would not capture these invocations. Minimal conflict risk fits anchor 5; anchor 4's 'minor overlap risk' is not warranted since the disambiguating keyword appears in all triggers.

5 / 5

Total

20

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Agenta-AI/agenta

Path

.agents/skills/review-slop/SKILL.md

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.