CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-and-simplify-changes

Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review...

Quality

76%

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/review-and-simplify-changes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-sequenced, genuinely actionable orchestration workflow with concrete commands, a findings schema, and safety constraints. Its main weaknesses are token-inefficiency from verbatim repetition of the read-only rule across all four sub-agent sections and the duplicated description text, plus a missing validation failure-recovery loop.

Suggestions

State the read-only constraint once in the sub-agent spawning rules and remove the four verbatim repetitions of 'This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.'

Add an error-recovery loop to Step 5: instruct that if validation fails, the agent should fix the reported issues and re-run the same scoped validation before summarizing.

Drop the 'When to Use' section that restates the frontmatter description verbatim (including its truncation artifact), or replace it with a one-line scope summary.

DimensionReasoningScore

Conciseness

The instruction 'This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes' is repeated verbatim under all four sub-agent roles even though the general spawning rules already state 'do not let sub-agents edit files, run apply_patch, stage changes, commit'. The 'When to Use' section also restates the frontmatter description verbatim, which is unnecessary padding that could be trimmed.

3 / 5

Actionability

Concrete, executable guidance throughout: exact diff commands ('git diff', 'git diff --cached'), a defined findings schema (file/line, category, why, fix, confidence), named sub-agent roles, preferred fix types, and validation examples (targeted tests, typecheck, lint). Minor gaps — e.g., it says 'read the repo's local instruction files' without naming a search order beyond AGENTS.md — keep it below 5.

4 / 5

Workflow Clarity

A clear six-step sequence with explicit mode selection, defaults, scope-resolution order, and a validation step in fix-and-validate mode. It falls short of anchor 5 because Step 5 lacks an error-recovery loop (what to do when validation fails) and the 'Recommended sub-agent role: explorer/reviewer' references are undefined role names rather than concrete spawn instructions.

4 / 5

Progressive Disclosure

No bundle files exist, and the single SKILL.md is well-organized with clear section headers (Modes, Steps 1–6, Limitations) and no nested references. The four sub-agent role specifications could plausibly live in separate reference files, but each is short enough that inlining is defensible — good structure with minor organization gaps, matching anchor 4.

4 / 5

Total

15

/

20

Passed

Description

75%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 clearly communicates both capability and trigger conditions with natural quoted phrases, but it is literally truncated mid-sentence ('review...'), which caps every dimension. The repeated verbatim copy of the truncated text in the body's 'When to Use' section confirms the truncation is not a parsing artifact.

Suggestions

Complete the truncated trigger list — the description ends mid-phrase at 'review...' and likely cuts off additional trigger terms.

Add common synonyms users say for this task, such as 'refactor', 'clean up code', or 'audit changes', to broaden natural trigger coverage.

Mention the file-scope and diff-target flexibility in the trigger clause (e.g., 'use when the user names specific files or a branch/commit range to review') to sharpen the 'when' guidance.

DimensionReasoningScore

Specificity

The description lists several specific actions — 'Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes' — which matches the 'several specific actions; minor gaps' anchor. It falls short of 5 because the sentence is truncated ('review...') and the fix capabilities are described only abstractly.

4 / 5

Completeness

Both 'what' (review diff for reuse/quality/efficiency/clarity/standards, optionally apply safe fixes) and 'when' ('Use when the user asks to...') are present with concrete trigger phrases. It sits between anchors 4 and 5: the explicit trigger list would qualify for 5, but the truncation ('review...') leaves the 'when' clause incomplete, so 4 fits better.

4 / 5

Trigger Term Quality

Includes natural quoted phrases users would say: "simplify code", "review changed code", "check for code reuse", "review code quality" — good keyword coverage matching anchor 4. Not 5 because the final trigger is cut off mid-phrase and common synonyms like 'refactor', 'clean up', or 'audit' are absent.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (diff-scoped quality/reuse review with safe fixes) with distinct quoted triggers, so it is 'mostly distinct; minor overlap risk' with other code-review skills. It is not 5 because generic triggers like "review code quality" could overlap with other review-oriented skills.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/review-and-simplify-changes/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.